Deviation request

nutrab2b.quality.deviation_decided.v2 · Quality & compliance

Purpose: Request and record approval to ship or use material outside specification, with conditions and expiry.
When to send: OOS result where use may still be acceptable.
Sender → receiver: Supplier (request) / buyer (decision) → Counterparty
Expected responses: ACK
Equivalent standards: -
Scenarios using it: Out-of-spec lot ships under deviation

Fields and mappings

Field	Type	Req	Description	Code list / format
deviation_id	string	yes	Deviation id
lot_number	string	yes	Lot
analyte	string	yes	Parameter	analyte
requested	string	yes	What deviates and by how much
decision	string	yes	requested \| approved \| rejected	^(requested\|approved\|rejected)$
conditions	string		Conditions of approval
valid_until	date		Approval valid until

Business rules

None beyond schema and code lists.

Example

{
  "specversion": "2.0",
  "id": "evt-deviation-ASH-26-121-1",
  "type": "nutrab2b.quality.deviation_decided.v2",
  "source": "urn:gln:4012345000009:erp",
  "subject": "ASH-26-121",
  "time": "2026-11-02T09:00:00Z",
  "datacontenttype": "application/json",
  "dataschema": "https://nutrab2b.org/schemas/2.0/DEVIATION.json",
  "sender": {
    "gln": "4012345000009"
  },
  "receiver": {
    "gln": "0614141000012"
  },
  "correlationid": "CONV-RFQ-1001",
  "idempotencykey": "DEVIATION:ASH-26-121:1",
  "sequence": 1,
  "env": "test",
  "data": {
    "deviation_id": "DEV-19",
    "lot_number": "ASH-26-121",
    "analyte": "LOD",
    "requested": "LOD 6.2% vs ≤ 6.0%",
    "decision": "approved",
    "conditions": "Use within 6 months; store DRY",
    "valid_until": "2027-06-30"
  }
}

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