Request for information

nutrab2b.sourcing.rfi_issued.v2 · Sourcing

Purpose: Ask suppliers about capability, certifications and documents before an RFQ.
When to send: New sourcing project.
Sender → receiver: Buyer → Supplier
Expected responses: ACK
Equivalent standards: -
Scenarios using it: -

Fields and mappings

Field	Type	Req	Description
rfi_id	string	yes	RFI id
respond_by	date	yes	Respond by
questions	array<object>	yes	Questions
q_id	string	yes	Question id
text	string	yes	Question
required_docs	array<string>		Documents requested (doc_type codes)

Business rules

None beyond schema and code lists.

Example

{
  "specversion": "2.0",
  "id": "evt-rfi-RFI-1",
  "type": "nutrab2b.sourcing.rfi_issued.v2",
  "source": "urn:gln:0614141000012:erp",
  "subject": "RFI",
  "time": "2026-11-02T09:00:00Z",
  "datacontenttype": "application/json",
  "dataschema": "https://nutrab2b.org/schemas/2.0/RFI.json",
  "sender": {
    "gln": "0614141000012"
  },
  "receiver": {
    "gln": "4012345000009"
  },
  "correlationid": "CONV-RFQ-1001",
  "idempotencykey": "RFI:RFI:1",
  "sequence": 1,
  "env": "test",
  "data": {
    "rfi_id": "RFI-300",
    "respond_by": "2026-11-15",
    "questions": [
      {
        "q_id": "Q1",
        "text": "Provide GACP evidence for ashwagandha root",
        "required_docs": [
          "AUDIT",
          "SPEC"
        ]
      }
    ]
  }
}

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