TMS-ERP integration: How to connect transport to the system that runs your business

Once a sales order is in your ERP system and the goods are ready for dispatch, someone still has to book the transport to deliver them to their destination. This is the point where the ERP system that runs your business is unable to proceed, and where TMS-ERP integration comes into effect.

Your ERP knows the customer, the address, the items and their weights. But it cannot book the shipment, because it has no direct line to DHL, DSV, Kuehne + Nagel or the regional carrier you use. So someone on your team opens a carrier portal, enters the delivery details by hand, books the shipment and copies the tracking number back into the ERP. Then they do it again in a different portal for the next carrier.

This is the gap between what your business knows and how your goods move. Most logistics teams fill this gap manually, and it costs them more than they realize. That manual step is worth a closer look and how a TMS-ERP system integration changes things.

What is TMS-ERP integration?

There are two systems on either side of this. Your ERP system is the core of your business, handling finance, inventory, procurement, production and the orders that trigger everything down the line. Common ERP platforms in manufacturing include SAP, Microsoft Dynamics 365, NetSuite, Odoo and Monitor. A transport management system (TMS) is responsible for transport operations such as comparing carrier rates, booking shipments, producing labels and freight documents, tracking deliveries, and checking carrier invoices. If you would like a full breakdown of how the two differ and whether you need both, read our article ERP vs TMS. 

TMS-ERP integration is the two-way data bridge that links the two systems. When an order is confirmed in the ERP, the integration passes the shipment details to the TMS. Once the shipment is booked and on its way, the TMS sends the carrier, the tracking reference and the actual freight cost back to the ERP. The ERP remains responsible for the order, and your carriers continue to move the goods. The integration removes the manual handoff in the middle, so nobody has to re-enter shipment details into a portal and then into the ERP again.

Without this connection, your team becomes the connection: exporting spreadsheets, copying tracking numbers between tabs and reconciling freight costs that a connected system would match automatically.

Why your ERP cannot connect to your carriers on its own

Your ERP and your carriers use different systems, and keeping up with them all is a full-time job that your ERP vendor has no reason to take on.

Each carrier has its own integration setup. Some use modern APIs, others use EDI, and the specifics differ from carrier to carrier. Building a connection with one carrier tells you very little about how to build the next one. Once you work with more than a handful of carriers, you are maintaining a handful of different connections, each with its own specific features.

Those connections also change over time. Carriers update their APIs, adjust their data requirements and revise their formats over time. A connection that works today requires maintenance to ensure it continues to work next year. This involves an ongoing effort rather than a one-off build. 

Your ERP was built to manage finance, inventory, procurement and production. Carrier connectivity is not its area of expertise, and ERP vendors do not invest in keeping dozens of carrier integrations current. Most ERP shipping modules let you assign a carrier and print a delivery note, but they fall short of live booking and rate comparison across your whole carrier list, along with several other areas a dedicated TMS covers. That is the difference between a basic shipping field and a working TMS-ERP integration.

Building all of this in-house therefore becomes an IT project that never really finishes. 

How data flows between your TMS and ERP

The order (from ERP to TMS). Once a sales order is confirmed and a delivery is triggered, the ERP system passes the shipment details to the TMS, including the consignee, address, items, weights, dimensions, and required delivery date. This handover enables booking to begin without anyone having to enter the information again. If this process is delayed, the whole chain is affected.

The shipment status (from TMS back to ERP). Once you book, the TMS sends the chosen carrier, the tracking reference and delivery milestones back to the ERP. This allows anyone in the company who is looking at the order (whether in sales, customer service or on the production floor)  to see where it is without logging into a carrier portal.

The freight cost (from TMS back to ERP). The actual cost of the shipment is recorded against the order in your financial records. This turns invoice checking from blind approval into a match against the agreed rate. Freight billing errors are estimated to cost mid-market shippers between 3% and 7% of their total annual freight spend, and these errors can only be identified if the expected cost is recorded in the system alongside the invoice.

