Sample result

nutrab2b.sourcing.sample_evaluated.v2 · Sourcing

Purpose: Approve or reject a sample, with the lab's findings.
When to send: Sample tested.
Sender → receiver: Buyer or lab → Supplier
Expected responses: ACK
Equivalent standards: -
Scenarios using it: -

Fields and mappings

Field	Type	Req	Description	Code list / format
request_id	string	yes	Sample request
decision	string	yes	approved \| rejected	^(approved\|rejected)$
coa_ref	string		CoA id
comments	string		Comments

Business rules

None beyond schema and code lists.

Example

{
  "specversion": "2.0",
  "id": "evt-sample_result-SAMPLE_RESULT-1",
  "type": "nutrab2b.sourcing.sample_evaluated.v2",
  "source": "urn:gln:0614141000012:erp",
  "subject": "SAMPLE_RESULT",
  "time": "2026-11-02T09:00:00Z",
  "datacontenttype": "application/json",
  "dataschema": "https://nutrab2b.org/schemas/2.0/SAMPLE_RESULT.json",
  "sender": {
    "gln": "0614141000012"
  },
  "receiver": {
    "gln": "4012345000009"
  },
  "correlationid": "CONV-RFQ-1001",
  "idempotencykey": "SAMPLE_RESULT:SAMPLE_RESULT:1",
  "sequence": 1,
  "env": "test",
  "data": {
    "request_id": "SR-12",
    "decision": "approved",
    "coa_ref": "COA-ASH-26-118"
  }
}

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