GenFrontier homeScope a project
Menu
Reader questionWhen an ERP and a WMS both hold inventory, which system is the record for each data element, and how should they sync?

ERP or WMS: which system should own each inventory number?

ERP vs WMS for inventory data: a field-by-field ownership matrix, sync patterns, 3PL 944 and 947 flows and a daily reconciliation routine you can run.

field-notes / integrations / erp-vs-wms-system-of-record
A wooden tally stick split lengthwise into two halves lying side by side, the notches across both halves lining up exactly, the lower half printed red.

In an ERP vs WMS split, the WMS should be the system of record for physical inventory: which bin, which license plate, which lot, which status and how many. The ERP should own the item master, cost and valuation, customer and transfer orders, and the company-wide balance that planning and the general ledger rely on. Every data element gets exactly one owner, the other system keeps a read-only copy fed by transactions, and a daily reconciliation at item, site, lot and status level proves the copies still agree.

Most pages that rank for “ERP vs WMS” compare the two products and help you decide whether you need a WMS at all. This field note assumes you already run both, or an ERP plus a third-party warehouse, and need to decide who owns each number, how changes travel between the systems, and how to catch drift before it reaches a customer promise or a month-end close.

What “system of record” means when two systems hold inventory

The system of record for a data element is the one system allowed to create or change it. Every other copy is derived from that system’s transactions and is never edited where it lives.

“Inventory” is not one data element. It is a dozen or more: the item and its units of measure, the bin it sits in, the lot and expiry date on the label, its status (available, on hold, damaged), the order it is promised to, what it cost and what it is worth. A WMS and an ERP each need most of these, but they need them for different jobs, so ownership has to be assigned element by element rather than system by system.

Two records are really in play:

  • The physical record answers where the stock is, what state it is in and how many units sit in each location. Scans and warehouse tasks change it, many times an hour.
  • The financial and commercial record answers what the stock is worth, which orders it is committed to and what the business can promise next week. Purchasing, sales, planning and accounting change it.

For each data element, ask four questions before you draw any interface:

  1. Which system creates it, and at which event?
  2. Which system may change it, and who in the business approves the change?
  3. Which other systems need a copy, and how fresh must that copy be?
  4. What happens downstream if the copy is late or wrong?

The international data quality standard for master data takes the same field-level view. ISO 8000-100:2016 says its series addresses master data quality “from the bottom up, i.e. from the smallest meaningful element, the property value” and “at the interface of master data management systems, not within the systems.” That is a useful frame for ERP and WMS work: the decisions that matter are made per field, at the boundary where one system hands data to the other.

The ownership matrix: who owns each inventory data element

The WMS owns everything a scanner can observe, and the ERP owns everything that involves money, customers or suppliers. The matrix below applies that rule to the elements that usually cause arguments. It is a starting position for a distributor or manufacturer running its own warehouse, not a law; where your business differs, change the row and write down why.

Data element System of record Copy held by How the copy is updated
Item number, description, item type ERP WMS Item create or change message, sent before the first receipt
Units of measure and conversions (each, inner, case, pallet) ERP WMS Same item message; conversion changes scheduled, never made ad hoc while stock exists
Item dimensions and weights ERP (or a product data system that feeds it) WMS, TMS, shipping software Item message; measurements taken in the warehouse go back as a change request
Lot, serial and expiry control flags ERP WMS Item message; the flag decides whether the WMS must capture a lot at receipt
Sites and warehouses ERP WMS One-time setup
Zones, aisles, bins and location types WMS ERP only if it values stock by storage location Usually not sent; the ERP sees site totals
On-hand by bin and license plate WMS Nobody, or a reporting copy Not synced to the ERP at this level
On-hand quantity by item, site, lot and status WMS ERP Transactions: receipts, shipments, adjustments, status changes
Lot numbers and expiry dates of received goods WMS (captured at receipt) ERP Carried on the receipt transaction
Lot numbers of goods you produce ERP or production system WMS Carried on the production receipt or put-away task
Inventory status (available, QC hold, damaged, quarantine) WMS ERP Status change transaction, even when quantity does not change
Sales orders, transfer orders, purchase orders ERP WMS, as shipment and receipt orders Order release message
Allocation of stock to an order at site level, available to promise ERP None Calculated in the ERP from on-hand, status and open orders
Allocation of specific bins, license plates and lots to a pick WMS ERP sees the result Shipment confirmation lists what actually shipped
Unit cost, valuation, inventory accounts ERP None Never leaves the ERP
Inventory adjustments (count, damage, found, scrap) WMS for the physical change and reason; ERP for the financial posting ERP Adjustment transaction with a reason code
In-transit stock between your own sites ERP Destination WMS, as an expected receipt Transfer shipment at origin, receipt at destination
Cycle count schedule and count results WMS ERP receives net adjustments only Count adjustment transaction
Which way each kind of inventory data travels ERP financial record Item master and UoM Cost and valuation Orders and transfers Site totals and ATP Transfers in transit WMS physical record Bins and locations On-hand by bin, LPN Lot, serial, expiry Inventory status Pick allocations Items and UoM Orders to ship or receive Receipts Shipments Adjustments with reasons Status changes Daily reconciliation: item, site, lot, status
How the ownership matrix in this article moves data. Black arrows are transactions; the red loop is the daily comparison. Example basis: the matrix above, for a business running its own warehouse.

