Transport status
nutrab2b.logistics.transport_status.v2 · Logistics & customs
- Purpose
- Real-time milestones and exceptions from carriers and IoT loggers.
- When to send
- Milestone or sensor event.
- Sender → receiver
- Carrier / logistics provider → Buyer and supplier
- Expected responses
- none
- Equivalent standards
- X12: 214 · EDIFACT: IFTSTA · EPCIS: ObjectEvent departing/arriving + sensorElementList
- Scenarios using it
- Full order-to-cash · Cold-chain excursion
Fields and mappings
| Field | Type | Req | Description | Code list / format | EDI / GS1 / SAP mapping |
|---|---|---|---|---|---|
| asn_id | string | yes | Shipment | ||
| status | string | yes | Status | transport_status | |
| at | datetime | yes | When | ||
| location_unlocode | string | UN/LOCODE | ^[A-Z]{2}[A-Z2-9]{3}$ | ||
| celsius | number | Temperature °C | |||
| note | string | Exception detail |
Business rules
- NB-R020 Cold-chain excursion, temperature readings outside the storage class range.
Implementation notes
- Send the ASN when goods leave, before they arrive; one ASN per physical shipment.
- Pallet → case hierarchy uses parent_sscc; contents sit on the lowest level only.
- Every lot needs a passing CoA (or approved deviation) before shipping (NB-R003).
Example
{
"specversion": "2.0",
"id": "evt-transport_status-ASN-9001-1",
"type": "nutrab2b.logistics.transport_status.v2",
"source": "urn:gln:0614141000012:erp",
"subject": "ASN-9001",
"time": "2026-11-02T09:00:00Z",
"datacontenttype": "application/json",
"dataschema": "https://nutrab2b.org/schemas/2.0/TRANSPORT_STATUS.json",
"sender": {
"gln": "0614141000012"
},
"receiver": {
"gln": "4012345000009"
},
"correlationid": "CONV-RFQ-1001",
"idempotencykey": "TRANSPORT_STATUS:ASN-9001:1",
"sequence": 1,
"env": "test",
"data": {
"asn_id": "ASN-9001",
"status": "CUSTOMS_CLEARED",
"at": "2026-11-30T11:00:00-08:00",
"location_unlocode": "USSFO"
}
}Mapping checklist
- Every required field populated from your system of record
- Coded fields mapped to the Bodylia OpenB2B code lists
- GLN, GTIN and SSCC check digits validated
- Rules above pass in the validator
- Idempotency key and per-subject sequence generated
- Expected responses, including rejections, handled
