INDUSTRY FIELD GUIDE
Less-than-truckload cross-dock records for AI traceability
At a cross-dock, a carton can move to another pallet while its shipment identity stays the same.
NAICS 484122 · General Freight Trucking, Long-Distance, Less Than Truckload
At a cross-dock, a carton can move to another pallet while its shipment identity stays the same. GS1’s EPCIS guidance addresses how to represent business events and relationships. A carrier can show how to evaluate parentage with synthetic scan events and reviewer-confirmed membership. GS1 EPCIS guidance · Scale AI Data Partnerships
Make two mock pallets and four cartons. Give one carton a confirmed removal and a later addition to a new pallet. Add a receiving scan that mentions the carton without confirming aggregation. Ask the model where each carton belongs at a specified time and which event changed the relationship. Use an unresolved example where only the departure scan exists.
Protect shipper and consignee records, customer-specific scan formats, rates, commodity details, and cross-dock layout. Use demo labels and fictional scans when several operators own parts of the evidence.
Describe a cross-dock records exercise
Original Fiund exercise
A receiving scan does not itself place a carton on a new pallet
Two mock pallets and four original carton aliases form a synthetic event graph. No shipper, consignee, commodity, rate or cross-dock layout is included.
| Record | Source | What it records |
|---|---|---|
| LP1 | Starting aggregation | Pallet A contains C1 and C2; pallet B contains C3 and C4. Original membership event supplied. |
| LP2 | C2 reparenting | At 10:00 confirmed removal from A; at 10:05 confirmed addition to B. C2 shipment identity unchanged. |
| LP3 | C1 exception | At 10:10 confirmed removal from A, then receiving scan C1 at 10:12. No pallet-addition or current-parent event supplied. |
Question for the model
At 10:15, which pallet memberships are supported, and can C1's receiving scan establish B as its parent?
Show the reference answer and checks
LP1 and LP2 place C2 with C3 and C4 on B at 10:15. C1 has been removed from A under LP3 but has no confirmed new parent; its receiving scan is not an aggregation event. A therefore has no remaining listed carton in this fixture, while C1's current pallet remains unresolved. Preserve object identity separately from changing parentage rather than infer membership from general receipt at the facility.
- Treating a receiving scan as confirmation of pallet aggregation.
- Leaving a carton on its old pallet after a confirmed removal or changing its shipment identity during a parent move.
Fields to preserve
- Carton and shipment identity
- Preserves the object.
- Parent pallet and add/remove event
- Defines membership.
- Effective time and missing aggregation
- Supports the as-of graph.
Test another case
Add C1 to pallet B at 10:20. Require the 10:15 answer to remain unassigned while a later query includes the new membership.
Use original demo labels and fictional scans. Exclude customer-specific formats and facility layouts; several operators may control real evidence.
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.