Master data flows down from the ERP

Items, units of measure, lot and serial control flags and dimensions start in the ERP because purchasing, costing, pricing and planning all depend on them. The WMS receives them and does not edit them. When the warehouse measures a carton and finds the case weight is wrong, the correction goes back to the item owner as a change request, and the corrected value comes down again with the next item message.

The one rule that saves the most pain is about unit-of-measure conversions. If the ERP says a case holds 12 and the WMS says 24, every receipt, pick and adjustment converts wrongly in one direction, and the error looks like shrink. Our article on item master data readiness covers how to verify these values before go-live; this article only fixes who owns them.

Physical facts flow up from the WMS

Anything a scanner sees belongs to the WMS: the bin, the license plate number (LPN), the lot and expiry printed on the case, the quantity counted and the status after an inspection. These facts reach the ERP only as transactions: a receipt, a shipment, an adjustment, a status change. Nobody types an on-hand quantity into the ERP for a site the WMS controls.

The ERP usually holds on-hand at item, site, lot and status level, not by bin. That is enough for planning, costing and lot-level traceability queries. Bin-level detail stays in the WMS, where it changes too often to be worth copying.

Commitments split at the site line

Allocation causes the most confusion because both systems allocate, at different levels. The ERP commits stock at the site level when it confirms a customer order or calculates available to promise (ATP), the quantity it can still promise from on-hand and expected supply. The WMS then chooses which bins, license plates and lots fill that order when it builds pick work.

Keep those two decisions apart. The ERP should never pick a bin, and the WMS should never accept or reject a customer order. The shipment confirmation closes the loop by telling the ERP which lots and quantities actually left.

Value never leaves the ERP

Unit cost, inventory valuation and the general ledger accounts belong to the ERP. The WMS does not need them to move a pallet, and sending them creates a second place where someone can believe a number. The exception is a WMS that bills storage and handling, as a 3PL’s does; even then, the billing rates are the 3PL’s commercial data, not your inventory valuation.

Where the matrix usually changes

Three situations move rows, and each should be decided on purpose rather than discovered:

  • Line-side stock in manufacturing. Once the WMS delivers components to a production line, someone has to own them until they are consumed. If the ERP or a production system backflushes consumption from finished output, line-side stock is usually handed to the ERP at delivery, and the WMS stops tracking it by bin. If operators scan each issue, the WMS can keep it. Either works; a line location that both systems decrement does not.
  • An ERP with its own warehouse module at another site. Ownership is decided per site. Site 1 may run the ERP’s warehouse module, where the ERP is the physical record too, while site 2 runs a separate WMS. The matrix gets a “site” column, and reports that add the sites together must know which source each figure came from.
  • Consigned or customer-owned stock. When you hold goods you do not own, the physical record is still the WMS, but valuation stays off your books. An owner dimension on every on-hand record, and in every message, keeps the quantities from leaking into your own available stock.

What goes wrong when ownership is unclear

When two systems both believe they own a number, the business sees negative on-hand, double-counted adjustments, phantom available stock and lots that cannot be traced. The symptom usually appears in the ERP, while the cause sits in the interface or in a manual edit made on the wrong side.

