INDUSTRY FIELD GUIDE
Courier return and redelivery records for AI traceability
A package can come back to the dispatch point after an unsuccessful attempt.
NAICS 492110 · Couriers and Express Delivery Services
NAICS 492210 · Local Messengers and Local Delivery
A package can come back to the dispatch point after an unsuccessful attempt. A later label may refer to that same parcel. GS1’s event guidance supports tracking what was observed and where. An approved logistics capture program may seek other evidence, such as a staging demonstration. Agree separately on any filmed task. GS1 EPCIS guidance · micro1 robotics data offer
Prepare a mock parcel, two training labels, and an event sequence with an attempt, a return handoff, and a new dispatch. Include a proposed redelivery with no scan to confirm it. Ask the model where custody was last confirmed and whether the labels refer to one parcel or two. For a visual sample, use an unbranded training package and keep the same object ID through the transition.
Use fictional addresses or none. Exclude recipient details, proof-of-delivery images, precise routes, private dispatch communications, and contractor identifiers. Obtain permission from partners if using real records.
Describe a parcel custody exercise
Original Fiund exercise
A relabeled returned parcel remains one object, while proposed redelivery adds no custody event
An unbranded training parcel uses original nonfunctional labels and a wholly fictional event log. There is no address, recipient, delivery image or live dispatch.
| Record | Source | What it records |
|---|---|---|
| CPR1 | Original dispatch and attempt | Object O1, label L1 dispatched from mock depot D. Attempt marked unsuccessful, no recipient receipt. |
| CPR2 | Return and relabel | D acknowledges O1 returned. Approved original crosswalk replaces label L1 with L2 on the same O1; no second parcel created. |
| CPR3 | Later plan | Redelivery proposed for L2. No new dispatch scan or receiving event. Another object's L2-like scan has different full ID O2. |
Question for the model
Where is O1's custody last confirmed, how many parcels do L1 and L2 represent, and is redelivery established?
Show the reference answer and checks
CPR2 confirms O1's return to depot D and explicitly links L1 and L2 as successive labels on one object. CPR3's redelivery is only a proposal, with no later dispatch or receipt for O1; the O2 near-match cannot advance its history. Report D as the last confirmed custody point and preserve the unsuccessful attempt separately. Two labels do not imply two parcels or completed redelivery.
- Counting relabeled returned items as separate parcels.
- Treating a redelivery proposal or another object's similar label as a new custody event.
Fields to preserve
- Stable object ID and label crosswalk
- Preserves identity.
- Attempt, return and dispatch event types
- Separates stages.
- Custody acknowledgment and planned state
- Supports the last-confirmed location.
Test another case
Add an O1 dispatch under L2 with no final receipt. Require custody progression to be reported without calling it delivered.
Use original props and logs. Exclude recipients, routes, contractor IDs and private messages; partner-controlled real records require permission.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.