Key takeaway
Track the goods and their container relationships over time. A shipment or pallet scan may support an inference, but it should not be presented as direct observation of every item.
The question is which goods moved together
A warehouse history may contain receiving scans, packing events, container movements and shipping confirmations. Before combining them, choose the question: which identified cases were associated with which container at each event? A current contents list cannot necessarily reconstruct a past pallet. Make additions and removals visible, and state where the archive only records the parent container.
GS1’s EPCIS/CBV implementation guideline describes aggregation and disaggregation relationships. The EPCIS standard also distinguishes the event’s asserted occurrence time from repository recording time. These are useful modeling references, not a certification that your warehouse has captured every event or authority to sell the resulting history.
A split pallet exposes an otherwise hidden gap
This hypothetical timeline uses local illustrative identifiers. Four cases, C1–C4, arrive associated with pallet P10. C1 and C2 are removed and packed onto P20. A later shipping observation records P20 alone. Still later, an internal scan finds C2 in storage. The final observation conflicts with the assumed shipping membership and requires reconciliation.
The table is a reader’s field map, not an EPCIS message or standard-conformant payload. It makes the inference auditable: shipping P20 does not constitute a separate direct scan of C1 and C2. A missing unpacking event, an incorrect packing entry or a later return are different explanations. None should be silently chosen without evidence.
| Sequence | Recorded relationship | Review label |
|---|---|---|
| 1: receive | P10 associated with C1–C4 | Membership observed in this illustrative record |
| 2: split | C1 and C2 removed from P10 | Old membership ended for these cases |
| 3: pack | C1 and C2 associated with P20 | New membership recorded |
| 4: ship | P20 observed leaving; no case scans | Case movement inferred from membership |
| 5: reconcile | C2 observed in storage; timing documented | Conflict unresolved; check correction or return history |
Write down the inference conditions
GS1’s guideline explains that inferring child presence from a parent depends on the recorded aggregation and intervening disaggregation history. In an internal review, ask whether you have that intervening history for the proposed period. If the archive retained only packing and shipping, a case-level conclusion may require assumptions about omitted events.
For the hypothetical conflict, keep the original shipping assertion and the later contradictory observation in the review record. Record what the operations owner checked and whether the relationship is corrected, remains uncertain or is explained by a subsequent return. A tidied summary that removes the conflict would make the archive appear more certain than the evidence warrants.
Time and custody need separate labels
Keep event time and system recording time distinguishable when they both exist. A late entry can otherwise make a receiving or shipping sequence appear reversed. Document time zones and known clock or migration issues in the dictionary. If occurrence time is absent, say so rather than copying an import timestamp into that field.
A movement observation is also different from a change in legal ownership. For this review, use explicit fields such as “physical movement recorded,” “custody party recorded” and “ownership transfer not assessed.” Do not infer a legal transfer just because a pallet crossed a loading dock. The intended evaluation may need only event relationships, while contracts and commercial terms remain outside the technical map.
Reduce disclosure without collapsing the relationships
If an exact customer location is unnecessary for the proposed question, consider an approved location category or alias while preserving internal joins. Review how repeated rare movements could reveal counterparties or commercial patterns. Removing a customer-name column alone does not settle those risks, and aliases should not be advertised as anonymous.
Keep raw identifiers and mapping keys in the company’s authorized environment. The initial inventory can describe case/container linkage, period, event coverage, correction history and excluded counterparties. A separate sample approval should define whether any real location, transaction reference or event detail is needed. Technical standards structure data exchange; they do not grant permission for each exchange.
A clear acceptance question saves mapping work
Ask a potential evaluator which unit matters: container movement, item movement or a reconstructed trace. State how much of the proposed answer is observed, inferred or unresolved. If it requires item-level evidence the archive does not hold, stop or narrow the scope instead of promising to reconstruct it perfectly. Use the inventory and readiness tools to assign the missing-history question before agreeing to recurring delivery. Updating a current container list will not, by itself, repair a historical gap.