Industries / Supply chain & distribution
A distributor lives on two numbers: whether the stock will be there when the customer wants it, and what the line really earned once freight and duty landed on it. Both are ordinary Business Central, configured properly. Neither survives being kept in a spreadsheet beside it.
Sub-models
The four we implement, and what each one actually changes in the configuration.
Customer-specific price and discount structures, backorders, and part-shipment rules. The configuration question is how much of your pricing belongs in price lists rather than in someone’s memory.
You hold stock you do not own. That is a different inventory model — ownership, billing for storage and handling, and reporting per client rather than per company.
Long lead times and container economics. Landed cost stops being an accounting afterthought and becomes the number the buying decision is made on.
The same stock promised to several channels at once. Availability has to be one figure, not one per channel, or you oversell the fastest-moving lines.
The processes, by name
If your operations manager uses the word, we implement the thing.
A projected available balance that accounts for what is on order and what is already committed, so a date given on the phone is one the warehouse can keep.
Reorder points and safety stock that reflect the lead time each vendor actually achieves rather than the one on the agreement, and a requisition worksheet people trust enough to act on.
Bins, zones and directed movement sized to the building you have. A small warehouse over-configured is slower than one with no bins at all, and we will say so.
Freight, duty, brokerage and insurance applied to the receipt as item charges, so margin is calculated on what the goods cost you and not on the invoice price.
Purchase orders in, invoices and despatch advices out, mapped to what each partner demands. Business Central does not ship an EDI engine; this is integration work and it is scoped as such, in the estimate, not discovered in testing.
A return that puts stock back in the right condition and the right bin, and a credit that ties to the original sale rather than floating on its own.
The part that gets tested
A large retail customer does not send a complaint. It sends a chargeback, and the first you hear of it is a deduction on a remittance.
Carrier, pallet build and appointment rules that differ by customer, held in the system rather than in the shipping clerk’s head.
Barcode labels and an advance despatch notice that matches what physically arrives. A mismatch between the notice and the pallet is the most commonly deducted error.
Measured from your own posted shipments, so a disputed deduction is answered with a document rather than an assertion.
Our apps that earn their keep here
Software we already ship for this work.
Receiving, put-away, picking and counting
A mobile barcode WMS that runs inside Business Central. Scanner-driven receiving, put-away, picks, moves and counts — posting through BC’s own codeunits, so the ledger is the only source of truth.
On Microsoft AppSource (opens the marketplace listing in a new tab)
License plating and container handling
License-plate management for pallets and containers: build, split, merge and move whole plates instead of line-by-line quantities.
On Microsoft AppSource
Demand forecasting and replenishment
Per-location demand forecasts and service-level-driven reorder points, written into Business Central’s own planning fields and ranked by dollar exposure. Classical statistics, back-tested against a baseline they have to beat — deliberately no AI in the arithmetic.
On Microsoft AppSource (opens the marketplace listing in a new tab)
Supplier invoice processing
Vendor invoice to posted purchase invoice, inside Business Central. The invoice is treated as a claim and reconciled against BC’s own order and posted receipt, so a mis-read number raises a legible exception instead of posting a wrong figure.
On Microsoft AppSource
Every app above is implemented by the team that built it — one contract, one accountable engineering group.
How we deliver
FitShipRunFit to standard first
Most requirements are configuration, not code.
Build like it ships
Custom work held to our marketplace bar.
Run it with you
We stay through your first month-end close.
Straight answers
Including the ones where the honest answer is that we are not the right firm.
Not on its own. It has the document structures and the API surface, but the mapping and the transport are integration work, through a connector or a broker. We scope it explicitly rather than letting it surface as a change request in month four.
Yes, and it is a design decision rather than a setting. Third-party stock is usually modelled with separate locations and non-owned item handling, and getting that structure right at the start is far cheaper than restating it later.
Freight, duty and brokerage are applied to the receipt as item charges, so they land on the item cost rather than in an expense account. The discipline is applying them before the goods sell; a charge applied afterwards corrects the ledger but not the margin you already quoted on.
Often not. Business Central has several levels of warehousing, from simple bins to directed put-away and pick, and the right one depends on the building and the volume. Over-configuring a small warehouse makes it slower, and that is a thing we tell customers before they buy it, not after.
The other three
Next step
Thirty minutes, not a deck. We’ll tell you whether standard Business Central covers it, whether one of our apps does, or what a build would honestly take.
sales@dynamicspro.ca · Serving North America · 416-843-6575