Ross doesn't know what shipping actually cost you
A TMS optimizes how you ship. Ross owns what it cost and what you promised. If they aren't connected, your margins are a rumor.
You bought a TMS to fix shipping, and it did. Rates get shopped, loads get planned, labels get printed, trucks get booked. The warehouse is happier. The problem is on the other side of the wall: Ross, which is the system of record for the order and therefore for the margin, has no idea what any of it actually cost. So your margins are educated guesses, and when a customer calls to ask where their order is, customer service reads the tea leaves.
Here's the thesis. A TMS optimizes how you ship; Ross owns what it cost and what you promised. If the two aren't connected, freight cost never makes it back to the order — and your margins, and your ship-status answers, are fiction. Well-produced fiction, but fiction.
The frustration, stated plainly
The setup feels modern and is quietly broken. Great shipping decisions happen in the TMS — Odyssey, BluJay (now part of E2open), MercuryGate, Oracle Transportation Management, whichever one you run. None of the truth flows back into Ross. Someone re-keys tracking numbers when they have time, freight cost lands in the GL as a lump nobody can tie to an order, and "what did we actually make on that shipment?" is a question your finance team answers with a brave face. The TMS made the shipping better and the books no better at all, which is a strange place to end up after buying software specifically to improve operations.
Rate and mode, without typing the order twice
The first thing that should flow is the shipping decision itself, and it should flow without anyone re-entering the order into a second system. If your team is reading an order out of Ross and typing it into the TMS to get a rate, you've built a very expensive photocopier. The order — addresses, weights, contents, service level — should reach the TMS from Ross directly, so rate shopping and mode selection happen on real data instead of a hand-transcribed approximation with a typo in the zip code.
The number that matters most: freight cost back into Ross
This is the whole point, so I'll be blunt about it. The single most valuable thing this integration does is push actual freight cost back onto the order in Ross — into cost accounting and the general ledger — so your margin is a real number instead of a hopeful one.
Freight is not a rounding error. On a lot of orders it's the difference between a healthy margin and a quiet loss, and if Ross is booking a plan rate, or an average, or last quarter's guess, then every margin report you've run is off by exactly the amount you most needed to know. Getting the real, per-shipment freight back into the order is where an ERP-and-finance person earns their keep, because it's not just plumbing — it's making the books tell the truth about profitability. This is the part generic integrators skip, because they don't think about the GL. It's the part I lead with, because I do.
Tracking and status on the order
The less glamorous but very appreciated win is closing the loop on status. When tracking and ship confirmation flow back onto the Ross order, sales and customer service can answer "where's my order?" without a relay race to the warehouse and back. It's a small thing that removes a daily friction and makes the company look like it has its act together, which — with the integration in place — it now does.
Timing and reconciliation
As with any integration between two systems of record, the failure modes hide in the timing. Shipments get voided. Rates get corrected after the fact. A load gets re-planned an hour before it leaves. If Ross and the TMS don't reconcile — if they just fire events at each other and hope — the two will diverge, and you'll find the divergence in a freight accrual that never quite ties out. So the same discipline that governs every serious integration applies here: verify the two still agree, handle the voids and re-rates deliberately, and surface anything that doesn't reconcile instead of letting it rot in the GL.
Do it once, correctly
None of this is exotic. It's the unglamorous, careful work of getting the shipping decision out of Ross cleanly and the shipping reality — cost, tracking, status — back in. Do it once, properly, and you get honest margins, answerable status questions, and a finance team that stops flinching at the freight line. Skip it, and your shiny TMS will keep making beautiful shipping decisions that your system of record never hears about.
The bottom line
A TMS without a real connection to Ross improves your shipping and lies to your books. The fix is to close the loop — order out, cost and status back — with reconciliation underneath and the GL kept honest. It's the same integration everyone underestimates, and the payoff is the one number every business actually cares about: what you really made.
If your margins are guesses because freight never makes it back to the order, that's a fixable gap — and the finance side of it is exactly where I live. Let's talk →. Related: Ross ↔ WMS.
Ross was never built to hand off cleanly to a modern WMS, so they drift. On a plant floor, drift isn't untidy — it's a compliance and cash problem.
Most integration projects go sideways because nobody named the shape of the thing before building it. Here are the shapes.
NACHA files keyed by hand, payments typed into a bank portal, statements reconciled by eye. Every step is real money and one typo from the wrong account. It doesn't have to be.
learned it the hard way so you don't have to — one email starts it