Purchase order cancellation

nutrab2b.order.cancelled.v2 · Ordering

Purpose: Cancel a whole PO. Rejected if goods already shipped (cancel race).
When to send: Buyer cancels.
Sender → receiver: Buyer → Supplier
Expected responses: ACK
Equivalent standards: X12: 860 (BCH01=01) · EDIFACT: ORDCHG (BGM 1225=1)
Scenarios using it: Cancel race after shipment

Fields and mappings

Field	Type	Req	Description	Code list / format	EDI / GS1 / SAP mapping
po_number	string	yes	PO
reason	string	yes	Reason	cancel_reason

Business rules

None beyond schema and code lists.

Example

{
  "specversion": "2.0",
  "id": "evt-po_cancel-PO-55012-1",
  "type": "nutrab2b.order.cancelled.v2",
  "source": "urn:gln:0614141000012:erp",
  "subject": "PO-55012",
  "time": "2026-11-02T09:00:00Z",
  "datacontenttype": "application/json",
  "dataschema": "https://nutrab2b.org/schemas/2.0/PO_CANCEL.json",
  "sender": {
    "gln": "0614141000012"
  },
  "receiver": {
    "gln": "4012345000009"
  },
  "correlationid": "CONV-RFQ-1001",
  "idempotencykey": "PO_CANCEL:PO-55012:1",
  "sequence": 1,
  "env": "test",
  "data": {
    "po_number": "PO-55012",
    "reason": "BUYER_DEMAND"
  }
}

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