Seafood Module 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 uniquely identifies transport and storage units such as totes, cartons, pallets, or shipping containers. Aggregation events are always reversible; the products combined into a logistical unit can later be separated or re-identified through a disaggregation event, restoring their individual identity.

Examples include:

  • Totes of landed tuna aggregated on the vessel or dock for transfer to a cold storage facility (SSCC = tote or container).
  • Cases of frozen loins or fillets packed by a processor into cartons or master cases for export (SSCC = carton or case).
  • Multiple cases of finished product consolidated onto a single pallet for shipment to a distribution center (SSCC = pallet).

The seafood aggregation event extends the core aggregation event with additional KDEs specific to seafood products.

Event Profile

The seafood aggregation event is identified by the following event characteristics

KDE

Value

type

AggregationEvent

action

ADD

bizStep

packing

disposition

active

The seafood aggregation must have at least one child product with a productClassification of seafood.

KDE Requirements

The following KDEs are required on the root of a seafood aggregation event, in addition to the Core requirements.

KDE Description Example Value
readPoint A readPoint object with an id property equal to a geo formatted coordinate pair geo:37.860236,-123.144697
productOwner A URN formatted PGLN or GDST party identifier urn:epc:id:sgln:08600031303.0.0, urn:gdst:example.org:party:example_prefix.0
informationProvider A URN formatted PGLN or GDST party identifier urn:epc:id:sgln:08600031303.0.0, urn:gdst:example.org:party:example_prefix.0

Certificate Requirements

A seafood commissioning event must carry at least one complete certificate. GDST 2.0 does not name certification types in its normative event profiles; the controlled list of supported values is maintained in the Certification Types article.

A certificate may appear in the event's certificationList or in the certificationList of its ilmd property.

Certificates are required to have the following properties

Certificate Property Description Example Value
certificationType A URN formatted string defining the type of certificate urn:gdst:certType:harvestCert
certificationAgency The name of the certificate program owner WHO
certificationStandard The name of the standard associated with the certificate WHO Human Decency Policy
certificationValue An additional descriptor of the certificate if there are different quality values for the certificate Quality class 4
certificationIdentification The ID of the certificate 0987654321

Full JSON Example

{
              "@context": [
                  "https://ref.gs1.org/standards/epcis/epcis-context.jsonld",
                  {
                      "gdst": "https://traceability-dialogue.org/epcis"
                  }
              ],
              "type": "AggregationEvent",
              "eventTime": "2026-04-19T08:58:39.4957023+00:00",
              "eventTimeZoneOffset": "+00:00",
              "eventID": "urn:uuid:4721e892-bdc3-4f67-97cd-f0bd29d32a8c",
              "parentID": "urn:epc:id:sscc:08600031303.solution1",
              "childEPCs": [],
              "action": "ADD",
              "bizStep": "packing",
              "disposition": "active",
              "readPoint": {
                  "id": "geo:37.7749,-122.4194"
              },
              "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"
                  }
              ],
              "gdst:productOwner": "urn:gdst:example.org:party:solution.processor",
              "cbvmda:certificationList": {
                  "certification": [
                      {
                          "gdst:certificationType": "urn:gdst:certType:harvestCoC",
                          "certificationAgency": "CoC Agency",
                          "certificationStandard": "Generic Chain of Custody Standard",
                          "certificationValue": "abc123",
                          "certificationIdentification": "COC-0001"
                        }
                  ]
              },
              "cbvmda:informationProvider": "urn:gdst:example.org:party:solution.processor"
          }


How did we do?

Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)