Symptom Usual cause Ownership fix
ERP on-hand goes negative while the warehouse has stock Shipment confirmed in the WMS before the matching receipt reached the ERP, or an ERP-side manual adjustment WMS-controlled sites block manual on-hand edits in the ERP; the interface posts in event order
Adjustment appears twice in the ERP A snapshot overwrote the ERP quantity and the adjustment transaction was also posted Post transactions only; use snapshots for comparison, not for posting
Customer promised stock that is on QC hold Status changed in the WMS but only quantity changes are sent Send status changes as transactions even when quantity is unchanged
Recall query cannot say which customer got lot L-0417 Lot captured in the WMS but stripped from the shipment confirmation Shipment confirmation carries lot and quantity per line
Variance that looks like shrink on every receipt Case pack differs between ERP and WMS ERP owns conversions; WMS rejects receipts for items with no conversion
Cycle count posted in the WMS never reaches the ERP Adjustment message failed with no error queue owner Every interface has a named owner, an error queue and a replay

Negative on-hand deserves its own investigation, which our article on why the ERP shows negative inventory covers in detail. One lesson carries over here: settings that govern the same decision in two places produce surprises. Microsoft’s support note for Dynamics 365 Supply Chain Management explains that the location profile’s “Allow negative inventory” setting “applies only to warehouse processes, such as picking”, while item model groups that allow negative inventory “affect all processes” and the location profile “won’t override the setting.” If precedence is that subtle inside one product, it is worse across two, so the ownership document should state which system’s rule wins for each control.

Unclear ownership also shows up in investigations. When a count does not match, the first question is which record is wrong. If both systems can be edited, the honest answer is “either”, and the cycle count variance investigation starts from a weaker position than it should.

How ERP and WMS inventory should sync: transactions, snapshots or both

Sync inventory with transactions and prove it with snapshots. Each receipt, shipment, adjustment and status change travels from the WMS to the ERP as its own message, carrying a delta, a reason and the dimensions the ERP tracks; a periodic on-hand snapshot from the WMS is compared with the ERP but never used to overwrite it.

The three common patterns

Pattern What travels Strength Weakness Use it for
Transaction events One message per receipt, shipment, adjustment or status change Full audit trail; ERP valuation and lot history stay correct Needs ordering, duplicate protection and an error queue The normal flow for every WMS-controlled site
Periodic summary Net change per item, site and day Low volume; simple to build Loses the reason and the time of each change; weak for lot costing and recalls Rarely; only when the ERP does not need lot or reason detail
On-hand snapshot Absolute quantity per item, site, lot and status as of a time Shows drift clearly Overwriting with it hides the cause of every difference Reconciliation only

Microsoft’s documentation for running its WMS against an external ERP makes the delta rule explicit. When a counting journal changes on-hand, external systems are told through a business event, and the guidance says: “It’s important to act only on the updated quantities. Otherwise, the systems can go out of sync because of the updates.” (Microsoft Learn) The same page notes that the inventory update log publishes updates every 10 minutes by default and warns against “double updates” when the same change also arrives on a shipment receipt or packing slip.

Rules every inventory message should follow

  1. Carry a delta, not a balance. “Plus 10 of EX-20118, lot L-0417, available, at site 2” can be applied exactly once. “Site 2 now has 260” cannot be checked.
  2. Carry a unique key. Use the WMS transaction ID, so a resent message is recognized and not posted twice.
  3. Carry the event time and a sequence. The ERP should post a receipt before the shipment that consumed it, even if the messages arrive the other way round.
  4. State the unit of measure explicitly. Never let the receiver assume “each”.
  5. Include lot, serial and status whenever the item is controlled by them, and include a status change even when quantity is unchanged.
  6. Include a reason code on every adjustment, mapped to the ERP’s own reason list.
  7. Fail into a queue with an owner. A rejected message waits for a person to fix the data and replay it; it does not vanish into a log file.

Timing gaps are normal; unexplained gaps are not

The two records will rarely agree at an arbitrary moment. Stock received and put away may not post to the ERP until the receipt is closed. Picked stock may sit in a staging lane until the load is confirmed. Microsoft’s worked example shows exactly this: 10 units received in the WMS without “receiving completed” processing leave the ERP at 0 and the WMS at 10 until the receipt is completed and the external system reads it.

