GS1-Conformant Resolver Standard 1.2.0
The resolver standard release packagepage is built and tested against, ratified in January 2026 — what it governs, and why it changes nothing about artwork already at a printer.
Affects artwork already at a printer? No
Does this affect artwork already at a printer?
No. This standard governs the service a code reaches, not the symbol on the label. Nothing here requires a reprint, a new proof or a change to a plate.
What it is
Release 1.2.0 of the GS1-Conformant Resolver Standard was ratified in January 2026. It is the release our resolver implements and the release the public GS1 conformance test suite tests against.
It defines what a conformant resolver has to do: validate an incoming Digital Link URI
before answering it, redirect to a default link, answer a request for a specific link type
or return the whole linkset, negotiate on Accept and Accept-Language, publish a
description file, and support CORS.
The date
GS1 records the ratification as January 2026 without a day, and so do we. Where a source gives a month, this changelog shows a month.
Sources
Every factual claim about GS1 above is from one of these. Where the research did not support a claim, the claim was deleted rather than softened.
- GS1-Conformant Resolver Standard, Release 1.2.0
https://ref.gs1.org/standards/resolver/1.2.0/Read 13 AUG 2026
Run one of your own products through it
The fastest way to understand any of this is to put one of your own SKUs through it and look at the print files.
Read next
Our GS1 resolver conformance run
A dated run of GS1's public resolver conformance test suite against a live packagepage resolver — the result, the raw output, the one warning it returned, and the thing the suite does not test.
Why we will not let you write custom CSS on your product page
Consumer product pages are themed with typed tokens rather than a stylesheet. The reason is the allergen block, and it is the one product decision we are not willing to negotiate.