The GDST Capability Test is being updated to align with the release of the GDST Standard v2.0. As we approach the release, we want to provide a clear overview of what is changing, why these changes are being made, and the resources that will be available to support implementation.
While many of the updates are technical in nature, our goal remains the same: to ensure that GDST-capable solutions continue to exchange traceability information reliably and interoperably as the Standard evolves.
Key Technical Updates
The updated Capability Test reflects the technical changes introduced in GDST Standard v2.0. The most significant updates include:
- Read and write capabilities will now be required for all GDST-capable solutions. As a result, the dedicated “first-mile” Capability Test will be retired.
- Alignment with the latest GS1 standards. GDST 2.0 adopts the updated GS1 Digital Link Resolver 1.2 specification, which now defines the RFC 9264 Linkset as the normative Digital Link resolver response.
- Updated EPCIS query parameters. The previous “less than or equal to” (LE) query parameters have been replaced by the EPCIS 2.0 “less than” (LT) parameters. Although the names have changed, they provide the same functionality.
- Expanded query validation. The Capability Test will verify that each required EPCIS query parameter is supported by your solution by issuing queries using every required parameter. Solution providers will not be required to manually exercise every parameter during testing.
- Master data validation. The Capability Test will verify that master data is resolved through the Digital Link Resolver and is not included within EPCIS Query Documents.
- Support for new Standard requirements. GDST 2.0 introduces the Decommission event, product and location classifications, support for geofences, and several harmonization updates including normalized EPCIS business steps and removal of redundant KDEs.
Capability Test Governance Updates
In addition to the technical updates, the Capability Test itself is evolving.
Modular Capability Testing
The Capability Test will now follow the same modular structure as the Standard.
All solution providers must successfully complete the GDST Commodity Agnostic Core (referred to as Core) Capability Test in order to maintain their GDST-Capable status. Beyond this common foundation, solution providers may choose which additional modules they wish to support based on the needs of their customers.
Although only the Core is required for GDST-Capable status, seafood-focused solution providers are strongly encouraged to support the Seafood, Wild-Capture, and Aquaculture modules, as applicable.
Ongoing Validation
Rather than annual testing, GDST-capable solutions will now be expected to execute the automated Capability Test daily.
The GDST website will display the most recent date on which each solution successfully passed the automated test. This provides greater transparency and helps ensure that the versions deployed in production remain aligned with the versions that have been validated.
Solutions will not immediately lose GDST-Capable status if they miss or fail an individual daily test. However, if a solution provider goes more than one year without both:
- a successful Capability Test pass, and
- the required annual live review,
their GDST-Capable designation will be removed until compliance is re-established.
Resources to Support the Transition
A complete set of updated implementation resources will be released alongside Standard 2.0, including:
- Developer Documentation with detailed technical specifications and implementation guidance
- Software Development Kits (SDKs) to simplify implementation and reduce development effort
- Migration Guidance describing and providing guidance to address the technical changes between GDST v1.2 and v2.0
- Educational resources for both technical and non-technical audiences
- Traceability Driver, an open-source interoperability tool that enables organizations to connect existing traceability systems to standardized GDST-compatible data exchange without replacing their current software. Traceability Driver guide and case studies are publicly available.
We welcome feedback on these resources and encourage you to let us know if additional guidance would be helpful as you prepare for implementation.
Timeline
September 1, 2026
- Release of GDST Standard v2.0
- Release of the updated Capability Test
- Publication of supporting implementation resources
September 2026 – September 2027
- One-year transition period
- Current (v2.0) resources will be hosted on the GDST website
- Previous v1.2 resources will remain available upon request during the transition
September 2027
- Solution providers must have successfully passed the updated Capability Test to maintain their GDST-Capable designation.
- GDST will transition fully to v2.0 resources and retire routine support for previous versions.
Thank you for your continued engagement and support throughout this transition. We appreciate the collaboration of the GDST community in helping ensure that interoperable seafood traceability continues to evolve in a practical and transparent way.
If you have any questions, please don’t hesitate to reach out to the GDST Secretariat.
We look forward to working with you throughout the transition to GDST Standard v2.0.