Transportation management in Dynamics 365 SCM

The Transportation Management (TMS) module in Dynamics 365 SCM extends order management into the freight world — rating shipments, building loads, planning routes, generating shipping documents, and reconciling freight invoices. It's a meaningful capability for mid-market shippers, with clear ceilings beyond which dedicated TMS platforms (BluJay, MercuryGate, Manhattan, Oracle TMS) start to win.

Core entities.

• Carriers — the transportation providers. Each carrier has services (LTL, FTL, parcel) and rate engines.
• Routes — origin-destination definitions; can include intermediate stops.
• Loads — the container holding shipped goods, with a carrier, a route, and load lines from one or more orders.
• Shipments — the warehouse-side outbound (already in WMS); loads aggregate one or more shipments.
• Rate engines — code that computes freight cost for a load.
• Rate routes / Rate masters — rate cards per carrier per route.
• Freight bills — what the carrier billed; reconciled against the system's rated cost.

Rating. Two types:

• Spot rates — manual entry for ad-hoc shipments.
• Contract rates — uploaded rate cards (per weight, per mile, per pallet, per container).

Rate engine extensibility means partner ISVs add specific carrier rate APIs (FedEx, UPS, DHL) for real-time quotes. Without an API, you upload tariff sheets and the engine looks up rates.

Load building. The Load Planning Workbench lets a planner consolidate open shipments into loads:

• Filter by ship-from, ship-to, carrier, equipment type.
• Assign shipments to loads based on weight, volume, route compatibility.
• Calculate utilisation (% of vehicle capacity).
• Multi-stop routing (truck visits two customers on one trip).

For high-volume operations, load building is the planner's daily task; for low-volume, it's automated by rules.

Routing. Routes can be:

• Direct — origin to destination, one carrier.
• Multi-leg — pickup, hub consolidation, line-haul, last-mile delivery.
• Pool point — collected at a pool point and forwarded.

Multi-leg routing supports international shipments crossing border with brokerage steps.

Shipping documents. TMS generates:

• Bill of lading (BOL) — the carrier's contract.
• Packing list — what's in the shipment.
• Commercial invoice — for international.
• Carrier-specific labels — UPS, FedEx, DHL labels via integration.
• Custom documents — country-specific export paperwork.

For parcel carriers, the workflow ends with a label printed at the pack station; for LTL/FTL, paperwork rides with the driver.

Freight reconciliation. Carrier invoices arrive after the shipment. The reconciliation workflow:

1. Freight invoice imported (EDI, file, manual entry).
2. System matches invoice line to load and rated cost.
3. Variances flagged (rate difference, weight reweigh, accessorials).
4. Approved invoices post to AP as cost; variances post to a freight variance account or get disputed.

Done right, freight reconciliation recovers material savings; done poorly, freight overcharges sneak through.

Hazardous goods. Items flagged as hazmat carry hazmat group codes. TMS enforces:

• Carrier eligibility (not all carriers handle hazmat).
• Documentation generation (hazmat declarations).
• Mode restrictions (some hazmat can't fly).

Container management. For ocean and rail freight, container tracking integrates:

• Container booking against carriers.
• Stowage planning.
• Customs documentation per container.

Integration with WMS. Once a load is planned, the warehouse pick logic respects load assignment — pickers pick to load destination, pack to load. The handover is bidirectional: WMS reports actual ship weight back, which can trigger reweigh adjustments in TMS.

Where TMS in F&O stops being enough.

• Complex multi-modal optimisation — sophisticated TMS platforms run mathematical optimisation across thousands of shipments daily; F&O's load building is rule-based.
• Spot market integration — real-time spot quotes across freight marketplaces; F&O doesn't natively integrate.
• Visibility services — Project44, FourKites integration for in-transit tracking; F&O integrates via partner connectors.
• Yard management — F&O has basic yard features; deep yard ops typically use a dedicated YMS.

Common pitfalls.

• Rate cards out of date. Carriers renegotiate; rate cards need to follow. A monthly rate refresh cadence avoids surprise variances.
• Accessorials not modelled. Detention, fuel surcharges, residential surcharges accumulate; if not in the rate engine, they appear as variances.
• Load planning skipped. Planners ignore load building, just dispatch each shipment individually; missed consolidation savings.
• No freight invoice reconciliation. Pay-on-receipt; carriers overbill systematically when they sense no scrutiny.
• Carrier API integration cost underestimated. Integration with FedEx, UPS, DHL is ongoing work as APIs change.

Decision. F&O TMS is well-suited to mid-market shippers with consistent lanes and moderate carrier counts. Beyond that, a dedicated TMS connected to F&O via integration delivers more capability than trying to push F&O TMS past its design envelope.