Inventory, lead-time and traceability data quality
6 min read
Lesson objectives
- Reconcile movements and calculate availability without double subtraction or counting unreceived purchases.
- Distinguish first-acceptance from full-completion lead time.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A better demand forecast cannot compensate for stock that exists only on the planning screen. Physical units may also be committed to another customer, awaiting inspection, or moving between sites. Specify the item, location, quality state and time before asking for a balance. A stock balance is measured at a point in time; receipts and dispatches are flows during an interval. Adding every daily snapshot would be like adding a bank balance each morning and calling the result monthly income. Instead, explain how opening stock becomes closing stock through movements. Then identify which part of that closing stock is actually available for the decision under consideration.
For a defined item and site, closing balance equals opening balance plus physical receipts and inward transfers, minus dispatches and outward transfers, plus documented net adjustments. Convert units first. If one carton contains 12 pieces, receiving ten cartons contributes 120 pieces, not ten. Define which interval contains a boundary event so it cannot enter two periods. A practical table convention uses an inclusive start and exclusive end; the next interval starts at that same endpoint. This is a movement identity, not a forecasting model. A failure to reconcile directs attention to missing, duplicated or misclassified transactions before any demand-model parameter is changed.
GS1's EPCIS implementation guidance distinguishes event time from recording time and discusses retaining a correction trail. Apply that idea to our teaching ledger: preserve an event identifier, source, both timestamps and any link to a correction. Resending the same message does not create another physical receipt. However, two rows with the same item, quantity and approximate time are not necessarily duplicates; two genuine shipments can be equal. Compare event identifiers and receiving evidence before excluding a row. The numerical cases below use a simplified ledger rather than requiring an EPCIS installation.
| Reconciliation step | Pieces | Interpretation |
|---|---|---|
| Count both receipt messages and dispatch | 240 | 200+80+80−120 |
| Count the genuine receipt once | 160 | 200+80−120 |
| Post the evidenced scrap of 15 | 145 | 160−15 |
| Available for a new order | 85 | 145−20−40 |
State groups can overlap in another system. Sales may reserve units that are still awaiting inspection. Direct subtraction would then remove the shared units twice. If reservations total 40, inspection totals 20 and ten pieces belong to both, availability from 145 is 145−40−20+10=95. Prefer mutually exclusive states where possible; otherwise calculate the union of excluded sets rather than simply adding their sizes. A field labeled available may mean available to sell, physically present, or projected after an expected purchase receipt. Its name is insufficient evidence. Check its actual definition against the decision, especially before making a customer commitment that assumes goods can be dispatched immediately.
Transfers expose another boundary problem. Moving 20 pieces from site A to site B is neither a network sale nor a new network purchase. Site ledgers record dispatch from A and later receipt at B. Between those events, the 20 pieces are in transit. A network ownership view that includes transit retains its total, while a warehouse-only view temporarily falls by 20. Do not alter a valid movement merely to force those two reports to match. Explain their boundaries. Similarly, moving a carton from a shelf to inspection changes its state but must not add another carton to the site's physical total. Draw the measurement boundary and distinguish movements crossing it from changes occurring entirely within it.
Apply the same discipline to lead time. A purchase order is released at the start of day one. Forty pieces are accepted at the start of day four and 60 at the start of day seven. Time to first accepted quantity is three days; time to full acceptance is six. Production requiring all 100 pieces simultaneously cannot use the three-day figure without overlooking its constraint. A process that can operate in smaller batches may need the entire receipt profile instead of one lead-time number. Preserve quantity and acceptance time for each receipt. Specify whether timing begins at release or approval, and whether it ends at the warehouse gate or after inspection. Different clocks do not provide a fair supplier-speed comparison.
Never replace an unknown acceptance timestamp with zero lead time. Zero describes immediate acceptance; missing means the duration is unknown. Report the fraction of complete records alongside the lead-time summary and investigate whether missingness concentrates among delayed receipts. Omitting those cases could make the average appear faster. Normalize time zones before checking that acceptance follows release. A negative interval needs investigation, not silent inclusion in the average. When evidence establishes a late-entered or corrected date, retain the correction trail so later analysts can distinguish the reconstructed physical history from information that was actually available to the planner at an earlier decision time.
Lesson summary
Explain stock through evidenced movements, separate availability states and define the lead-time clock before comparing suppliers.