
Your ERP is the system of record. It knows every sales order, every transfer, every procurement order. It holds your equipment rates and labor costs. It’s where finance goes to figure out whether you made money.
But ask it a simple question — what did it actually cost to deliver that order? — and it has no idea. Because the real delivery cost is sitting in a completely different system. Or in a spreadsheet. Or in Tyler’s head.
Here’s how it works in most mid-size fleet operations. Orders originate in the ERP — typically Microsoft Business Central. They get pushed (usually one-way) into a TMS or dispatch tool. Loads get assigned, drivers execute, and completed shipments come back into the system.
But the cost data doesn’t come back clean. The actual delivery cost — fuel, driver hours, kilometers traveled, wait time, empty return legs — either doesn’t flow back to the ERP at all, or flows back as a flat allocation that tells you nothing about what the individual order actually cost to fulfill.
So finance is making margin calculations based on theoretical costs. Pricing decisions are based on estimates. And nobody knows which customers are profitable and which are quietly losing money on every delivery.
“Your ERP can tell you exactly what you charged the customer. It can’t tell you what it cost to get the product there. That gap is where margin disappears.”
Most TMS platforms do some version of cost tracking. But the data stays in the TMS. It doesn’t flow back onto the specific sales order, transfer order, or procurement order in the ERP where finance needs it.
And when it does flow back, it’s usually at the wrong level of granularity. You get a total cost for a route, not a cost per order. Or you get a flat rate per load that doesn’t account for the empty leg, the detour, or the three hours the driver spent waiting at a site.
The result is a business running on two separate views of reality. Sales and finance see revenue and theoretical cost in the ERP. Operations sees actual delivery performance in the TMS. Neither team trusts the other’s numbers. And the real margin picture is somewhere in between.
Stat: Companies that implement closed-loop cost tracking between their TMS and ERP report discovering 8–15% of customer accounts are margin-negative — losses that were invisible under theoretical cost allocation.
The technical challenge isn’t moving data from one system to another. It’s mapping the data correctly. A single sales order might generate multiple shipments across different days. A single route might carry loads for three different order types. A transfer between production sites has a different cost structure than a customer delivery.
Getting this right requires a middleware layer that understands how your orders work, how your routes are structured, and how costs should be allocated across different load types. It’s not a standard integration. It’s a business logic problem that’s specific to how your operation runs.
This is exactly why off-the-shelf TMS platforms struggle with it. They were built for a generic cost model. Your cost model isn’t generic.
We talk about ERP integration and cost visibility. If your finance team is making margin decisions based on theoretical delivery costs, that’s a gap worth closing.
Book a call with the ScaleLabs team and we’ll map how your delivery costs should flow back into Business Central so finance sees the real numbers.