Example (fictional). A distributor runs its ERP against a WMS at its second site. At 2:00 p.m. the WMS receives 120 cases of EX-20118 but the receipt stays open while the last pallet is inspected. At 2:20 p.m. a cycle counter finds 2 extra cases in bin 14-03-B and posts a count adjustment, which reaches the ERP as “plus 2, reason Physical Count”. At 3:00 p.m. a nightly-style snapshot job, run early by mistake, sends “site 2 now holds 362” and the interface overwrites the ERP balance.

At 3:30 p.m. the receipt closes and the ERP posts plus 120. The ERP now shows 482 against a physical 362, because the snapshot already included the 120. Nobody can see why from the ERP alone, since the overwrite left no reason code. The fix was not a better snapshot. It was to stop posting snapshots at all, and to compare them instead.

How fresh does each copy need to be?

Freshness should follow the decision the copy supports. Order promising for same-day shipping needs status and quantity changes within minutes. Planning runs and replenishment proposals usually work from a position taken at a fixed time. Valuation needs every transaction for the period, in order, before the close, but not instantly. Write the required freshness next to each row of the ownership matrix; it is the requirement your interface has to meet.

When the warehouse belongs to a 3PL: the 940, 943, 944, 945, 947 and 846 flows

With a third-party warehouse, the 3PL’s WMS is the physical record and your ERP is the financial record, and X12 EDI usually carries the transactions between them. Receipts arrive as 944s, shipments as 945s, adjustments and status changes as 947s, and an 846 snapshot is the natural input to reconciliation.

The X12 descriptions make the division of labor clear. The X12 transaction set list says the 944 Warehouse Stock Transfer Receipt Advice “can be used by a receiving location to advise a depositor or an agent of the depositor or other business party that a transfer shipment has been received.” The 947 Warehouse Inventory Adjustment Advice “can be used to inform a warehouse/depositor or other business party of a quantity or status change to inventory records.” “Depositor” is the X12 word for the owner of the goods, which is you.

Transaction set Direction What it does in the ownership model
940 Warehouse Shipping Order Owner to warehouse ERP releases an order for the 3PL to ship
945 Warehouse Shipping Advice Warehouse to owner Tells the ERP what actually shipped; X12 says it “is used to reconcile order quantities with shipment quantities”
943 Warehouse Stock Transfer Shipment Advice Owner to warehouse Tells the 3PL what inbound stock to expect
944 Warehouse Stock Transfer Receipt Advice Warehouse to owner Confirms what was received, the receipt transaction for the ERP
947 Warehouse Inventory Adjustment Advice Warehouse to owner Adjustments and status changes, each with a reason code
846 Inventory Inquiry/Advice Warehouse to owner A position report, the snapshot for reconciliation

Mapping 947 reason codes to your ERP

In X12 version 4010, the 947 carries each adjustment in a W19 segment (Warehouse Adjustment Item Detail), whose first element is the Quantity or Status Adjustment Reason Code (element 181). The code list, as reproduced in Stedi’s X12 4010 reference, separates quantity changes from status changes, which is exactly the split the ERP needs. Your 3PL’s implementation guide decides which codes it actually sends, so map from that guide, not from the full list.

947 code (X12 4010) Meaning Typical ERP treatment
AA Physical Count Count adjustment, posted with a count reason
AU Damaged in Facility Move to damaged status or write off; may support a claim against the 3PL, depending on the warehouse agreement
AV Damaged in Transit Write-off that may support a carrier claim rather than a 3PL claim
05 Product Put on Hold Status change only; quantity unchanged, ATP reduced
55 Product Taken Off Hold Status change only; ATP restored
07 Product Dumped or Destroyed Scrap posting with approval evidence
AX Shelf-life Obsolescence Expiry write-off or move to quarantine
AG Ownership Change Transfer between owners; check it is expected

Two practical rules follow. First, codes 05 and 55 must never be posted as quantity adjustments, or available stock and on-hand stock drift apart in opposite directions. Second, the reason code decides who pays for a loss, so the mapping belongs in the requirements and is signed off by finance and the warehouse agreement owner, not left to the EDI developer. Our article on inventory adjustment reason codes covers how to design the ERP side of that list.