What a TMS-ERP integration looks like

Here is a single shipment once the two systems are connected.

1. The order is created in your ERP. A sales order comes in and triggers a delivery, same as it does today.
2. The delivery data flows into the TMS automatically. The consignee, address, items, weights and dimensions are sent to the TMS without anyone entering them manually.
3. You choose the carrier and book. You compare live rates across your carriers, pick the right one, and book it in a few clicks.
4. Labels and documents are generated automatically. The shipping label, the CMR and any other paperwork are produced from the shipment data, in the format each carrier needs.
5. Tracking and cost flow back to the ERP. The tracking reference and the actual freight cost are pushed back into the ERP, so your financial record is complete and your team can check the invoice later against what was agreed.

Compare that with the manual version, where steps two to five are done manually, per shipment, often across several carrier portals. The data is entered once into the portal and again into the ERP. Each entry is a chance for an error, and each shipment takes an extra amount of time.

Measurable benefits of a TMS-ERP integration

• Time. This is the most visible benefit. Booking a shipment manually takes fifteen to twenty minutes. Once the data is in place and the rates are loaded, the time taken drops to just a few minutes. If you have several hundred shipments a month, it will save you days of work.
• Accuracy. When shipment data is entered once in the ERP and used everywhere else, a whole range of errors caused by copy-and-paste mistakes disappears: no mistyped postcodes, no mislabeled shipments, no rejected bookings and no parcels sent to the wrong depot. These issues do not appear in the monthly report, but in the form of a phone call from a customer.
• Visibility. Instead of logging into separate carrier portals to piece together what is in transit, you get one view across every carrier. When the production planner or the sales team asks where an order is, you can answer straight away. This grows with scale: valve manufacturer AVK ran freight inquiries by email until 25 companies and 70 users depended on the system, then moved to Cargoson and could approach carriers with combined volume data from across the group.

For production companies that ship varying cargo sizes to different destinations at different frequencies, it gives them a good overview and a quick possibility to check the best carrier for the job.

Agnieszka Skrzypińska, Global Category Freight Manager

• Resilience. When onboarding, booking and tracking are all carried out through one connected system, the knowledge is stored in the system rather than in one person's routine. This means that the process is no longer dependent on who knows which portal to use and where the passwords are kept. When someone is on holiday, off sick or leaves, operations can continue as normal. 

One integration instead of many

The real change that a TMS brings is in the number of connections you have to manage. Instead of building and maintaining a separate integration for each carrier, you only need to build one connection to the TMS. The TMS then handles all the carrier connections behind it. When you add a carrier, it's not another IT project you're starting. Either the connection already exists, or the TMS provider builds it. This is what tools and machinery wholesaler Stokker did when it moved to a new ERP: rather than rebuild every carrier integration in the new system, it connected all its transport partners through Cargoson, cut setup time from weeks to minutes, and now runs 15,000 shipments a month with a two-person team. 

We didn't want to initiate the integrations with all the different transport providers. Our goal was to use a single point of centre, which is Cargoson. That fully helps us to move faster and actually provide value for our customers, because we don't have to spend money on linking all the transport partners.

Taivo Karu, Head of Supply Chain and Board Member at Stokker

The same single point works on the inbound side too: let your suppliers book against your contracted rates through it and you can see incoming raw materials alongside outbound goods, which for larger manufacturers is often where the biggest wins are. 

This also solves the problem of carriers offering services that vary widely. Some have a full pricing and booking API, others only have a booking portal, and some still work entirely over email. A good TMS levels this out by filling in the gaps left by a carrier. If a carrier has no pricing API, your negotiated rate card is loaded into the system so that the price calculation happens there instead. The same goes for transit times, tracking, labels and freight documents.

