← Automation
Automation

ERP and WMS integration: stock levels, locations, receipts and issues without retyping

19 November 2026

The ERP and the WMS describe the same warehouse from two sides. The ERP keeps the book stock: item code, quantity, value, document. The WMS keeps the physical stock: this pallet, in this location, with this best-before date. Without a connection every receipt and issue is entered twice, and the discrepancies come out at stocktaking. Integration is not a single “interface”; it is a set of flows, each with a direction, a source of truth and error handling. Below: how to design them.

What flows in which direction

A typical split, which has to be confirmed for the specific pair of systems:

Data Source of truth Direction
item codes, units, packaging ERP ERP → WMS
counterparties, delivery addresses ERP ERP → WMS
purchase orders (what is due to arrive) ERP ERP → WMS
sales orders (what to issue) ERP ERP → WMS
physical receipt (what actually arrived) WMS WMS → ERP
physical issue, picking WMS WMS → ERP
locations, batches, dates WMS stay in the WMS
stock quantity disputed see below

Stock quantity is the most common source of conflict. A rule that works: the WMS is the source of truth for what is physically there, the ERP for what has been posted, and the difference between them has to be visible and explained, not hidden by “forced” synchronisation.

Flows step by step

Advance notice and receipt. The ERP sends the purchase order to the WMS as an advance shipping notice. The WMS receives the delivery: actual quantity, batch, location. The WMS sends the receipt back to the ERP with the actual quantity. The ERP creates the goods receipt document and, if there is a discrepancy, an event for purchasing to resolve. Never the other way round: nobody enters a receipt in the ERP “because the invoice has arrived”.

Order and issue. The ERP sends the sales order to the WMS. The WMS picks, packs and issues; it sends the issue back to the ERP with lines and quantities. The ERP issues the WZ (goods issue note) and the invoice based on what was issued, not on what was ordered.

Adjustments and transfers. Transfers between locations stay in the WMS. Transfers between accounting warehouses (e.g. to production) go to the ERP as a document. A post-stocktake adjustment is created in the WMS and goes to the ERP with a reason.

Master data. A new item code is created in the ERP and passed to the WMS; the WMS does not create item codes. If a warehouse worker has to receive something that is not in the master data, they need a “report missing item code” path, not the ability to create it locally.

The technical side without jargon

Three ways of exchanging data, from the best:

  1. An interface (API) on both systems, event by event, with acknowledgement of receipt. The fastest and the easiest to diagnose.
  2. A message queue or a staging table in the database: one system puts a message there, the other picks it up. Good when the systems work at different rhythms.
  3. Files exchanged at set intervals. The simplest, but the delay is built into the method; with issues every few minutes, a file once an hour is not enough.

Whatever the method, you need: a unique identifier for each message (so that a receipt is not posted twice), a log of what went out and what came back, and a queue of rejected messages with the reason, reviewed by a person.

Common mistakes

  • Two sources of truth for stock and a “synchronisation” that overwrites one with the other. The discrepancies disappear from the screen, not from the warehouse.
  • A receipt entered in the ERP from the invoice and then a second time from the WMS.
  • No handling of discrepancies: a delivery of 98 instead of 100 ends with a manual correction and no trace.
  • Creating item codes in the WMS because “it takes ages in the ERP”.
  • File-based integration once a day with shipments going out during the day.
  • No message log; in a dispute it is impossible to establish what each system sent.

What to calculate

The number of receipts and issues per day and the minutes needed to enter each one manually into the other system give you the retyping time. The number of stocktaking discrepancies in the last year and the time spent explaining them is the cost of not having a single source of truth. The time from physical issue to invoice is the measure the customer feels. The company has these numbers in its own documents; they just need to be collected.

Checklist

  • A flow table with direction and source of truth, approved by the warehouse, purchasing and accounting.
  • Handling of receipt and issue discrepancies as an event for a person.
  • A single place for creating item codes and counterparties.
  • Message identifiers, a log, a rejected-message queue.
  • An exchange rhythm matched to the rhythm of the warehouse.
  • A pilot in one warehouse or one group of item codes.

At ErgoFlow we start an ERP–WMS integration with the flow table and sources of truth, and build it with a log and a rejected-message queue so that discrepancies are visible; for warehouses with automated storage systems and dispensing machines, receipt and issue events are created in the device and sent from there to the systems. More on the Automation page.

This article is for information only. The split of flows and the exchange method depend on the specific ERP and WMS and their licences; we agree the details after an audit.

Want this in your company?

Book a demo and see ErgoFlow in action.

Book a demo