A load never ships until three questions get answered: which carrier, what rate, and which route. D365 transportation management answers all three through one form, the Rate Route Workbench, before a shipment ever leaves the dock.
This guide will explore how D365 transportation management structures rate engines, load planning, and carrier selection, and where freight cost analysis still needs more than the reconciliation process ships natively.
Every load answers three questions before it ships
The Rate route workbench is where rate, route, and carrier actually get decided, and it offers three distinct functions rather than one blended answer.
- Rate retrieves the single best, lowest available rate for a load.
- Rate shop retrieves multiple rate and route options at once, letting a logistics planner compare rather than accept the first result.
- Route retrieves only the available routes matching source and destination criteria, without pricing attached.
This workbench can be opened from load planning, from the loads list, or directly from a sales order, and opening it from an order auto-populates the required fields rather than asking a planner to re-enter what the order already specifies.
Clearing the shipping carrier, service, and mode fields before running Rate Shop widens the search rather than narrowing it, which is a small setting most new users get backwards on their first attempt, expecting the opposite result.
Rate engines: how a carrier’s price actually gets built
A rate does not come from a single number typed into a carrier record. D365 transportation management rate engines are built from a specific chain of configuration: rating metadata first, then a break master, then a rate master associated to that metadata, then one or more rate bases each tied to a break master, then rate base assignments, and finally a rating profile unique to one carrier.
- A break master defines the pricing logic itself, a rule such as charging one rate under 100 miles and a different rate beyond it.
- The rating profile is what actually ties a specific carrier and shipping service to all of this configuration, which is why two carriers can be rated completely differently even for the identical shipment.
This chain has to be built in a specific order, since a rate master cannot exist without a rating metadata ID to attach to, and a rating profile cannot exist without a rate master to reference. A logistics manager who tries to configure a rating profile first, before the underlying rate master and break master exist, will find the system has nothing to actually connect it to.
Rate masters, break masters, and rating profiles generate a rate for every load, but almost none of that structure survives into a simple freight report. The Metrixs analytics suite is what keeps it visible.
Load planning: consolidating shipments before rating even starts
The Outbound load planning workbench is where individual orders become loads, using a Volume-based load building strategy that respects the height and weight limits on a load template, or a custom strategy an organization builds for its own constraints.
- Hub consolidation lets multiple loads route through an intermediate hub before final delivery, generating new transportation request lines with the hub as the drop-off point for the first leg and the customer as the destination for the next.
- Consolidating shipments this way is what actually reduces the number of trips a business needs, which is where most freight savings in D365 transportation management genuinely come from, before a single rate has even been calculated.
A load template’s height and weight limits only matter if someone actually configured them to reflect the real vehicles a business uses. A generic template copied from a demo environment and never revisited will happily consolidate orders into loads that look correct in the system and do not actually fit on the truck that shows up to collect them.
Carrier selection and routing
Carrier selection in D365 transportation management is rarely a single default choice. Rate shop surfaces multiple carriers side by side, and route guides act as decision-making frameworks that automatically match a load to the best route based on distance, load size, time constraints, and carrier performance.
- Scheduled routes handle recurring shipments, a daily replenishment route to the same set of stores, without a planner rebuilding the same route from scratch every time.
- Multi-mode transportation lets a single organization plan across trucks, rail, and other modes within the same system rather than switching tools depending on how a shipment moves.
Route guides earn their value most clearly during disruption. A road closure or a sudden capacity shortage with a preferred carrier is exactly when a static, manually maintained routing decision breaks down, while a route guide built to evaluate distance, time, and carrier performance together can redirect a load without a planner having to notice the problem first.
If carrier selection keeps defaulting to habit rather than what rate shop actually recommends, a Metrixs consulting review can show the gap between the two.
Freight cost analysis: where estimate meets actual
When a load is confirmed, D365 transportation management generates a freight bill carrying the rate engine’s estimated cost. That estimate is not the final word. Freight reconciliation, the matching process, compares the freight bill against the actual invoice a carrier sends, and any variance between the two gets flagged rather than absorbed silently.
- Reconciliation can run manually, matching freight bills to invoices line by line, or automatically for organizations that receive carrier invoices electronically.
- This is genuinely where the analysis starts: an estimate that is consistently high or low against actual invoices reveals a rate engine that has drifted from what carriers are actually charging, well beyond a single isolated billing dispute.
Shipment tracking and where native reporting still leaves a gap
Shipment tracking gives visibility into where a load stands across carriers and modes, integrated with the same loads and freight bills the rest of transportation management already generates.
That integration is what makes shipment tracking genuinely useful rather than a separate status board someone checks out of habit. A delayed shipment flagged through tracking is tied directly back to the load, the carrier, and the freight bill behind it, so a service failure and its cost impact are visible together instead of requiring two separate lookups to connect them.
- Freight reconciliation happens load by load, so a variance pattern across an entire carrier relationship, or across a full fiscal year, is not something the matching process itself was built to trend.
- Comparing cost variance across multiple carriers, modes, or legal entities at once usually means exporting reconciliation results and assembling the comparison manually.
| What you need | Native D365 F&O tools | A dedicated layer such as Metrixs |
|---|---|---|
| Multi-year freight variance trend | One reconciliation run at a time | Configurable history in one saved view |
| Cross-carrier rate comparison | Assembled by hand, carrier by carrier | Consolidated automatically |
| Estimate vs. actual across all loads | Reviewed load by load | One reporting layer across every shipment |
| Refresh | As current as the last reconciliation run | 15 to 30 minutes via Synapse Link |
How Metrixs extends D365 transportation management reporting
Metrixs reads freight bills, carrier invoices, reconciliation results, and load and route data through Azure Synapse Link into the same dedicated Azure Data Lake used for the rest of D365 F&O, built across more than 6,000 backend tables.
- Freight variance held as configurable history, so a multi-year trend by carrier, mode, or route is a saved report, not a rebuilt export.
- Cross-carrier and cross-mode comparison consolidated automatically, surfacing which relationships are drifting from their rated cost before the pattern becomes expensive.
- Cost variance consolidated across a multi-entity or multi-ERP environment, not limited to one legal entity at a time.
- Refresh every 15 to 30 minutes, inside the same 12-module, 100+ report, 1,000+ metric suite; most deployments live in under 6 weeks; client ROI 290% to 450%.
D365 transportation management still rates, routes, and reconciles every load correctly on its own. Metrixs is where that reconciliation history finally becomes a trend a logistics or finance team can actually watch.
Estimated versus actual freight cost, by carrier, by mode, by year, in one place. See it in the D365 F&O finance and accounting analytics use case.
Frequently asked questions
What does the Rate route workbench do in D365 transportation management?
It provides three functions for a load: Rate returns the single lowest available rate, Rate shop returns multiple rate and route options for comparison, and Route returns available routes without pricing. It can be opened from load planning, the loads list, or directly from a sales order.
How are freight rates calculated in D365 F&O?
Rate engines use a configuration chain: rating metadata, a break master defining pricing rules, a rate master tied to that metadata, one or more rate bases, rate base assignments, and a rating profile unique to a specific carrier. This structure is why identical shipments can be rated differently by different carriers.
What is hub consolidation in D365 transportation management?
Hub consolidation routes multiple loads through an intermediate hub before final delivery, generating new transportation request lines with the hub as the interim drop-off point. It is one of the load planning techniques used to reduce the number of trips a business needs to make.
What is freight reconciliation, and how does it support freight cost analysis?
Freight reconciliation matches the freight bill generated when a load is confirmed, an estimate, against the actual invoice a carrier sends, flagging any variance between the two. It can run manually or automatically and is the foundation this kind of cost analysis is actually built on.
How does carrier selection work in D365 transportation management?
Carrier selection typically runs through Rate shop, which surfaces multiple carriers and routes side by side, or through route guides, which automatically match a load to a carrier and route based on distance, size, time constraints, and carrier performance.
Can D365 F&O trend freight variance across carriers and years?
Not as a single native view. Freight reconciliation happens load by load, so comparing variance trends across carriers, modes, or fiscal years usually means exporting reconciliation results from each period and assembling the comparison by hand.
The verdict
D365 transportation management genuinely covers the mechanics well: rate engines that price a load correctly, load planning that consolidates shipments before rating even starts, carrier selection backed by real comparison, and freight reconciliation that catches variance between estimate and actual. Every use case in this guide runs on capability D365 transportation management already ships.
Where it stops is the trend view: cost analysis held as history, compared across carriers, modes, and entities at once. Metrixs closes that gap, reading the same freight bills and reconciliation data, refreshing every 15 to 30 minutes, and shipping it as part of the same suite that already covers general ledger, budgeting, and inventory.
Ready to see your own freight cost analysis as one connected view? Book a Metrixs reporting assessment, and we will map your rate engines and reconciliation data against what the reporting layer already covers.
Related reading: Master planning in D365 F&O: how Planning Optimization changes MRP runs
