e-label - Editor - QR Codes - GS1 Digital Link - Preparation and Generation in Bulk - Enterprise

GS1 Digital link is coming and more and more Brands are trying to get a head start. 

GS1 Digital Link-compliant QR codes can be achieved via our Code Ingestion Feature. 

For further reading here is a link for the GS1 Digital Link Standard, published by GS1. 




Important to Know 

  • GS1 Digital Link, as per GS1, should NOT have a logo inside the QR Code 
  • should have the 14-digit GTIN
  • can have additional information
    • GS1 information is encoded via the GS1 Application Identifiers (GS1 Application Identifiers (AI) are considered as primary identification keys for GS1 Digital Link URI
  • if GS1 Digital link is used for seasonally recurring products
    • you may want to add additional Application Identifiers to differentiate the changes between i.e. the batches/lots
    • if your GS1 Digital link QR Code is used for something like the European Digital Wine Labels, where the regulation specifies to display ingredients and nutrition information that can change between batches and years, you may need to create a "new product" in the Scantrust Portal, and in that case, that variability must then also be reflected in the GS1 Digital Link compliant QR code. 

Prep-work for GS1 Digital Link Compliant Codes

  • determine the information that needs to be encoded into your QR Code URL
  • find the correct Application Identifier for your information
    • while Scantrust can share what we have learned, to be sure, it is best you consult with a GS1 representative directly
  • Decide if you do want to utilize a custom prefix with your GS1 Digital Link identifiers (only available for Enterprise Plans).

Prepare the Document

  • Format
    • CSV
    • EXCEL (.xls, xlsx) (preferred as calculations remain)
  • configure the SCM fields you would like to track (THIS IS OPTIONAL, but recommended)
  • Build your URL ID
    • here is an example with placeholder names for SCM fields

    • Here are the corresponding file headers
    • Here an example with descriptive names for SCM fields
    • here are the corresponding file headers

      • a header may exist in the header of the CSV/Excel and not have a corresponding SCM field. 
      • headers in the CSV must show the lowercase SCM field references
    • Mandatory fields:
      • product (use SKU from product in the portal - if the product does not exist yet, the upload will fail)
      • activation_status (set to 1 to activate the code)
      • minimum one (1) app_id (to easily calculate the correct id)
      • minimum one (1) field (to generate the individual id for the product)
    • The template can be downloaded from this article

        • Formula in the example to generate the ID =CONCATENATE(B2,C2,D2,E2,F2,G2)
        • IMPORTANT:
          • the first APP_ID should start with the APP_ID itself, followed by a "/"
            • 01/ or10/ or 22/
          • all following APP_IDs should begin with a "/" followed by the APP_ID, followed by a "/"
            • /01/ or/10/ or /22/
          • NOTE: GTIN does not have to be at the beginning of the id, but it has to be somewhere in it

Uploading your GS1-compliant Codes

  • in the Slide out menu select work orders
  • click on "Upload Codes" in the bottom left corner
  • click on upload codes in the upper right corner
  • Select the Code Type: SID, choose YES, for use with the GS1 Identifier, Upload the file you just created, and specify on which "sheet" the data you want to use is located
  • assuming you followed all previously outlined steps: click "UPLOAD"
  • once you see the following screen, you are done :-) and the codes have been uploaded




Potential Issues

    • product must already exist in the portal - the product column must contain the Product Reference/SKU, otherwise, you receive the following error: 





Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request