Core Module Aggregation Event
Aggregation events capture the grouping of individual products into a single logistical unit, typically for logistical purposes. Aggregation events are always reversible, meaning the products can always be separated from the logistical unit and retain their original identities.
Event Profile
Aggregation events are identified by the following event characteristics.
KDE | Value |
type | AggregationEvent |
action | ADD |
disposition | active |
bizStep | packing |
KDE Requirements
The following KDEs are required on the root of an aggregation event.
| KDE | Description | Example Value |
|---|---|---|
| eventID | A URN formatted universally unique ID (UUID) | urn:uuid:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx |
| action | The action says how an event relates to the lifecycle of the entity being described. ADD means the entity in question has been created or added to. OBSERVE means the entity in question has not been changed. DELETE means the entity in question has been removed from or destroyed altogether |
ADD, DELETE, OBSERVE |
| disposition | The disposition field of an event specifies the business condition of the event's objects, subsequent to the event. The disposition is assumed to hold true until another event indicates a change of disposition. A full list of disposition values and their definitions is available in the EPCIS Core Business Vocabulary | active |
| 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. The purpose of eventTimeZoneOffset is to provide additional business context about the event, namely to identify what time zone offset was in effect at the time and place the event was captured. | "+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 |
| parentID | A urn formatted SSCC or GDST LPN identifying the EPC of the parent product the child products are aggregated into | urn:epc:id:sscc:08600031303.solution1, urn:gdst:example.org:lpn:obj:example_prefix.01 |
Full JSON Example
{
"@context": [
"https://ref.gs1.org/standards/epcis/epcis-context.jsonld",
{
"gdst": "https://traceability-dialogue.org/epcis"
}
],
"type": "AggregationEvent",
"eventTime": "2026-04-19T13:08:41.6112327+00:00",
"eventTimeZoneOffset": "+00:00",
"eventID": "urn:uuid:a5d495c6-16cc-4b15-96cf-5dfabbe6e585",
"parentID": "urn:epc:id:sscc:08600031303.solution1",
"childEPCs": [],
"action": "ADD",
"bizStep": "packing",
"disposition": "active",
"bizLocation": {
"id": "urn:gdst:example.org:location:loc:solution.processorplant"
},
"childQuantityList": [
{
"epcClass": "urn:gdst:example.org:product:lot:class:solution.processedfish.final1",
"quantity": 15876,
"uom": "KGM"
}
]
}