Dynamics 365 Shipping Integration for Freight Shippers
A Microsoft Dynamics 365 shipping integration connects Dynamics 365 Business Central or Finance and Operations directly to your carriers and...
Microsoft Dynamics 365 supports transportation management in two ways: through a built-in TMS module within Dynamics 365 Finance and Operations, or through a third-party TMS integration that can be used across both Finance and Operations and Business Central.
The Microsoft module, which is limited to Dynamics 365 Finance and Operations, is designed to handle routing, load planning, and freight reconciliation within the ERP environment. In contrast, a third party TMS integration extends Dynamics 365 with capabilities such as real-time rate shopping, multi-carrier connectivity, and end-to-end shipment visibility across all transportation modes. In practical terms, this reflects the difference between managing transportation planning internally and executing freight across a broader carrier network.
This guide compares both approaches to help freight operations teams determine how to structure and optimize transportation management within their Dynamics 365 environment.
The Dynamics 365 TMS module is a built-in component of Dynamics 365 Finance and Operations. Business Central does not include a transportation management capability.
The module covers five core transportation workflows:
For operations with a limited carrier network, domestic lanes, and standard routing requirements, the Dynamics 365 TMS module provides a functional transportation layer built directly into the Dynamics 365 Supply Chain Management license.
No. Business Central does not include a built-in Transportation Management module. It provides basic shipping fields such as carrier assignment and shipment method, but does not support rate shopping, load planning, or freight reconciliation out of the box.
For freight operations in Business Central, a third-party TMS integration is required from the start. There is no module to extend or configure for this purpose. The integration becomes the operational foundation rather than an optional upgrade.
This is the most important distinction when evaluating the Dynamics 365 TMS landscape. F&O users are deciding whether to extend existing capabilities. Business Central users are selecting where freight execution begins.
The built-in Dynamics 365 TMS module was designed for a defined scope of transportation planning. In freight operations with multiple carriers, complex accessorials, and real-time execution requirements, five capability gaps typically appear:
Real-time multi-carrier rate shopping: The built-in TMS module uses static rate tables configured within Finance and Operations. It does not connect to live carrier feeds for dynamic rate comparison across LTL, FTL, parcel, and intermodal. Operations that rely on fixed tables are not optimizing freight spend in real time.
Active carrier connectivity: Real-time booking, label generation, and shipment tracking require live API or EDI connections to individual carriers. The Dynamics 365 TMS module does not maintain those connections at the depth most freight operations require.
LTL accessorial handling: Liftgate, residential delivery, inside pickup, detention charges. LTL accessorial logic requires carrier-specific rules that go beyond the standard load planning functionality.
Automated freight audit: Identifying invoice discrepancies, flagging overcharges, and preventing overpayment before costs post to the general ledger requires audit automation the standard reconciliation workflow does not deliver at scale.
Continuous shipment visibility: Real-time tracking data must be sourced through external carrier integrations. Without additional middleware, live shipment status updates are not consistently available.
Operations that extend the Dynamics 365 TMS module with a third-party integration report a 20% to 30% reduction in freight costs through multi-carrier rate shopping and up to 10% savings through automated freight invoice auditing.
A third-party TMS integration connects Dynamics 365 to a logistics execution platform. Business Central connects via OData APIs using token-based OAuth authentication. Finance and Operations connects via data entities and APIs. In both cases the result is a bi-directional data flow.
Order data moves from Dynamics 365 to the logistics platform, where carrier selection, rate shopping, and shipment execution happen. Carrier information, service codes, and tracking numbers are written back to Dynamics 365 in real time upon shipment. For operations with AP transaction processing enabled, audited freight costs are exported back into Dynamics 365 Purchase Journals automatically, keeping financial records accurate without manual reconciliation.
For freight-heavy operations the additions are material:
For a full breakdown of how the integration data flows work in practice, see the FreightPOP guide to Dynamics 365 shipping integration.
The right structure depends on freight volume, carrier diversity, and which Dynamics 365 version the operation runs.
Dynamics 365 TMS module is sufficient for operations with a limited carrier network, simple domestic lane structures, lower shipment volumes, and no requirement for real-time rate comparison or automated freight audit.
A third-party integration is necessary for operations managing multi-carrier LTL and FTL at scale, complex accessorial requirements, freight audit automation, and all Business Central users who have no built-in TMS module to begin with.
In both cases the principle is additive. A third-party Dynamics 365 TMS integration extends what the ERP does well, order management, financial reporting, procurement, by adding freight execution capabilities the built-in module was not designed to cover. Dynamics 365 remains the system of record. The TMS integration handles carrier-level execution.
FreightPOP integrates with both Dynamics 365 Business Central and Finance and Operations, providing multi-carrier freight execution, real-time rate shopping, automated freight audit, and shipment visibility from a single platform.
The integration connects to Business Central via OData APIs and writes carrier, service, and tracking data back in real time upon shipment. For accounts with AP transaction processing enabled, audited freight costs are exported directly into Dynamics 365 Purchase Journals. Operations using FreightPOP report a 95% reduction in shipment processing time, a 40% increase in on-time deliveries, and freight cost reductions of 20 to 30% through live rate shopping across hundreds of carriers.
See how FreightPOP integrates with Dynamics 365.
The Dynamics 365 TMS module is a built-in transportation management component within Finance and Operations that handles route planning, load optimization, carrier rating, and freight reconciliation inside the ERP. It is not available in Business Central.
No. Business Central does not include a Transportation Management module. Freight execution for Business Central operations requires a third-party TMS integration connected via OData APIs using token-based OAuth authentication.
The Transportation Management module is available in Dynamics 365 Finance and Operations (Supply Chain Management) only. It is not included in Business Central, Dynamics NAV, or earlier AX versions without additional configuration.
The built-in TMS module covers routing, load planning, and basic freight reconciliation using static rate tables configured within Finance and Operations. A third-party integration adds live multi-carrier rate shopping, real-time carrier connectivity, LTL accessorial handling, automated freight audit, and bi-directional cost sync back into the ERP.
No. The built-in TMS module uses static rate tables rather than live carrier connections. Real-time rate shopping across LTL, FTL, parcel, and intermodal requires a third-party TMS integration with an active carrier network.
Finance and Operations includes basic LTL load planning within the built-in Dynamics 365 TMS module. Real-time LTL rate shopping, accessorial handling such as liftgate and residential delivery, and carrier-specific BOL generation require a third-party integration with active LTL carrier connections.
The strongest integrations provide bi-directional data sync with both Business Central and Finance and Operations, real-time rate shopping across hundreds of carriers, automated freight audit, and seamless cost data flow back into the ERP. The right fit depends on freight modes managed, carrier volume, and ERP version.
FreightPOP's freight audit tool compares each carrier invoice against the original shipment quote. If the invoice falls within a predefined variance threshold it is automatically approved. If discrepancies exceed the threshold the invoice is flagged for review before payment. For accounts with AP transaction processing enabled, approved invoices are exported directly to Dynamics 365 Purchase Journals. Operations typically recover 6% to 8% of freight spend through this process.
Timelines typically range from 3 to 6 months depending on carrier connections, freight modes, custom field mapping, and workflow configuration. Business Central deployments via OData APIs tend to move faster than Finance and Operations implementations requiring data entity and API configuration.
Yes. A full TMS integration manages inbound freight from purchase orders alongside outbound shipments from sales orders, providing visibility and cost capture across all freight movement, not just outbound execution.
The Dynamics 365 TMS module provides basic LTL load planning. Real-time LTL rate shopping, accessorial handling, and carrier-specific BOL generation require a third-party integration with active LTL carrier connections.
Yes. Existing contracted rates connect directly into the TMS rate shopping dashboard, preserving carrier relationships while enabling real-time comparison against additional options.
The Dynamics 365 TMS module covers transportation planning fundamentals for Finance and Operations users with standard freight needs. But for operations managing multi-carrier LTL and FTL at scale, and for all Business Central users, a third-party integration delivers the carrier connectivity, rate shopping automation, and freight audit capabilities the built-in module was not designed to handle.
See how FreightPOP connects to Dynamics 365 Business Central and Finance and Operations
A Microsoft Dynamics 365 shipping integration connects Dynamics 365 Business Central or Finance and Operations directly to your carriers and...
In the fast-paced world of logistics and supply chain management, efficiency, cost-effectiveness, and seamless operations are not just goals but...
SAP shipping in S/4HANA and Business One is supported through SAP’s Transportation Management, Extended Warehouse Management, and Sales and...