Identity, product, location, status, linked order, container and last observation for this individual unit.
AUR-25-COG · EPC …9B31
Traceability and supply chain
Know where each item has been and who handled it.
Each item keeps the same identity from receiving to handover. Recorded steps add the location, person and time to its history. Handovers stay open until the partner confirms them.
AUR-25-COG · EPC …9B31
- Receiving Registered INB-1038 · label printed Recorded in Beam
- B-11 Put away Receiving → Rack B · B-11 Recorded in Beam
- ORD-30425 Picked In stock → Picked Recorded in Beam
- Carrier Handed over Confirmation missing Follow-up: Dispatch
01 The problem
A code alone does not tell you what happened.
You need to connect each item to its movements, locations and the people responsible, including after it leaves the warehouse.
- 01 It is unclear exactly which item was handed over.
- 02 History stops at a location or system boundary.
- 03 Partners see different versions of events, and no one owns the exceptions.
02 The process
One sofa, four handovers.
↓ Scroll to follow the process
01 / 04
Register the item
Label printerOn receipt, the sofa gets its own code and label. From now on, every record is linked to this individual unit.
Registered on receipt
02 / 04
Follow it through the warehouse
RFID handheldPlaced at B-11 and seen during the count. Each step records a name and time, with no extra action.
Warehouse history
03 / 04
Hand it over
BarcodeThe sofa is picked for ORD-30425 and handed over at the destination. Beam records the handover and waits for the partner to confirm it.
From pick to handover
04 / 04
Spot an unconfirmed handover
Confirmed in the appThe carrier's confirmation is missing. Beam does not assume it happened: the handover stays open, with dispatch responsible for following up.
Where the chain stops
Three handovers are recorded in Beam, with a place, person and time. The fourth, to the carrier, awaits partner confirmation. Follow-up: dispatch.
AUR-25-COG · EPC …9B31Manchester distribution centre
Starting point 123 Confirmation missing Carrier INB-1038 · label printedB-11 · seen during countORD-30425 · handed over
Handovers recorded1 of 4
Without confirmation0
Orange pin = agreement without confirmationFictional example · schematic view
03 In the app
What each item’s history shows
AUR-25-COG · EPC …9B31
AUR-25-COG · EPC …9B31
AUR-25-COG · EPC …9B31
AUR-25-COG · EPC …9B31
- Order system
- Order, customer and delivery addressProvides the outbound order
- Beam
- Identity, location, status and work recordsReports a completed pick when the integration supports it
- Carrier
- Delivery confirmationConfirmation has not yet been agreed
04 Outcome
What each handover tells you
- Exactly which item was processed?
- Where was it, and in what state?
- Which order, container or handover did it belong to?
- Who was responsible for the event?
- Where is the history or data exchange incomplete?
05 Fit
When this solution fits
- You need each item’s history for daily work or to meet contractual requirements.
- Goods pass through multiple locations, organisations or supply chain partners.
- Your existing systems do not show clearly what was done or where something went wrong.
A supply chain needs a defined setup, not a switch: shared identifiers, agreed handover points, one owner per data field and visible exceptions must be agreed and verified for each handover. A fixed read zone is a configured checkpoint, never automatic tracking of every movement. Beam does not promise a signed audit trail or complete supply chain visibility.
Follow your items from one handover to the next.
In the demo, we follow an item between two locations or through a handover to a partner, and agree who records each step.