Skip to main content

Aggregation Event

Aggregation Event. Aggregation events capture the grouping of individual products into a single logistical unit, enabling them to be tracked collectively for downstream activities such as shipping, r…

John Heggelund
Updated by John Heggelund

Aggregation Event

Aggregation events capture the grouping of individual products into a single logistical unit, enabling them to be tracked collectively for downstream activities such as shipping, receiving, storage, or internal movements. The logistical unit is identified with a Serial Shipping Container Code (SSCC), which serves as an identifier for transport and storage units such as pallets, cartons, cases, or entire shipping containers.

Examples include:

  • Serialized cattle loaded into a truck for shipment from a feedlot to a slaughterhouse (SSCC = truck container).
  • Hides stacked onto a pallet for transport (SSCC = pallet).
  • Cases of finished product packed into cartons by a processor, enabling documentation of the carton as a single unit rather than each case individually (SSCC = carton).

Aggregation events can be carried out for different purposes, but they are often performed immediately before shipping. While a shipping event does not require a preceding aggregation event, aggregation should be performed when the logistical unit will be used as the basis for recording the shipment and any subsequent movements. In cases where multiple logistical units are created, an aggregation event should be recorded for each unit.

Aggregation should be recorded using an AGGREGATION-ADD event.

Below are the KDEs that should be recorded with the event.

KDE

CBV Field

Data Description

Event Type

eventType

AGGREGATION*

Action

action

ADD*

Business Step

bizStep

PACKING*

Event ID

eventID

Identifier for the event that distinguishes it from other recorded events (this is usually generated by the capturing application)

Product Identification (EPC) – Output

parentId

The SSCC of the logistical unit that the products are aggregated into.

Product Identification (EPC) – Input

childEpcList

The EPC(s) of the products that are being aggregated. This field is used when the input products are being traced using instance-level traceability.

Product Identification (EPC) – Input

childQuantityList

The EPCs and quantity of the products being aggregated. This field is used when the input products are being traced using lot-level traceability. (epcClass, quantity, and uom elements should be included)

Event Date & Time

eventTime

The date and time that the cattle are aggregated into the logistical unit.

Event Location ID

bizLocation

The GLN of the location where the products are being aggregated.

*Indicates that the value is always this value.

How did we do?

Receiving Event

Shipping Event

Contact