The Hidden Challenge in Dynamics 365 Supply Chain Management Transportation
Dynamics 365 Supply Chain Management includes transportation management capabilities for rate shopping, load building, tendering, freight reconciliation, and inbound and outbound transportation planning.
The bigger question for many organizations is carrier connectivity. F&SCM does not include the rate engines needed to connect those workflows to individual carriers, so companies must build or acquire them and maintain them as carrier requirements change.
That makes the key implementation decision less about whether F&SCM can manage transportation and more about how much carrier connectivity the organization wants to build, acquire, and maintain. It is the decision behind most Dynamics 365 TMS integration evaluations, and it is worth making deliberately rather than discovering mid-implementation.
What does the transportation management module cover?
F&SCM manages transportation planning and execution workflows inside the ERP.
Rate shopping and freight optimization. The rate route workbench supports rate shopping across carriers and modes, with flexible rating through the rating engine and support for volumetric weight. Microsoft also exposes a rating engine API for integration with external parties.
Load building and optimization. Orders can be consolidated into loads using load templates and load building strategies, including volume-based strategies that work from height and weight maximums.
Tendering and dispatch. The module supports electronic shipment requests to carriers, dock appointment scheduling tied to warehouse operations, and transportation documents.
Freight reconciliation. When a load is confirmed, freight rates calculated by the carrier's rate engine transfer to a freight bill and post as miscellaneous charges to the source document. Reconciliation can match the freight bill against the carrier invoice manually or automatically using configured match tolerances.
Inbound and outbound coverage. Transportation planning extends across sales orders, purchase orders, and transfer orders, with inbound and outbound load planning workbenches.
For organizations with a contained freight profile, such as a handful of contracted carriers and stable domestic lanes, configuring the required engines may be manageable. The cost and complexity increase as carrier networks, modes, and rating requirements expand.
Why does carrier connectivity create ongoing work?
Transportation management engines provide the logic used to calculate transportation rates and process carrier-specific requirements. A rate engine is required for each carrier, alongside supporting engines it may depend on, such as mileage engines.
Because the engines are not supplied with F&SCM, each carrier creates a build-or-buy decision.
Building means developing against the transportation management engine framework and maintaining that code as carriers revise specifications and service requirements. Buying means sourcing engines from a third party.
The ongoing work tends to surface in several areas.
Rate accuracy. Carrier base rates, fuel surcharges, and accessorial schedules change independently of the ERP configuration. An engine that is not maintained can produce variances that surface later during freight reconciliation.
Accessorials. Charges such as liftgate, residential delivery, inside pickup, limited access, detention, and reconsignment require logic in the rate engine. Anything not encoded can become a downstream variance requiring review.
Mode expansion. LTL, FTL, parcel, ocean, rail, and international air bring different rating, connectivity, and documentation requirements. Each additional mode expands the integration scope.
Visibility. In the small parcel shipping workflow, the documented carrier exchange returns a rate, label, and tracking number when a container is closed. Continuous milestones such as picked up, in transit, out for delivery, exception, and delivered require separate carrier data feeds.
This is where a transportation strategy can become constrained by what has already been configured. Adding another carrier, mode, or service may require additional development or a new integration rather than simply changing an ERP setting.
For importers, there is another consideration: freight rating and landed cost capitalization are handled through separate F&SCM capabilities, and transportation freight charges are not added to item cost. Teams managing significant import volume should account for both when designing the overall freight workflow.
How does a connected freight platform integrate with Supply Chain Management?
A connected freight platform integrates with Supply Chain Management through the Data Management Framework or direct API integration. The transportation management module's rating engine API is also designed for integration with external parties.
Order and shipment data moves to the freight platform, where rating against maintained carrier connections, carrier selection, booking, document generation, and tracking take place. Carrier, service-level, and tracking data then moves back into the ERP. Where freight audit and AP workflows are configured, validated freight cost can return to the ERP's financial processes.
The platform operates alongside F&SCM rather than as software embedded within it.
In practice, transportation planning can remain inF&SCM while carrier execution runs through the connected freight platform. Order entry, customer service, and finance can continue working in the ERP while shipping teams use the freight platform for execution.
The trade is specific: carrier connectivity becomes a vendor's maintenance obligation instead of an implementation partner's development backlog.
What should teams establish before adding a freight execution layer?
Integration ownership. Establish which party configures F&SCM endpoints and data entities and which owns the freight platform side.
Carrier integration ownership. Determine whether the vendor maintains its own carrier connections or relies on third-party rate engines or broker networks. That model has commercial and reliability implications.
System roles. Decide which system owns planning, which owns execution, and how data moves between them. Adding an execution layer does not require abandoning transportation planning in F&SCM.
Environment requirements. Sovereign and GCC High environments can introduce additional requirements for external integrations, while on-premises deployments raise questions about whether shipment data can leave the network.
How does FreightPOP extend Dynamics 365 Supply Chain Management?
FreightPOP is an AI supply chain software platform unifying order management, warehouse management, and transportation management. It extends Supply Chain Management with carrier connectivity and freight execution while allowing the ERP to remain the system of record for core order and supply chain data.
FreightPOP connects to Dynamics 365 Supply Chain Management through the Data Management Framework or direct API integration and is listed on Microsoft AppSource. It supports parcel, LTL, FTL, ocean, rail, and international air, with automated freight audit and AI auto-dispatch across the shipping workflow.
Carrier integrations are owned and maintained directly rather than routed through third-party rate engines or brokers. That shifts the ongoing carrier connectivity burden away from the ERP implementation team.
Customers see up to 30% savings on freight spend with FreightPOP. On the audit side, operations see 8–15% savings through invoice auditing.
Frequently Asked Questions
Does Dynamics 365 Supply Chain Management include a transportation management module?
Yes. Transportation management is a feature area within Dynamics 365 Supply Chain Management. It covers rate shopping, load building, tendering, dock appointments, freight reconciliation, and transportation across sales orders, purchase orders, and transfer orders.
Does the transportation management module support multi-carrier rate shopping?
Yes. The rate route workbench supports rate shopping across carriers and modes for which rate engines are configured. F&SCM does not include those carrier-specific rate engines, so organizations must obtain or build the engines they need.
What are transportation management engines?
Transportation management engines define the logic used to generate and process transportation rates. Rate engines are tied to specific carrier requirements and may rely on supporting engines, such as mileage engines, to calculate rates.
Does F&SCM include rate engines for carriers like FedEx or UPS?
No. Microsoft's documentation states that F&SCM doesn't include any rate engines and that organizations must obtain or create the engines they require. A demo engine is provided for testing purposes.
How is freight cost posted back into Dynamics 365 Supply Chain Management?
Freight rates calculated by the carrier's rate engine transfer to a freight bill when a load is confirmed and post as miscellaneous charges to the source document. Reconciliation matches the freight bill against the carrier invoice using configured match tolerances. Where a connected platform handles audit and AP transaction processing is enabled, validated freight cost can export back into the ERP.
How does a connected freight platform integrate with Supply Chain Management?
A connected freight platform can integrate with Supply Chain Management through the Data Management Framework or direct API integration. Order and shipment information can move to the freight platform for carrier rating, booking, execution, and tracking, with carrier and shipment data written back to the ERP.
The decision is about connectivity, not capability
Dynamics 365 Supply Chain Management includes a transportation management module, and for organizations with a contained carrier network, it can provide the core capabilities needed to plan and manage freight.
As carrier count, mode mix, and accessorial complexity increase, however, the challenge shifts from transportation planning to maintaining the carrier connectivity behind it.
A connected freight execution layer can move that burden to a vendor while allowing Supply Chain Management to remain central to the broader supply chain workflow.