A WMS on a single platform, not beside it
The value of a WMS in the core is not a longer feature list but a single stock figure: sales, procurement, the floor and finance read the same number at the same moment, with no nightly syncs and no two truths to reconcile.
- Published
- Author
- Konis Software
A distributor's ERP prints a stock report in the morning. The warehouse works from its own WMS at the same time. Two figures for the same goods, and they differ — because the interface between them turns over once overnight, while the goods move all day. The question is not whether the two systems can be joined; they can, and companies pay for years to keep them joined. The question is what it costs that they must be joined at all.
That cost never appears on the software invoice. It appears in the salesperson who promises delivery from stock the warehouse shipped two hours ago; in the accountant who asks at month-end why the inventory ledger disagrees with the warehouse; in the shift lead who knows the figure on screen is from last night. Each of them does the same surplus job: reconciling two truths about one pile of goods.
This piece is not about what a WMS does — bin locations, directed put-away and wave picking are a subject of their own. It is about where the stock figure lives. When the WMS is part of the same platform as purchasing, sales and finance, inventory stops being a number ferried between systems and becomes one record everyone reads at the same instant. That is a business difference, not an architectural one.
The price of two truths
A separate WMS and ERP exchange data across an interface: the warehouse reports receipts and issues, the ERP returns orders and master data. As long as the interface runs in real time and never breaks, the two databases behave as one. In practice the sync runs in batches — every fifteen minutes, hourly, or overnight — and there is always a window in which neither side knows the other's true state. The window is small while the company is small; it grows with turnover.
Decisions are made inside that window. Sales reserves stock in the ERP that the warehouse has already issued against another order. Purchasing reorders because the ERP shows a shortage that is really goods on their way to the rack, not yet posted. A count is done in the WMS and the correction in the ERP, so the difference is smoothed by hand — and later nobody can separate the real shortage from the sync artefact. None of these failures is a fault; each is built into having two databases.
- Sales quotes a delivery date from stock the warehouse has already issued — the customer gets a delay notice instead of goods.
- The same pallet is reserved twice because, inside the sync window, both systems believed it was free.
- Purchasing orders a double minimum because the ERP cannot yet see a receipt sitting on the dock in the WMS.
- A shortage found during picking does not reach finance until the next transfer — and the POPDV entry and the write-off wait on that number.
- A complaint needs the lot the goods left from; that lives in the WMS, while the ERP knows only that a quantity went out.
What the company gains when stock is one number
When receiving, put-away, reservation, picking and posting write to the same stock model, an entire translation layer disappears. Salesperson, buyer, accountant and forklift driver look at one number — not copies that get reconciled, but the same record from different angles. Available-to-sell is stock less reservations, computed at the moment of the query, not copied from last night's report. The same questions the business already asks get answered without an intermediary, and without the delay that intermediary adds.
| Question from the business | Two systems (ERP + separate WMS) | One platform |
|---|---|---|
| How much can I promise a customer today? | Last sync's figure, adjusted by hand for what you know left | Available = stock − reserved, at the moment asked |
| Is a dock receipt sellable yet? | Only after the next transfer to the ERP | The moment it is put away, in the same state |
| Which lot did the returned goods leave from? | In the WMS; a call to the warehouse | On the order, tied to customer and document |
| Why does the ledger disagree with the floor? | A standing month-end question | There are not two sides to differ |
| When does a shortage enter POPDV? | After the two systems are reconciled | On posting the issue, that instant |
None of this is a new feature. These are the same questions asked every morning already — only without the moment where someone has to translate them from one system into another. A single platform does not add a capability; it removes the step where the truth is lost.
A reservation tied to the order
In a two-database setup a reservation is usually just a number: set ten units aside. It names no order, follows no specific goods, and holds only until the next transfer. On one platform a reservation is a link — a specific quantity bound to a specific order line, visible to sales and the warehouse at the same moment. The same link carries a status: available, reserved, on-order, in-transit, blocked are not reporting categories but states of one record.
Available-to-promise falls out of that link. The salesperson entering an order sees not total stock but what is free after everyone else's reservations, so the delivery date they promise is backed by specific goods, not an estimate. When the warehouse picks, it takes exactly what was reserved for that order — FEFO chooses the lot, but within the quantity already promised to that customer, not from a common pile someone else can reach first. In separated systems, the reservation in the ERP and the physical pick in the WMS are two acts someone must equate; here they are two angles on one record.
Receiving, put-away, picking — one flow, one document
In separated systems the goods cross a boundary several times: a receipt is keyed in the WMS and pushed to the ERP; an order is keyed in the ERP and pushed to the WMS to pick; the shipment is confirmed in the WMS and returned to the ERP to post. Every crossing is a place where data can lag, drop or be re-keyed. In one model the flow is unbroken — each step moves the same stock, with no export and no import.
- 1
Receiving
Goods are received against a purchase order; quantity, lot and expiry are entered once. Purchasing immediately sees the order arrived and finance that the liability exists — with no wait for a transfer and no re-keying.
- 2
Put-away
Put-away brings the goods into available stock. There is no state where they are received in the WMS but invisible to sales — they are sellable the same instant, or not, by status, not by the next batch.
- 3
Reservation for an order
A sales order reserves a specific quantity. The salesperson sees available reduced; the warehouse sees what is promised and to whom — one datum, two angles, no reconciliation.
- 4
Picking
The warehouse takes what was reserved, FEFO chooses the lot, and the issue posts on confirmation. Inventory drops at that moment, not in the next transfer.
- 5
Shipping and posting
The delivery note and the electronic delivery note lean on the same issue record; COGS and inventory agree by definition, not by an overnight job.
FEFO and lots are not a feature but a safeguard
FEFO and lot tracking sell as line items in a spec sheet, but their value is commercial. FEFO at picking means the shorter-dated goods leave first — not because someone remembered to check, but because the system chooses the lot. The result is fewer write-offs on expired stock, on goods a shelf would otherwise consume. A lot tied to order and customer means a recall or complaint does not start from zero: you know which batch went where, to whom, and how much still stands in the warehouse. In separated systems that data exists, but in a different database from the one holding the customer — so every withdrawal of goods begins with a cross-check of the two systems.
The work that disappears
The clearest gain of one platform is not a new capability but work that stops existing. No reconciling of ledger against floor, because there is no second figure. No question of which system is right, because the record is one. No overnight window in which decisions are made blind. No re-keying of receipts and shipments between systems, and so none of the errors re-keying brings. That time and those errors were the quiet cost of separation — visible only once they are gone.
Two systems for one pile of goods do not give two views of the truth — they give two truths someone has to reconcile. The cost is not the interface licence; it is every day spent deciding which of them is right.
How NG One approaches it
In NG One, purchasing, inventory, sales and finance are one system, so the stock figure is one record. The WMS described in other pieces — bin locations, directed put-away, waves — sits beneath that figure, not beside it: the sum across locations equals the stock card at every moment, with no reconciliation. A reservation is a link to an order line, available is computed at query time, FEFO chooses the lot at picking, and an issue posts inventory and finance in the same step. The salesperson promising a date, the accountant closing the month and the driver at the rack read the same number — because there is no other number.