Independent guidance on traceability, responsible sourcing and market accessIdentity / Events / Evidence

Interactive learning / Fictional records

Follow the relationships.

Inspect a product journey, then highlight how a suspect input can connect to more than one output.

1. Inspect the event record

Select each step. Notice that a recorded receipt can still have pending evidence.

Follow one product through four events.ILLUSTRATIVE / BATCH-B42
Who / where

Material supplier

Event time

Example · 08:10 UTC

Record / evidence

A supplier lot is recorded alongside its origin and receipt reference.

Select an event to see the relationships behind the physical movement. This is an educational example, not an EPCIS payload.

2. Trace the affected path

Input 01 is used in both outputs. Input 02 is used only in output 02. These are potentially affected paths.

Input materialMAT-A17Supplier 01
Input materialMAT-A18Supplier 02
Output batchPROD-B42Uses input 01
Output batchPROD-B43Uses both inputs
DispatchSHIP-C08Destination 01
DispatchSHIP-C09Destination 02

Two inputs, two output batches and two dispatches. Select a suspect input to highlight its downstream relationships.

Fictional relationships for demonstration. Highlighting means potentially affected, not a confirmed safety finding.

What the simplified graph leaves out

Real investigations need quantities, timestamps, rework, packing changes, uncertainty and supporting evidence. The example demonstrates the relationship logic; it does not determine a recall or implement an EPCIS schema.

Continue with manufacturing genealogy or recall traceback planning.