ERP records the order. The warehouse management system, or WMS, records picking and dispatch. The serialization platform maintains product identities and related events. Their responsibilities vary by implementation, so an investigation should begin with the agreed data flow.
When records disagree, use one affected shipment to establish where the source activity and its electronic record first diverged.
Compare equivalent records
Confirm that each system refers to the same order, delivery, shipment, or receipt. Check units of measure, partial deliveries, cancellations, returns, and the time of the latest update.
Ten cases and 240 packages can describe the same quantity if each case contains 24 packages. Matching totals still does not establish that the correct serial numbers were assigned to that shipment.
Preserve original identifier values during comparison. Formatting changes can remove meaningful characters from product codes, lots, or serial numbers.
Trace the transaction through each handoff
Collect the source document references, scans, original payloads, transformations, message identifiers, processing results, and timestamps.
Distinguish the time of the physical event from the time the event reached a repository. EPCIS defines separate event and recording times. See the GS1 EPCIS standard.
Use the evidence to test possible causes:
- A mapping used the order quantity instead of the final shipment quantity.
- Case quantities were converted incorrectly.
- Rework changed a case’s contents without updating the relevant records.
- The message arrived, but the receiving application rejected it.
- A retry created duplicate processing.
These are investigation paths, not conclusions about every discrepancy.
Follow packaging changes
If one damaged package is removed from a case and replaced, the total quantity may stay the same while the serial numbers change. Confirm that both the physical operation and revised packaging relationship were captured and communicated.
EPCIS aggregation events can describe packages being added to or removed from a parent container. Use the event model agreed for the interface and supported by the connected applications.
Correct the source and check downstream recovery
Identify the authorized correction, affected recipients, and required processing sequence. Preserve the original evidence, reason, approval, and resulting responses. Confirm duplicate handling before resubmitting information.
An erroneous record and a genuine later activity need different treatment. EPCIS provides error declarations for erroneous events; a real return after a valid shipment is a later business event. Agree the supported correction process with the recipient.
Keep the data investigation connected to inventory decisions. FDA’s enhanced security guidance discusses reconciling shipped and received product with tracing information and handling discrepancies. See Sections V.B through V.D.
Illustrative scenario: one order, two deliveries
An order for 240 packages is fulfilled through two deliveries of 120. The interface selects all serial numbers associated with the order and reports 240 against the first delivery.
The investigation identifies selection logic that did not restrict the records to the confirmed delivery. The team reconciles the actual serial numbers for each shipment, coordinates the appropriate corrections, and tests partial deliveries, short picks, and shipment changes.
The Hakile team helps investigate differences across ERP, WMS, and serialization platforms, covering data ownership, mappings, event analysis, and controlled recovery.