Logistics system integration: ERP, WMS and TMS

An order arrives in the online store, gets re-typed into the ERP, then into the warehouse system, and the tracking number is emailed to the customer by hand. Every step is a chance for a mistake. We connect those systems so the data flows on its own.

Logistics usually runs on several systems. The ERP manages products, orders and invoices. The WMS knows where goods are in the warehouse and what's being prepared for shipping. The TMS plans vehicles and routes. On top of that come the online store, shipping carriers and partners' systems.

Each of them does its own job well, but if they don't exchange data, there are people in between copying it over. Integration removes that copying.

01

What we connect

  • ERP with the online store, so stock levels and prices are accurate and orders arrive automatically
  • ERP with WMS, for inbound and outbound notices and confirmation of what actually left the warehouse
  • WMS with TMS, so vehicle planning knows what's ready for loading
  • shipping carriers, for creating shipments and labels and tracking their status
  • the dock scheduling system, so each slot is tied to a real order

We have built integrations like these before and know where they usually get stuck: product codes that differ from system to system, units of measure and partial deliveries.

02

What an integration looks like

First we map the data - what each thing is called in each system and which system is the source of truth for what. This step is often skipped, and it decides whether the integration will work or just move errors around faster.

Then we build the connection through the API of each system that has one. Messages go through a queue and are resent if the other side is unavailable, without ever recording the same order twice. Every exchange is logged, and when something gets stuck, the responsible person is notified instead of a customer finding the problem.

03

When a system has no API

Older ERP and warehouse systems often have no API. In that case data is exchanged through CSV or XML files in an agreed location, or directly through the database, if the vendor allows it.

For those cases we build an intermediate layer that understands the old system on one side and offers a clean API on the other. When you eventually replace the ERP, only that one connection changes and the rest of the system keeps working as before. Our general approach to building applications is described on our web application development page.

For example, for a manufacturing and logistics company we built an internal application that reads delivery plans from PDF with the help of AI and turns them into EDI files ready for exchange with other systems.

FAQ

Questions about logistics integrations

It depends on the number of systems, the quality of their documentation and how different the data is. You get an estimate once we've reviewed the systems to be connected.

If the integration is built through an intermediate layer, only the connection to that system changes and everything else stays the same.

Yes, if the carrier offers an API or file exchange. Shipments and labels are then created automatically and the delivery status comes back into your system.

Are your people copying data from one system to another?

Tell us which systems you use and where data is re-entered by hand today. We'll suggest how to connect them.

Request a free estimate →