Verified GDST-Capable Solutions

Here you can find an authoritative list of software products and systems solutions owned by active partners of the GDST Foundation, that have passed the GDST Capability Test, and are thereby entitled to make a claim of “GDST Capability” and/or bear the GDST-Capable logo.

This claim and logo use is allowed for only one year from the date that the test was passed and is only applicable to the specific version of the software that was tested. Any changes or update made to the version of software that originally passed the GDST Capability Test will make the original test null and void, meaning the new version of the software will need to be retested to verify that the software or system is still “GDST-Capable”

Note: To earn the logo or make the “capable” claim, the traceability software or system must score a passing grade when using the GDST’s online tool test to demonstrate its ability to capture all data required by GDST “Key Data Elements”, to receive and transmit data in the correct GDST formats, and to use the GDST standardized communications protocol. Software systems that meet these requirements are capable of interoperability because they can easily interface with one another to support full chain seafood traceability compliant with the GDST standards.

To learn more about a verified GDST Solution, please click on the company logos in the table below. As you use this list, please keep in mind the following important notes:

The GDST Capability Test is only able to verify the ability of the tested software to support GDST compliance – it does not verify whether companies using the software are GDST-compliant. See the fuller disclaimer at the bottom of this page.
The GDST-Capable Logo is awarded to software products, not companies. Companies must earn the logo for specific versions of specific software, and they are only entitled to display the logo in connection with the specific products that have passed the Capability Test. Earning the GDST-Capable logo does NOT mean the GDST endorses or otherwise attests to the ability of any company to provide its services.
The GDST-Capable logo is only valid for the specific version of software used to pass the test. Updated versions of the software must pass the test again to maintain the logo. In addition, the logo is only valid for one year after it is first awarded.
The GDST-Capable logo and related “Capability” claim can only be awarded to the company that developed the tested software, provided they are a partner of the GDST Foundation. Users of a GDST Capable software or system (sub-licensees) wishing to make a GDST Capability claim for the data that they are entering, may only do so if they are also Partners of the GDST Foundation (i.e., through a GDST Affinity Program with the owner). Their claim is also restricted to the specific software version that passed the test.

If you have any questions, please contact info@TheGDST.org

Solution Provider	Solution Name	Version Tested	Date Passed and Expiration Date	Capability Level

Trace Register	TR5	5.0	October 9, 2024 September 29, 2025	Full Chain
Wholechain, Inc.	Wholechain	1.1	December 12, 2023 December 12, 2024	Full Chain
Pacifical	SmarTuna	1.0.22	March 7, 2024 March 7, 2025	Full Chain
Seafood Souq	SFS Trace	2.0	January 17, 2024 January 17, 2025	Full Chain
OpsSmart Global	OpsSmart	1.0	June 12, 2024 June 12, 2025	Full Chain
ThisFish, Inc	Tally Version	2.2.4	6 March, 2024 6 March, 2025	Full Chain

.

GDST Partners who have not yet passed the GDST Capability Test:

iFoodDS
Trustwell
Seafsoft
FIA PNG (iFIMS) – previously v1.1 GDST-Capable which is now obsolete
NETYIELD
Koltiva
Mabel Systems – previously v1.1 capable which is now obsolete
Marel
Maritech
NTT Dara
TraceGains
UpsTrace
VeriCatch
Chainparency
TraceChain
Agritrack SA
One Network Enterprises (ONE)

Software Solutions who have been talking to GDST about achieving GDST-Capability

Important Disclaimer: The GDST Capability Test is limited in its application. It verifies the ability of a software product or system to enable GDST compliance. However, it does NOT verify:

The level of GDST compliance resulting from use of the software, including by the company that developed it. For example, it does NOT verify that a company implementing the software is actually collecting and delivering GDST-compliant information in a transactional environment; or
The capability of the software when implemented by any company other than the developer, such as a client of a solution provider (considering that performance of software may vary when installed and operated in specific operational contexts).

The GDST is working towards developing mechanisms and benchmarks to address these other verification needs in the future. However, if your supply chain has 2 or more GDST-Capable verified systems that are linked then you can use the Completeness Tool to check how many KDEs are visible to you through those stages of your supply chain.