Skip to content
EUlabelBeta

GS1 resolver

The routing layer behind every QR code.

A scan is a web request. The resolver reads the identifiers in it and sends each visitor to the right place.

A scan, parsed
  1. Resolver

    eulabel.eu

  2. Product

    01 / 05601234290004

  3. Unit

    21 / VX48-2609-000117

What happens in a scan

From camera to passport.

  1. 1

    The phone reads a web address

    No app needed. The QR code holds a GS1 Digital Link.

  2. 2

    The resolver reads the keys

    GTIN, batch and serial are checked, including the GTIN check digit.

  3. 3

    It picks the destination

    The passport by default, or the link type a client asks for, where one exists.

  4. 4

    A serial starts from its model's links

    A serial with no links of its own uses its model's links. On passports, an unregistered serial ends on a clear 404 page.

GS1 behavior

Standard behavior, not a redirect script.

Linksets
Clients can request every link for a product as a linkset.
Link types
Each passport answers gs1:defaultLink and gs1:dpp. Other link types return 404 for now.
Description file
A resolver description at /.well-known/gs1resolver.
Compressed EPCs
Compressed SGTIN-96 and SGTIN-198 paths from RFID tags expand to GTIN and serial.
Clear errors
Malformed keys return a GS1-style 400 or 404, not a marketing page.
Your own domain
Digital Links can resolve on your verified domain, on request. QR downloads encode eulabel.eu today.

Open identifiers

The identifier stays yours.

A GTIN does not depend on a domain, so the identity on your products stays valid if you move. Codes printed with eulabel.eu still point to our domain.

Start with one product.

Early access is free and open to producers in all four sectors. Your QR codes keep working as the rules change.