5 Freight Gaps in Business Central's Built-In Shipping Tools
Shipping in Microsoft Dynamics 365 Business Central is organized around the shipping agent record: a carrier, a service level, a tracking URL. For a parcel order that structure is sufficient, and the path from order to label runs without much friction.
What the structure does not carry is freight class, density, or accessorial codes, because it was never scoped to. Freight execution begins where the shipping agent record stops, and it is a different discipline with different data requirements.
Five areas account for most of the work that manufacturers and distributors running Business Central end up handling outside the ERP: inbound freight cost, multi-mode rate comparison, invoice reconciliation, in-transit status, and carrier selection logic.
1. Inbound Freight Cost Does Not Reach the Purchase Order
Business Central tracks purchase order lines, quantities, and unit costs accurately. What it does not carry is the transportation side: which carrier is moving the inbound load, what the freight will cost, and when the material lands on the dock.
Landed cost therefore stays an estimate until the carrier invoice posts, often weeks after receipt. A purchasing team comparing two vendors on unit price alone is working without the variable that frequently decides which one is actually cheaper.
This is also the least-addressed area in the Business Central shipping ecosystem. Most available tools are outbound-first, built around the sales shipment rather than the purchase order, which leaves inbound freight coordination running on email and spreadsheets.
2. Rate Comparison Is Limited to Parcel Carriers
Built-in rate retrieval works through configured shipping agents, which covers parcel.
LTL and FTL rating does not work that way. Rates turn on freight class, dimensions, density, origin and destination pairing, accessorials, and negotiated contract terms that differ by carrier. Comparing three LTL carriers on one shipment means entering the same shipment details three times, in three portals, and recording the results somewhere outside the ERP.
At low freight volume that is manageable. At real volume it is the reason shipments go out on whichever carrier the shipping clerk used last time, because the comparison is the step that gets skipped when the dock is backed up. Multi-carrier rate comparison across freight modes cuts freight spend by 20 to 30 percent, and that figure depends entirely on the comparison actually happening.
Extending rate coverage across freight modes is the function Microsoft Dynamics shipping software is built to add.
3. Freight Invoices Post Without Reconciliation
Business Central posts a vendor invoice as entered. It has no mechanism for checking that invoice against what was quoted.
Freight billing is unusually error-prone: reclassified freight, weight corrections, accessorials nobody authorized, fuel surcharges calculated off the wrong base, duplicate billing on re-tendered loads. Catching any of it means holding three records side by side, the original quote, the contract terms, and the actual shipment, then disputing the difference inside the carrier's filing window.
For most teams the audit simply does not happen, because manual reconciliation across several hundred invoices a month is not work an AP team has room for. Automated freight invoice auditing recovers 8 to 15 percent of freight spend.
4. In-Transit Status Is Not Written Back to the ERP
Business Central holds the record of what shipped. Where that shipment currently sits lives in the carrier's system.
Answering a customer means looking the load up in the carrier's system, matching it against the PRO number, and relaying the status by hand. Across multiple carriers and the daily volume of status questions, that is a real share of customer service time spent retrieving data that already exists somewhere.
The larger cost is timing. A load that missed its pickup or sat at a terminal over a weekend is discoverable, but only if someone thinks to look. Tracking data written back to shipment records as it changes moves exception handling from reactive to same-day.
5. Carrier Selection Operates Without a Rules Layer
Built-in shipping executes a carrier decision. It does not make one. That call happens per order, and it depends on the judgment of whoever is processing it.
Freight operations at volume run on defined logic instead: orders above a weight threshold tender to LTL, contract customers route to assigned carriers, regional shipments consolidate before dispatch, service levels map to what was promised rather than to habit. Encoding that logic so tendering happens automatically, with exceptions routed for review, is what separates a shipping desk from a freight operation.
Without it, carrier selection quality varies by operator and by shift, and consistency depends on tribal knowledge rather than configuration. A closer comparison of the built-in module against a Dynamics 365 TMS running alongside it sets out where each approach fits.
What Closing These Requires Alongside Business Central
FreightPOP connects to Business Central through its Microsoft AppSource listing, using OData and SOAP APIs with token-based authentication. It is not an AL extension embedded in Business Central. It runs alongside the ERP and exchanges data with it.
Confirmed Business Central integration scope:
- Posted Sales Shipments, imported and exported
- Carrier and tracking write-back to shipment records
- Purchase Journal export, supplying freight invoice data for auditing
Setup requires the Business Central partner to expose the relevant API pages and provide endpoints and credentials. There is no auto-configuration of web services.
Freight execution running in FreightPOP: rate comparison across parcel, LTL, FTL, ocean, rail, and international air over 500-plus directly owned carrier connections with no third-party rate engines in the path, automated freight invoice auditing, in-transit tracking, rules-based and AI-assisted dispatch, and inbound freight management. Order management and warehouse operations run on the same platform, which matters where receiving, picking, and shipping are one conversation.
For most of the business the platform stays out of view. Finance, customer service, and sales work from shipment and tracking data in Business Central. Warehouse and logistics staff are the ones in FreightPOP directly.
Frequently Asked Questions
Does Business Central include a transportation management system?
No. Business Central includes shipping agent configuration and shipment posting, which supports parcel execution. Multi-carrier freight rating, BOL generation, freight audit, and carrier tendering are handled by transportation management system platforms connected to the ERP.
What freight modes do Business Central's built-in shipping tools support?
The built-in tools are oriented around parcel carriers configured as shipping agents. LTL, FTL, ocean, rail, and air freight require freight classification, density-based rating, and BOL documentation beyond what that configuration covers.
How does inbound freight cost get onto a purchase order in Business Central?
Business Central supports charge allocation on purchase documents, but the freight cost value has to come from somewhere. In most environments it is entered manually after the carrier invoice arrives, which is why landed cost accuracy at receipt remains a common issue for teams managing inbound freight.
Can Business Central audit freight invoices automatically?
No. Business Central posts vendor invoices as entered. Validating a carrier invoice requires the original rate quote and the shipment record to be available for comparison, which is a function of the freight platform rather than the ERP.
Is FreightPOP a native Business Central extension?
No. FreightPOP is listed on Microsoft AppSource and connects to Business Central through OData and SOAP APIs, running alongside the ERP rather than inside it. Shipping tools built as AL extensions embedded in Business Central represent a different architecture serving a different scope.
What does the Business Central partner need to do for setup?
The partner exposes the required API pages in the Business Central environment and provides endpoints and credentials. FreightPOP integrates into those endpoints from there.
Does FreightPOP work with Dynamics 365 Finance and Supply Chain Management?
Yes. F&SCM connects through the Data Management Framework or direct API, supporting both inbound and outbound freight workflows.
Business Central covers parcel shipping execution within its intended scope. Freight operations spanning LTL, FTL, inbound, and multi-carrier rating need a layer built for that work, connected to the ERP rather than replacing any part of it. Integration detail is available on FreightPOP's Microsoft Dynamics shipping software page.