Core Module Receiving Event

Receiving events record products arriving at a physical location after being shipped from another location.

Event Profile

Core receiving events are identified by the following characteristics.

KDE

Value

type

ObjectEvent

action

OBSERVE

bizStep

receiving

A core receiving event does not carry a required disposition. If you want to record the business state of the goods after receipt, the value must come from the CBV disposition vocabulary. The full controlled list is published at https://ref.gs1.org/cbv

KDE Requirements

The following KDEs are required on the root of a core receiving event.

KDE Description Example Value
eventID A URN formatted universally unique ID (UUID) urn:uuid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
epcList The EPCs of the products or logistical units being received. Used when product is traced at instance level urn:epc:id:sgtin:0614141.107346.0001
quantityList The EPCs and quantity of the product being received. Used when product is traced at lot level (epcClass, quantity, and uom elements should be included) { "epcClass": "urn:gdst:example.org:product:lot:class:examplePrefix.wildfish.lot2", "quantity": 9876, "uom": "KGM" }
eventTime A string value formatted as an ISO datetime 2026-01-01T00:00:00.000Z
eventTimeZoneOffset The time zone offset in effect at the time and place the event occurred, expressed as an offset from UTC +00:00
bizLocation A URN formatted GLN or GDST location identifier validated as a GLN with related master data urn:epc:id:gln:1234567890123, urn:gdst:example.org:location:loc:examplePrefix.0

Source List Requirements

The location must be set on the source list. The source list is an array property of objects that have a type and source property. Entries in sourceList tie the shipment to originating locations and product owners.

KDE Description Example Value
type Indicates what is identified by the value. On a core event, the location urn:epcglobal:cbv:sdt:location
source A GLN or GDST location identifier urn:epc:id:sgln:08600031303.0.0, urn:gdst:example.org:location:loc:example_prefix.0

Example

 [ 
              { 
                  "type": "location", 
                  "source": "urn:gdst:traceability-solution.com:location:loc:0048000.fishing_vessel" 
              } 
          ] 

Destination List Requirements

The location must be set on the destination list. The destination list is an array property of objects that have a type and source property. Entries in destinationList tie the shipment to destination locations and product owners.

KDE Description Example Value
type Indicates what is identified by the value. On a core event, the location urn:epcglobal:cbv:sdt:location
destination A GLN or GDST location identifier urn:epc:id:sgln:08600031303.0.0, urn:gdst:example.org:location:loc:example_prefix.0

Example

 [ 
              { 
                  "type": "location", 
                  "destination": "urn:gdst:traceability-solution.com:location:loc:0048000.fishing_vessel" 
              } 
          ] 

Full JSON Example

{
              "@context": [
                  "https://ref.gs1.org/standards/epcis/epcis-context.jsonld",
                  {
                      "gdst": "https://traceability-dialogue.org/epcis"
                  }
              ],
              "type": "ObjectEvent",
              "eventTime": "2026-04-19T12:08:41.6112327+00:00",
              "eventTimeZoneOffset": "+00:00",
              "eventID": "urn:uuid:1178d826-cf72-41de-a2a8-9bc8baad6c03",
              "epcList": [],
              "action": "OBSERVE",
              "bizStep": "receiving",
              "bizLocation": {
                  "id": "urn:gdst:example.org:location:loc:solution.processorplant"
              },
              "quantityList": [
                  {
                      "epcClass": "urn:gdst:example.org:product:lot:class:solution.wildfish.lot2",
                      "quantity": 9876,
                      "uom": "KGM"
                  }
              ],
              "sourceList": [
                  {
                      "type": "location",
                      "source": "urn:gdst:example.org:location:loc:solution.port"
                  }
              ],
              "destinationList": [
                  {
                      "type": "location",
                      "destination": "urn:gdst:example.org:location:loc:solution.processorplant"
                  }
              ]
          }
This article documents what the Core requires, kept commodity-agnostic. A seafood document also carries additional fields on this event, such as read point, certifications, product owner, and the source and destination owning party; their requirements are described in the Seafood Module articles.


How did we do?

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)