The part that matters for your IT team is that the TMS provides a single API for your ERP. A delivery triggered in the ERP can request live rates from all your carriers and book the chosen carrier through that single connection. The tracking reference and cost are then returned in the same way. Your developers only need to integrate once and will never need to touch an individual carrier connection again. Medical device maker SomnoMed connected all its carriers to NetSuite through one Cargoson integration and cut label creation from 90 minutes a day to 20 in France alone, then rolled the same setup out across its other European hubs.

What to look for in a TMS-ERP integration and how Cargoson can support

Not every TMS treats ERP integration the same way. Some charge for each connector, some offer only a one-way feed. These are the questions to put to any vendor before the technical validation stage, with how Cargoson answers each one, since Cargoson is built to be exactly this layer between your ERP and your carriers for European manufacturers and wholesalers.

Does it connect to your ERP natively? Ask specifically about your platform, whether that is SAP, Microsoft Dynamics 365, NetSuite, Odoo or Monitor. A native connector means setup is configuration, not custom development, so ask how many live integrations the vendor already has with your ERP, not just whether they support it. 

Cargoson offers pre-built connectors for the major platforms, including Microsoft Dynamics, Dynamics 365 for Finance and Operations, NetSuite and Odoo, along with warehouse and e-commerce systems. If your platform is on that list, the connector already exists.

Is it configuration or custom development? This tells you whether implementation is measured in days or in months, and it is the question your IT team will want answered first.

Because Cargoson's connectors already exist, linking your ERP is a matter of configuration rather than a custom build. This keeps implementation times to just a few days.

Is the data flow two-way? A one-way feed that only pushes orders to the TMS solves half the problem. You need shipment status and freight cost flowing back to the ERP as well. 

Cargoson pushes tracking references and actual freight costs back automatically, so your financial record stays complete and you can check carrier invoices against what was agreed.

Does it use your existing carrier contracts and rates? You want a platform that works with the rates you have already negotiated, so you keep your pricing and your carrier relationships. A good TMS does not push new carriers on you or renegotiate anything. 

Cargoson is an independent platform and is not carrier-owned, so you work directly with your own carrier contracts and keep the pricing you negotiated. With Cargoson, your rates stay yours.

How are new carriers added, and how long does it take? Adding or switching a carrier should take days, not months. Ask what happens when you bring on a carrier that is not yet connected, and who builds that integration. 

Cargoson connects to more than 2,000 carriers via direct API and EDI, syncing rates, transit times and tracking automatically, and if you work with one that is not yet connected, Cargoson builds it at no extra cost.

Practical tips to avoid common mistakes 

It is rarely the technology that makes these projects difficult. A few practical things keep a TMS-ERP integration on track and avoid common mistakes: 

1. Don’t treat your ERP's built-in shipping module as if it were a TMS. That native module typically covers a fraction of what a dedicated system does. It will assign a carrier and print a delivery note, but rates across carriers, tracking and freight invoice reconciliation are usually missing.
2. Sort your carrier and address data. If your ERP uses inconsistent carrier codes or has messy address fields, these problems will be transferred straight into the TMS. Doing a little cleanup before you connect will save you a lot of time troubleshooting afterwards.
3. Don’t go live without testing. A good TMS gives you a sandbox, so use it: run a batch of real orders through end to end before anything reaches a carrier. A mistake caught in a test environment is a line in a log. The same mistake in production is a wrong label and a carrier dispatched for nothing. Cargoson provides a test environment for this, so you can test the integration and see it working before you commit. 
4. Give it an owner. An integration is not set-and-forget: ERPs are upgraded and carriers change formats. Having someone responsible for monitoring these changes is the difference between a quiet fix and a surprise.

The connection between what your business knows and how your goods move should not depend on someone re-typing an address into a carrier portal. This manual step is where time is lost, errors occur, and knowledge becomes trapped in one person's routine.

A TMS is the layer that closes the gap. Done well, TMS-ERP integration means your ERP keeps the order, your carriers keep the freight, and the work in between stops being manual.

If you would like to see how to connect your ERP and your carriers, book a free demo and we are happy to walk you through. 

Book a free 30-minute consultation here