Inventory reconciliation is not a comparison of three numbers labeled “quantity.” A channel may show published sellable units, an OMS may show available-to-promise, and a warehouse may show physical stock by disposition. They can all be correct while differing.
Normalize the comparison
Before comparing, align:
- product identifier and pack level;
- location or fulfillment network scope;
- unit of measure;
- stock disposition;
- reservation and allocation treatment;
- event or snapshot time;
- channel caps and buffers.
Record the formula that converts each source into the intended comparable balance. Preserve raw values alongside normalized values so an operator can audit the calculation.
The available-to-promise article defines the OMS view. The inventory sync latency guide explains why timestamps and versions matter.
Choose an authoritative layer for each fact
The warehouse may own physical quantity and disposition. The OMS may own active reservations and channel allocations. A channel owns what it accepted and displays. Reconciliation should identify the layer where divergence begins, not declare one system authoritative for every field.
Use stable SKU and location mappings. Unmapped products should be an explicit exception population, not silently excluded from the report.
Work through a hypothetical comparison
At 14:00, the warehouse records 60 units: 50 sellable, five damaged and five awaiting inspection. The OMS holds 12 confirmed reservations and a three-unit buffer, producing ATP of 35. The channel displays 30 because its allocation cap is 30.
Those balances reconcile. A report that expects all three to equal 60 would manufacture a problem. If the channel still displays 40, the investigation compares the source version sent, acknowledgment and channel state to locate a stale or rejected update.
Classify differences
Useful difference classes include:
- timing or in-flight update;
- identifier or pack mapping;
- disposition mismatch;
- missing or duplicate reservation;
- unrecorded physical movement;
- stale or rejected channel publication;
- manual override;
- unexplained difference requiring count.
Assign each class an owner and safe correction path. Track both quantity impact and affected SKU-location pairs; one large discrepancy and many small ones create different operating risks.
Correct the owning fact
If the warehouse stock is wrong, investigate and use its approved count or adjustment process. If a reservation is stuck, repair its lifecycle in the OMS. If the channel is stale, publish the current authorized quantity with proper version or ordering controls.
Do not write the same adjustment into every system. That can double the correction when normal synchronization resumes. Keep a correlation ID and verify downstream convergence.
Handle reconciliation at scale
Run frequent lightweight comparisons for high-risk stock and deeper periodic reconciliations for full coverage. Keep watermarks or snapshot identifiers so every run has a clear boundary. If extracts complete at different times, adjust for events in the gap or label the comparison non-simultaneous.
Prioritize negative availability, last-unit conflicts, high-velocity items and large-value differences. A tolerance may help triage rounding or known timing effects, but it should not hide systematic errors.
Recover from a bad reconciliation run
If mappings, snapshots or formulas are wrong, stop automated corrections. Mark outputs invalid, preserve the faulty run for audit, fix the comparison logic and rerun from stable source evidence. Review any changes already applied before resuming automation.
Keep the output actionable
Each exception should show raw balances, normalized balance, difference, timestamps, formula version and the first divergent boundary. Include the owning team and proposed next diagnostic step, not an automatic adjustment. Age exceptions from the moment comparable evidence existed so a long-running mismatch cannot appear new after every scheduled run. Prioritize repeat differences as well as large ones.
A useful next step
Choose twenty SKUs across normal, reserved, damaged and recently adjusted stock. Build a timestamped bridge from physical quantity to ATP to channel publication, and explain every difference.
1Commerce can help connect inventory, order and channel operations according to configured integrations and agreed scope. Explore platform analytics or contact 1Commerce to review reconciliation controls.