Understanding GDST & Event-Based Traceability
Traceability only works when everyone speaks the same language. In the seafood industry, variations in how data is defined, recorded, and exchanged create inefficiencies and compliance risks. That’s why GDST (Global Dialogue on Seafood Traceability) was developed—to bring alignment across global supply chains.
GDST is built on GS1 EPCIS standards, which use Critical Tracking Events (CTEs) and Key Data Elements (KDEs) to document what happens to a product, when, where, why, and by whom. This enables standardized, end-to-end documentation of product movement and transformation across any supply chain.
This model supports:
• Automated traceability from origin to point of sale
• Clear chain-of-custody documentation
• Enhanced transparency for regulators and consumers alike
Lifecycle of a Product: Event-Based Mapping
The traceable journey of a product is defined by a series of Critical Tracking Events (CTEs). Each stage in your supply chain—whether farmed or wild-caught—should be mapped to one or more of these CTEs.
This matrix visualizes how Critical Tracking Events (CTEs) align with Key Data Elements (KDEs) across a product’s journey. This is the foundation of GDST and GS1 EPCIS event-based traceability.
| KDE / CTE |
Commission |
Receive |
Transform |
Ship |
Decommission |
| Species |
✓ |
|
|
|
|
| Harvest Date |
✓ |
|
|
|
|
| Lot Number |
✓ |
✓ |
✓ |
✓ |
|
| Processing Method |
|
|
✓ |
|
|
| Ship Date |
|
|
|
✓ |
|
| Origin Location |
✓ |
✓ |
|
|
|
| Product Format |
|
|
✓ |
|
|
| Quantity |
✓ |
✓ |
✓ |
✓ |
✓ |
| Storage Conditions |
|
✓ |
|
|
|
| End Use or Disposal |
|
|
|
|
✓ |
Where Wholechain Helps
Wholechain is fully aligned with GDST and GS1 EPCIS standards and helps companies at every stage of the traceability journey:
• Map your supply chain using KDEs and CTEs
• Onboard internal users and external suppliers
• Ensure data is interoperable, accurate, and audit-ready
Getting Started
- Identify your role(s): Map where your company sits in the supply chain and what types of events you’re responsible for logging.
- Organize your steps: Break your operation into traceable points—this will help define which events to capture in Wholechain and which may be unnecessary.
- Capture all required KDEs at each CTE, ensuring data accuracy and completeness.
- If possible, have product name consistency across the supply chain.
- Maintain documentation to support verification and audit processes.