The 846 has a different role. X12 says it can be used “for one location to supply another location with inventory information”, which makes it the 3PL’s daily statement of position. Compare it with your ERP; do not post it. For the inbound side, your suppliers’ ship notices drive the 943 you send the 3PL, so the structure of those notices matters too; see how the EDI 856 hierarchy should match the freight. If you run or are choosing a 3PL, our third-party logistics overview lists the other interfaces in play.

A daily ERP and WMS reconciliation routine

A daily reconciliation takes both records as of the same cutoff, compares them at item, site, lot and status level, explains each difference as timing, a failed message or a true variance, and assigns each unexplained difference to a named person. It is the control that tells you the sync works, and it is the evidence an auditor asks for.

  1. Fix a cutoff. Pick a time when the warehouse is quiet, for example the end of the last shift, and record it. Both sides report as of that time.
  2. Take the WMS snapshot. On-hand by item, site, lot and status, including stock that is received but not yet closed and picked but not yet confirmed, flagged as such. Some WMS products provide this directly: Microsoft’s “Create source system on-hand inventory report” takes an “As of date” and has a parameter to “Include Registered and Picked inventory quantities”.
  3. Take the ERP position at the same cutoff, at the same level of detail.
  4. Compare line by line and list every difference with its quantity and value.
  5. Explain timing differences first. Match each difference against messages sent before the cutoff but posted after it, and against open receipts and unconfirmed shipments.
  6. Check the error queue. Failed or held messages explain the next layer of differences. Fix and replay them; do not adjust around them.
  7. Treat what remains as a true variance. Trigger a count of the affected bins rather than adjusting the ERP to match the WMS.
  8. Record and age the result. Keep the report, the explanations and who signed off. A difference still open after a set number of days escalates.
Where a 70-unit gap between ERP and WMS came from Shipments in flight 48 Failed 947 (damage) 12 Unexplained: count it 10 ERP 4,860 minus WMS 4,790 = 70 units Units of EX-20118 at site 2
Fictional example data for illustration: one item at one site after a daily reconciliation, using the categories in the routine above.

Example (fictional). At the 10:00 p.m. cutoff, the ERP shows 4,860 units of EX-20118 at site 2 and the WMS shows 4,790. The reconciliation finds two loads totaling 48 units confirmed in the WMS at 9:40 p.m. whose shipment messages posted in the ERP at 10:05 p.m., so they are timing. A damage adjustment of 12 units sits in the error queue because its reason code had no ERP mapping; the mapping is added and the message replayed.

That leaves 10 units unexplained. The analyst does not adjust the ERP. She schedules a count of the item’s three bins for the first shift, and the count result, posted in the WMS with a reason, flows to the ERP like any other adjustment.

Compare more than quantity

A quantity match can hide a status or lot mismatch, so the comparison key matters as much as the totals. Compare at least these:

  • Status. 100 available in the ERP against 90 available and 10 on hold in the WMS is a difference, even though the totals agree. It is the one that leads to promising held stock.
  • Lot and expiry. Totals can agree while lots are swapped, which only surfaces during a recall or a first-expired-first-out pick.
  • Owner, where you hold consigned or 3PL client stock.
  • Open orders. Every order released in the ERP should exist in the WMS, and every shipment confirmed in the WMS should match an ERP order. An order that left the ERP but never reached the WMS is a missed shipment waiting to happen.

A useful rule for tolerance: set it by value and by item class, not as a single unit count, and never let tolerance hide a pattern. A small difference that appears every day on the same item is a broken interface or a broken conversion, not noise. The inventory accuracy calculator helps you measure the physical side once the records agree.

Why auditors care which perpetual record you rely on

Your financial statements rely on the ERP’s inventory balance, but its quantities come from the WMS, so an auditor will want evidence that the two agree and that neither can be changed without a trail. The reconciliation routine, the message logs and reason-coded adjustments are that evidence.

The PCAOB’s auditing standard on inventories, which auditors of US public companies follow, ties the timing of count observation to the quality of the perpetual records. AS 2510 paragraph .10 says: “When the well-kept perpetual inventory records are checked by the client periodically by comparisons with physical counts, the auditor’s observation procedures usually can be performed either during or after the end of the period under audit.” Paragraph .11 allows that some companies’ controls are reliable enough “to make unnecessary an annual physical count of each item of inventory”, provided the auditor is satisfied they produce “results substantially the same as those which would be obtained by a count of all items each year.”

