You are procuring against a column with no issuer
Resolver shortlists tend to carry a "GS1 certified" box. GS1 issues no such certification and maintains no register of resolvers, so the box cannot be ticked truthfully by anyone. Two vendors tick it anyway, and none of the twelve we probed publishes a conformance result you could check.
- A procurement criterion that no standards body actually issues.
- Vendors advertising a certification that does not exist.
- No published Resolver Standard version, from anyone, to compare against.
- The gap shows up at retail integration, which is after the print run.
What to ask a resolver vendor instead
Which primary keys does it read?
The identifier comes first in the path as an application identifier and its value. 16 primary keys are supported here, matching the set GS1 own reference resolver declares.
https://tap01.link/01/09506000134352Do qualifiers survive?
Batch and serial ride after the key in canonical order. Order is part of the grammar, so a qualifier out of position is a malformed URI rather than a tolerated variant.
/01/09506000134352/21/SN0472913What does it do with a bad URI?
A malformed Digital Link is answered with HTTP 400 and the reason. The official test suite probes for exactly this by appending junk to a valid URI.
What the resolver does, and what it publishes
- 16 primary keys
GTIN, GLN, SSCC, GRAI, GIAI and the rest, each with its own qualifier grammar and check-digit rules.
- The full AI table
541 application identifier codes recognised, validated by format and passed through to your destination.
- Errors reported, not swallowed
HTTP 400 and a reason, rather than a redirect that quietly drops the part it could not read.
- A dated artifact, not a badge
The conformance run is published with its date and its source, and the two runs behind it are kept visibly apart rather than blended into a better number.
- Query parameters preserved
The standard requires the query string to be passed on to the destination, and it is, including parameters we do not recognise.
- Priced like everything else
A GS1 product master is 200 credits, once per SKU, and your first one is granted, once per workspace. Scans are 1 credit.
Real previews
Where a Digital Link lands
A resolver is only as good as the page behind it. These are rendered by the resolver itself, so a bound page keeps the batch and serial a redirect would have dropped.
These are not screenshots. Each frame is the page itself, rendered by the same code that answers a scan.
Questions
Is this resolver GS1 certified?
No, and neither is anyone else: GS1 does not certify resolver vendors and keeps no register of them. Its own position is that operators are encouraged to run resolvers according to their own business practices. What can be said accurately is that this resolver is conformant to the GS1-Conformant Resolver Standard and has been verified against GS1 official test suite, with the dated artifact published.
What happens if a scanner sends a malformed Digital Link?
It receives HTTP 400 with the reason, rather than falling through to a short-link lookup and a 404. Reporting the error is required behaviour and the official test suite checks for it.
Which primary keys are supported?
16 of them, including GTIN, GLN and SSCC, each with its own qualifier grammar, permitted order and check-digit scheme. The demo above will tell you whether a specific URI parses.
Do I need my own GS1 prefix?
To print GTINs that are yours, yes. Identifiers come from GS1 through a licensed prefix, not from us, and no resolver vendor can issue one. We host and answer for identifiers you already have the right to use.
Do you verify that my licence is real?
Not against GS1 registry today. A registered prefix here is an attestation you make, not something we confirm upstream, and we would rather say so than let the word "verified" do work it has not earned.