Hold / release

nutrab2b.quality.hold_changed.v2 · Quality & compliance

Purpose: Place a lot on hold or release it; blocks shipment while held.
When to send: QA decision.
Sender → receiver: QA (any party) → Partners holding stock
Expected responses: ACK
Equivalent standards: EPCIS: ObjectEvent holding/releasing
Scenarios using it: Hold blocks shipment until release

Fields and mappings

Field	Type	Req	Description	Code list / format
lot_number	string	yes	Lot
action	string	yes	hold \| release	^(hold\|release)$
reason	string	yes	Reason	hold_reason
note	string		Note

Business rules

None beyond schema and code lists.

Example

{
  "specversion": "2.0",
  "id": "evt-hold-ASH-26-118-1",
  "type": "nutrab2b.quality.hold_changed.v2",
  "source": "urn:gln:0614141000012:erp",
  "subject": "ASH-26-118",
  "time": "2026-11-02T09:00:00Z",
  "datacontenttype": "application/json",
  "dataschema": "https://nutrab2b.org/schemas/2.0/HOLD.json",
  "sender": {
    "gln": "0614141000012"
  },
  "receiver": {
    "gln": "4012345000009"
  },
  "correlationid": "CONV-RFQ-1001",
  "idempotencykey": "HOLD:ASH-26-118:1",
  "sequence": 1,
  "env": "test",
  "data": {
    "lot_number": "ASH-26-118",
    "action": "release",
    "reason": "QA_PENDING"
  }
}

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