“Well-kept” is the operative phrase, and it is hard to claim if two systems can each edit the same balance. Three things make the claim easier to support:

  • One writable record per element. Manual on-hand edits in the ERP are blocked for WMS-controlled sites, and the block is documented.
  • A trail for every change. Each ERP inventory transaction carries the WMS transaction ID, the reason code and the user or process that caused it.
  • Retained reconciliations. Daily reports, explanations and sign-offs are kept for the audit period.

For stock held by a 3PL, AS 2510 paragraph .14 adds that when inventories are with “public warehouses or other outside custodians, the auditor ordinarily would obtain direct confirmation in writing from the custodian.” Your 846 reconciliation history makes that confirmation unremarkable. Whether cycle counts can replace a full physical inventory is a separate question with its own conditions, covered in cycle counting versus a wall-to-wall count. Private-company audits follow different standards, so confirm the requirements with your own auditor.

Ownership during a cutover, a recall and inbound transit

Ownership changes on a date, and the dangerous moments are the transitions: a new WMS going live, a recall query that needs data from both systems, and stock that has shipped from a supplier but not arrived. In each case, write down which system owns the number before, during and after the event.

At a WMS go-live

On cutover weekend, ownership of on-hand by bin moves from wherever it lived (a legacy WMS, spreadsheets, or the ERP itself) to the new WMS. The ERP stops accepting manual on-hand changes for that site at a stated time. Opening balances are loaded into the WMS by location, lot and owner, and the ERP total is reconciled to that load before the first order is released. The method is set out in our guide to moving inventory into a new WMS at go-live.

During a recall or traceability request

A traceability request usually needs records from both systems: production or purchase lots from the ERP, and which lot shipped to which customer from the WMS. If shipment confirmations dropped the lot, the answer cannot be assembled quickly. For foods on the FDA Food Traceability List, that matters because records may have to be produced as an electronic sortable spreadsheet; see what FSMA 204’s sortable spreadsheet requires and how to produce it. The ownership matrix should name which system answers each traceability question.

For stock in transit

Stock on a supplier’s truck is not in the WMS yet. The purchase order and its expected dates belong to the ERP; the ship notice becomes the WMS’s expected receipt. Transfers between your own sites are ERP-owned in transit, between the origin’s shipment and the destination’s receipt. If you need to see supplier orders before they reach the dock, read how to see inbound purchase orders before they arrive.

How to document data ownership before you build the interface

Write the ownership matrix, the message rules and the reconciliation routine down before anyone maps a field. In our engagements we start with requirements: the matrix becomes a section of the requirements document, each row is tested before go-live, and the routine is handed over in the runbook so your team can run it.

A practical sequence:

  1. List every interface that touches inventory, including spreadsheets and manual uploads. The integration inventory worksheet gives you the columns.
  2. List the data elements each interface carries, using the matrix in this article as a starting point.
  3. Assign one owning system and one accountable person per element. Disputes get resolved here, in writing, not in production.
  4. State the required freshness for each copy, tied to the decision it supports.
  5. Define each message: delta, key, event time, unit of measure, lot, status, reason.
  6. Block writes in the wrong place. Remove ERP permissions for manual on-hand edits at WMS-controlled sites.
  7. Define the reconciliation: cutoff, level of detail, categories, tolerance by value, escalation age.
  8. Test it with real scenarios: a receipt closed late, a status hold, a failed message, a duplicate.

Checklist before go-live:

  • Every row of the matrix has one owner and a named person.
  • Unit-of-measure conversions match in both systems for every active item.
  • Status changes travel even when quantity does not change.
  • Every adjustment carries a reason code that maps to an ERP reason.
  • Each interface has an error queue, an owner and a replay function.
  • The first reconciliation has been run on test data and explained to zero.

If you want help putting this into a requirements document, how we work describes the stages, and our ERP, WMS and TMS integration service builds and documents the interfaces themselves. The other field notes in the integrations hub cover the messages in more depth, and you can contact us to talk through your own matrix.

Working on this problem?

If this field note describes a process you need to fix or build software around, tell us about it. We start with your process, your systems and your deadline.