GenFrontier homeScope a project
Menu
Reader questionWhat do 2D barcodes (GS1 DataMatrix, and QR codes with GS1 Digital Link) mean for our receiving scanners, label printing and ERP/WMS data?

GS1 Sunrise 2027: what 2D barcodes change in the warehouse

GS1 Sunrise 2027 brings 2D barcodes to retail checkout. What it changes upstream: receiving scanners, lot and expiry parsing, WMS fields and labels.

field-notes / traceability-standards / gs1-sunrise-2027-2d-barcodes
A hand loom with long parallel black warp threads that turn into a small square of red checkered weave at one end.

GS1 Sunrise 2027 is a retail checkout initiative: retailers are upgrading point-of-sale scanners so they can read 2D barcodes (GS1 DataMatrix, and QR Code or Data Matrix carrying a GS1 Digital Link URI) alongside the linear barcodes already on packs. For a warehouse, nothing is switched off. GS1 rules keep a linear barcode on products during the transition and keep GS1-128 as the mandatory barcode on pallet labels. What changes is that more units arrive carrying lot, expiry and serial data in a 2D symbol, and your receiving scanners, your parser and your WMS fields decide whether that data is captured or thrown away.

This field note covers that upstream side: the symbols that reach your dock, scanner settings, parsing into WMS fields, item and lot master changes, printing 1D and 2D codes in parallel, and testing. Every GS1 rule quoted here was checked against GS1 documents in November 2026.

What GS1 Sunrise 2027 is, and what it is not

Sunrise 2027 is an industry goal for retail point of sale (POS), not a regulation and not a warehouse labeling mandate. GS1 US describes it as “a global transition from 1D UPC barcodes to 2D barcodes, like QR codes” that “supports retailers to ensure their point-of-sale (POS) systems can read and process these next-generation data-packed codes” (GS1 US, Sunrise 2027).

Three points from GS1’s own documents shape any upstream plan:

  • It is gradual and voluntary. GS1 US states that “it is not necessary to implement all the capabilities of 2D by that date.” GS1’s 2D Barcodes at Retail Point-of-Sale Implementation Guideline (release 1.1.0, ratified December 2025) describes “a smooth, voluntary transition from linear barcodes.”
  • Linear barcodes stay. The same guideline says: “Linear barcodes (e.g., EAN/UPC and GS1 DataBar) will not go away and will coexist with 2D barcodes for as long as there are uses for them.” During what GS1 calls the dual-marking phase, a trade item carries its current linear barcode plus a 2D symbol.
  • Its scope is the consumer unit at the register. The guideline lists “Non-consumer units and packaging hierarchies scanned in distribution and non-retail environments” as out of scope. Cases and pallets are governed by the GS1 General Specifications, covered later in this note.

The minimum scanner capability GS1 sets for the 2027 ambition is modest. The guideline states that “The minimum requirement for the Ambition 2027 is software Mode 1”: the scanner finds the first GTIN (Global Trade Item Number) in any compliant linear or 2D barcode and transmits it. Retailers that want lot or expiry data at the register need Mode 2 or Mode 3, which transmit the extra data as well.

A warehouse sits in the same position. Reading the GTIN out of a 2D code is the easy part. Capturing the lot, the expiry date and the serial number takes deliberate configuration in the scanner, the receiving app and the WMS.

Packaging level What stays What may be added GS1 rule
Consumer unit EAN/UPC or GS1 DataBar during the transition GS1 DataMatrix, QR Code with GS1 Digital Link URI, or Data Matrix with GS1 Digital Link URI 2D in Retail guideline 1.1.0, section 1.2
Case scanned in general distribution EAN/UPC, ITF-14, GS1-128 or GS1 DataBar GS1 DataMatrix or GS1 QR Code “in addition to linear symbols” General Specifications 26.0, section 2.1.7
Pallet or other logistic unit GS1-128 carrying the SSCC is mandatory GS1 DataMatrix or GS1 QR Code, which must hold every element string in the GS1-128 General Specifications 26.0, section 2.2.1
Your systems The GTIN remains the product key More attributes per scan, and a second syntax (a web address) to parse GS1 Digital Link URI Syntax 1.7.0

Which 2D barcodes and syntaxes will reach your dock

Three 2D symbols are approved for retail POS, and the data inside them is written in one of two syntaxes. Your software needs to know which combination it received, and a well-configured scanner tells it through a three-character prefix called the symbology identifier.

GS1’s guideline lists the POS 2D choices as “the QR Code with GS1 Digital Link URI syntax, Data Matrix with GS1 Digital Link URI syntax and GS1 DataMatrix.” The two syntaxes are:

  • GS1 element string syntax. A string of application identifiers (AIs) and values: (01) for the GTIN, (10) for batch or lot, (17) for the expiration date, and so on. It is the same syntax GS1-128 and GS1 DataBar already use. A value that is not of predefined length is closed by a Function 1 character (FNC1) when another field follows it, and a scanner transmits that as the ASCII group separator, hex 1D.
  • GS1 Digital Link URI syntax. The same AIs written as a web address, for example https://example.com/01/09506000134352/10/ABC123?17=271231. The GTIN and its key qualifiers (lot, serial) sit in the path; other attributes, such as the expiry date, sit in the query string.

The guideline puts the practical choice plainly: “If not needing to connect to an online experience, GS1 DataMatrix with GS1 element string syntax is ideal. If a web experience is needed, a QR Code with GS1 Digital Link or Data Matrix with Digital Link should be used.” A brand that wants a consumer web experience will therefore print a URI, and a brand that does not may print element strings. Your receiving software has to handle both.

Symbology identifiers tell the parser what it is reading

A symbology identifier is a prefix such as ]d2 that the scanner adds in front of the data. Table 5-2 of the General Specifications lists them, and section 4.15.1 states that “All barcode scanning systems SHALL deploy symbology identifiers” and process GS1 AIs according to GS1 rules.

Symbology identifier Symbol Content Typical place in a warehouse (our reading of GS1 application rules)
]E0 EAN-13, UPC-A or UPC-E 13 digits, GTIN only Consumer units
]I1 ITF-14 14 digits Cases printed on corrugate
]C1 GS1-128 Element strings Pallet and case labels
]e0 GS1 DataBar Element strings Fresh and variable-measure consumer units
]d2 GS1 DataMatrix Element strings Consumer units, healthcare packs, some cases
]Q3 GS1 QR Code Element strings Cases and logistic labels, as a supplement
]d1 Data Matrix GS1 Digital Link URI Consumer units
]Q1 QR Code GS1 Digital Link URI Consumer units

Source: GS1 General Specifications 26.0, Table 5-2, checked November 2026. Symbology identifiers are case sensitive: ]e0 is GS1 DataBar, while ]E0 is EAN/UPC.

Not every 2D code on a pack is a GS1 code

Packs can carry QR codes that are plain marketing links, and some manufacturers print internal Data Matrix codes for production control. The General Specifications say a production-control code “SHOULD be made as obscure as possible”, but you will still see some at receiving. A ]Q1 prefix only says “QR Code”, so the parser has to check that the content follows the Digital Link syntax before trusting it.

The Digital Link URI standard is explicit that a Digital Link URI “does not have any intrinsic meaning” until “it is parsed by a GS1-aware system.” It also says a Digital Link URI “can be constructed in any domain name.” Your parser should therefore ignore the domain and read the path. A receiving app that stores whatever a scanner sends will, sooner or later, save a marketing URL as a lot number.

Where 2D codes show up in a warehouse

Consumer units come first, because that is where Sunrise 2027 is aimed. Cases and pallets may carry 2D codes too, but apart from very small logistic units, only as a supplement to the linear barcode GS1 still requires at those levels.

Which barcode each packaging level carries during the transition Level Required (linear) Optional 2D Consumer unit EAN/UPC or GS1 DataBar stays during transition GS1 DataMatrix, or QR / Data Matrix with Digital Link URI Case EAN/UPC, ITF-14, GS1-128 or DataBar section 2.1.7 GS1 DataMatrix or GS1 QR Code, in addition to linear Pallet (logistic unit) GS1-128 with SSCC is mandatory section 2.2.1 2D may be added; it must repeat every GS1-128 element string
Source: GS1 General Specifications 26.0, sections 2.1.7, 2.2.1 and 4.15; GS1 2D Barcodes at Retail POS Implementation Guideline 1.1.0, section 1.2. Checked November 2026.

Consumer units and eaches

If your building touches eaches, the 2D code is now part of your receiving surface. Each picking, e-commerce packing, store replenishment, kitting, repacking and customer returns all handle consumer units. A returned unit with a lot and serial in its 2D code can be matched to the original shipment, provided you recorded the serial when it shipped. A UPC cannot do this, because the EAN/UPC family “carries only the Global Trade Item Number”, per the GS1 guideline.

Do not assume every 2D code carries a lot. GS1’s industry endorsement statement notes that “fresh foods using real-time labelling can soon incorporate expiration dates in their barcodes,” while “products with pre-printed packaging will need advanced manufacturing technology to do the same.” The guideline also notes that 2D codes added for marketing “tend to contain only the Global Trade Item Number (GTIN)”, so a code on a pack is no promise of lot data.

Cases

For trade items scanned in general distribution, section 2.1.7 of the General Specifications says: “Some scanning systems may be able to handle 2D barcodes as well as linear barcodes. In these environments, GS1 DataMatrix and GS1 QR Code may be used in addition to linear symbols.” The linear barcode is still the one every partner can read. A 2D code on a case is an extra, useful only to partners who scan it.

Pallets and other logistic units

The SSCC (Serial Shipping Container Code) is the only GS1 key for a logistic unit, and section 2.2.1 is direct: “The mandatory data carrier used to represent individual logistic units is the GS1-128 barcode symbology.” A GS1 DataMatrix or GS1 QR Code “MAY be included in addition”, and “the 2D barcode SHALL include all element strings included in the GS1-128 symbol(s).” For a unit too small for a 4 by 6 inch label, a 2D code may be used alone, “though a GS1-128 containing a SSCC is still recommended.” Our field note on SSCC pallet labels covers the label itself.

Which processes change

Process What a 2D code can add Decision you need to make
Receiving eaches or inner packs Lot, expiry or serial per unit Capture per unit, per case, or not at all
Receiving cases Lot and expiry without opening the case Trust the ship notice, scan the case, or both
Customer returns Lot and serial of the returned unit Match to the original order before restocking
Each picking and packing Serial number at the point of shipment Whether serials are recorded or only checked
Holds and recalls Lot on every unit in stock Whether lot lives at location level or only on receipts
Cycle counting Expiry date on the shelf Whether counters confirm dates or only quantities

What a 2D-ready receiving scanner needs

A 2D-ready receiving scanner is an imager configured to read Data Matrix and QR Code, transmit symbology identifiers and preserve the group separator. The hardware question is the easy one. GS1’s guideline notes that the 2027 ambition “will require software upgrades and may require equipment upgrades if the POS scanner is not already imager capable.”

The same logic applies to warehouse handhelds. A laser engine that sweeps a line across bars cannot read a matrix symbol, so 2D needs an imager. Most of the remaining work is configuration, and configuration drifts. GS1’s 2D Barcodes in Retail test suite has a troubleshooting entry for exactly this: when “the same hardware is producing different results, it is likely that the software is configured differently.”

Scanner settings to decide and write down

Setting Why it matters What to specify
Data Matrix and QR Code enabled When an imager does not read 2D codes, the test suite says the functionality “would need to be enabled within its software” Enable both; disable symbologies you never receive
Symbology identifier transmission Required by General Specifications 4.15.1; the parser routes on it On, for every symbology
Group separator (FNC1) handling Without it, a lot followed by another variable field runs together Transmit hex 1D, or map it to a character your app recognizes, and test it
Reverse reflectance White-on-dark codes “often” need a “reverse video” setting, per the test suite Enable if any supplier prints inverse codes
Digital Link conversion Some scanners can translate a URI into an element string before sending Decide whether the scanner or the app converts, and do it in one place only
Multiple codes on one item General Specifications 4.15.1: “only process one set of the desired data” Define which code wins at receiving when both are read

The transmitted string depends on configuration: for one GS1 DataMatrix, the test suite lists five host formats, from the full string with ]d2 to the GTIN alone with a “G” prefix. Pick one format per device class and record it in the scan specification.

Keyboard emulation and the invisible separator

Some warehouse apps receive scans as typed keystrokes (keyboard emulation). If the handheld sends scans that way, confirm the group separator arrives as a character your app can see. If it does not, an element string such as (10) lot followed by (17) expiry becomes one long lot value, and nothing flags the error until someone searches for that lot.

A GTIN-only test will pass on a misconfigured scanner, because a GTIN has a fixed length and needs no separator. Include at least one test code where a variable-length field is followed by another field. The test suite’s troubleshooting section has entries for exactly these symptoms, including “The barcodes will scan, but the data is not processed.”

Example (fictional). A distributor audits its 40 receiving handhelds before a grocery customer starts shipping units with 2D codes. Twelve are older laser models and cannot read 2D at all. Of the 28 imagers, 20 read Data Matrix, but only 9 transmit symbology identifiers, and 4 strip the group separator in keyboard mode. The team writes one configuration profile, pushes it to all 28 imagers, reruns the same six test labels on each, and schedules the 12 laser units for replacement on the dock doors that receive grocery.

How to parse a 2D scan into WMS fields

Parsing means turning the scanned string into a list of AI and value pairs, validating each value, and writing them to the right fields. Do it in one shared component, used by every app that scans, so receiving, returns and counting all interpret a code the same way.

From scan to WMS fields: one parser, two syntaxes Scan + identifier ]C1 ]e0 ]d2 ]Q3 element string ]d1 ]Q1 Digital Link URI ]E0 ]I1 GTIN only Other or none log and reject One list of AI and value pairs Validate: check digit, dates, lengths Map to WMS fields, keep raw scan
Symbology identifiers from GS1 General Specifications 26.0, Table 5-2. The single-parser design is our recommendation, not a GS1 requirement. Checked November 2026.

The parsing procedure, step by step

  1. Route on the symbology identifier. ]C1, ]e0, ]d2 and ]Q3 carry element strings. ]d1 and ]Q1 should carry a Digital Link URI. ]E0 and ]I1 carry a bare GTIN. Log anything else with the raw string and reject it at the scan prompt.
  2. Walk an element string AI by AI. Look up each AI’s length rule. A predefined-length AI such as (01), always 14 digits, or (17), always 6 digits, ends where its length ends. Every other AI, such as (10) batch or lot, ends at the next group separator or at the end of the string.
  3. Read a Digital Link URI path, then its query string. Find the primary key in the path (for products, /01/ followed by 14 digits). Key qualifiers follow in a fixed order: consumer product variant (22), then lot (10), then serial (21). Attributes such as 17=271231 sit after the ? as key=value pairs.
  4. Percent-decode URI values. The URI standard requires characters such as /, %, & and ? to be percent-encoded inside values. A lot printed as LOT/7A appears in the URI as LOT%2F7A and must be stored as LOT/7A.
  5. Normalize to one structure. Both parsers output the same list of AI and value pairs, so everything downstream is shared. GS1’s own Mode 2 example shows the equivalence: a QR Code holding https://id.dalgiardino.com/01/09506000134352/10/ABC?17=231231 is transmitted as 010950600013435210ABC^17231231, where ^ stands for the group separator.
  6. Validate. Check the GTIN check digit. Check each date is a real date. Check value lengths against the AI’s format. Check that a serial (21) arrives with a GTIN, since the guideline says a serial “must be encoded with GTIN to be meaningful.”
  7. Map and act. Write values to the receipt line, license plate or inventory record, and apply your receiving rules (minimum remaining shelf life, lot holds, serial uniqueness). Keep the raw scan string with the transaction for later investigation.

You do not have to write the AI dictionary from memory. The GS1 Barcode Syntax Resource is “a collection of assets that aims to help the GS1 user community to improve data quality and accurately convert between the different GS1 data syntaxes used with 1D and 2D barcodes.” It includes a syntax dictionary of all assigned AIs, a set of tests (linters) written in C, and a reference engine.

Two date rules that catch parsers out

GS1 dates are written YYMMDD, and two rules from section 3.4 and section 7.12 of the General Specifications matter at receiving:

  • Day 00 means the end of the month. When the day is not needed it is filled with zeros, and the string “SHALL be interpreted as the last day of the noted month including any adjustment for leap years.” The General Specifications give “160200” as February 29, 2016. A parser that rejects 00, or stores it as the first of the month, gets expiry dates wrong. (Regulated healthcare products have a different rule: since January 1, 2025, their day “SHALL NOT be expressed as two zeroes.”)
  • The century is computed, not assumed. A two-digit year can only express dates from 49 years in the past to 50 years in the future, and section 7.12 sets out how to pick the century. Use that rule instead of hard-coding “20”.

Mapping AIs to WMS fields

AI GS1 data title Format Typical WMS field Receiving check
(01) GTIN 14 digits Item, via GTIN cross-reference by packaging level Reject if the GTIN is unknown
(10) BATCH/LOT Up to 20 characters Lot number Create or match the lot; check holds
(17) USE BY or EXPIRY YYMMDD Expiration date Minimum remaining shelf life
(15) BEST BEFORE or BEST BY YYMMDD Best-before date, kept separate from expiry Your own rule; do not merge with (17)
(11) PROD DATE YYMMDD Production date Optional; supports rotation
(21) SERIAL Up to 20 characters Serial number Unique per GTIN
(22) CPV Up to 20 characters Consumer product variant Store if the brand uses it
(00) SSCC 18 digits License plate number Match to the ship notice
(02) CONTENT 14 digits GTIN of contents on a logistic unit Match to expected item
(37) COUNT Up to 8 digits Quantity of trade items on the unit Compare with expected quantity

Source for AI numbers, data titles and formats: GS1 General Specifications 26.0, Table 3-1, checked November 2026. Field names and checks are typical practice, not GS1 requirements.

Example (fictional). A receiver scans a unit of item EX-20118. The scanner sends ]Q1https://example.com/01/09506000134352/10/LOT%2F7A?17=270600. The parser routes on ]Q1, confirms the path starts with /01/ and 14 digits, and reads lot LOT%2F7A, decoded to LOT/7A. The query gives (17) 270600: day 00, so the expiry is June 30, 2027. The GTIN check digit (2) is valid and the GTIN maps to EX-20118 at the each level. The WMS records lot LOT/7A, expiry 2027-06-30, and the raw scan string. (The GTIN is the example number GS1 uses in its own documents.)

Which ERP and WMS data to fix before the codes arrive

A parser is wasted if the item and lot masters cannot hold what the code carries. Check five things first.

  1. GTINs at every packaging level. The each, the inner pack and the case usually carry different GTINs. Store each one against the right unit of measure, so a scan of a unit is never received as a case.
  2. GTINs stored as 14 digits. The Digital Link standard says GTIN-8, GTIN-12 and GTIN-13 “SHALL be expressed as 14 digits, with leading zeroes serving as filler digits.” The test suite advises: “Confirm that the host system can process 14-digit GTINs.” Normalize on input and compare as 14-digit strings.
  3. Lot fields wide enough and case sensitive. AI (10) allows up to 20 characters from GS1’s character set 82, which includes upper-case and lower-case letters and twenty special characters but no space. An ERP lot field that is shorter, forces upper case or rejects / will corrupt some supplier lots.
  4. Separate date fields. GS1 defines production (11), packaging (13), best before (15), sell by (16) and expiration (17) as different dates. The guideline describes (17) as the date that “determines the limit of consumption or use”, while (15) marks the end of a quality period. Keep them apart, and let your shelf-life rules name which one they use.
  5. Serial handling decided. If you will capture serials, decide where they live (receipt, license plate or unit record) and how duplicates are handled. The guideline says “The brand owner and the manufacturer are responsible for ensuring the non-duplication of serial numbers for a GTIN”, so a duplicate at your dock may point to a rescan, a data error or a counterfeit, and needs an owner.

Our note on item master data readiness covers the wider item master clean-up that usually sits around this work.

When the scan and the ship notice disagree

If a supplier already sends lot and expiry in its EDI 856 ship notice, and you also scan them from the product, the two can disagree. Write the rule down before go-live. One option is to treat the scanned value as the physical truth, hold the line, and send an exception to the buyer or supplier contact.

Food items and traceability lot codes

For foods on FDA’s Food Traceability List, a lot number read from a 2D code is a convenient carrier, but it is not automatically the traceability lot code you must keep. FDA states that Congress “directed FDA not to enforce the Food Traceability Rule prior to” July 20, 2028, and that it “intends to comply with this Congressional directive” (FDA, Food Traceability Rule, checked November 2026). Our note on FSMA 204 traceability lot codes explains when you assign one and when you keep the supplier’s. Our food traceability page describes the records work around it.

Example (fictional). A food distributor checks its ERP before a supplier adds 2D codes to cheese wedges. The lot field is 15 characters and upper case only; the supplier’s lots are up to 18 characters with lower-case letters. The expiry field exists, but receiving fills it from the purchase order’s default shelf life, not from the product. The team widens the lot field to 20 characters, turns off upper-case forcing, adds a best-before field, and changes receiving to take expiry from the scan when one is present.

How to print 1D and 2D codes in parallel on your own labels

If you print case labels, pallet labels or relabel consumer units, adding a 2D code is mostly a data discipline problem: the 2D code must say exactly what the linear code says. Section 4.15.1 of the General Specifications sets the rules for multiple data carriers on one item.

  • Same identifier. “All GS1 data carriers that are used for the same application on an entity SHALL encode the same GS1 identifier (e.g., same GTIN, same GRAI, etc.).”
  • Same attribute values. When identifiers and attributes appear in more than one carrier, “the attribute values SHALL be the same.”
  • 2D supplements GS1-128 in full. In general distribution, where GS1-128 is the main barcode, its element strings “at a minimum SHALL be encoded in the supplemental 2D barcode.”
  • Adjacent placement. Two barcodes for the same application “SHOULD be placed adjacent to each other while maintaining their Quiet Zones.”
  • One read, one beep. Scanning systems must “only process one set of the desired data” and “SHOULD only produce one acknowledgement.”

Bind both symbols to the same data source

The simplest way to obey “same values” is to generate both symbols from one record at print time. Do not type values into a second barcode object on the template. Static data such as the GTIN can live in the template. Dynamic data such as lot, expiry and serial must come from the WMS or ERP record for the unit being labeled. The guideline notes that “EAN/UPC barcodes can only accommodate static data while 2D barcode like GS1 DataMatrix or QR Codes can use dynamic data.”

Label field Data source Linear barcode 2D barcode Human-readable text
SSCC (00) Generated per pallet at build GS1-128 (mandatory) Repeated Yes
Contents GTIN (02) Pallet build record GS1-128 Repeated Yes
Lot (10) Production or receipt record GS1-128 Repeated Yes
Expiry (17) Lot master GS1-128 Repeated Yes
Count (37) Pallet build record GS1-128 Repeated Yes
Extra attributes Lot or order record Not required May be added Your choice

Symbol size on a thermal printer

The General Specifications set sizes and print quality per application in symbol specification tables. For logistic units (table 5), GS1-128 has an X-dimension (narrowest bar width) of 0.495 to 0.940 mm and a minimum bar height of 31.75 mm. GS1 DataMatrix and GS1 QR Code have an X-dimension of 0.743 to 1.50 mm, with a quiet zone of 1X for DataMatrix and 4X for QR Code. For consumer units scanned at POS and in general distribution (table 3, addendum 1), the 2D X-dimension runs from 0.743 mm to a 0.990 mm target, and “The use of these barcodes SHALL be in addition to a 1D barcode.” That table also requires Digital Link URIs to “use the uncompressed form.”

A thermal printer can only make modules a whole number of dots wide, so check the arithmetic. At 203 dpi, one dot is about 0.125 mm, so 6 dots give a 0.75 mm module, just above the 0.743 mm minimum. At 300 dpi, one dot is about 0.085 mm, so 9 dots give about 0.76 mm. Set the module size in dots in the template, then confirm it with a verifier.

Example (fictional). A manufacturer adds a GS1 DataMatrix to its 4 by 6 inch pallet label beside the GS1-128. The first test labels pass a scanner check, but the verifier report shows the DataMatrix holds (00) and (02) only, while the GS1-128 also holds (10) and (17). That breaks the “all element strings” rule. The fix is in the template: both symbols now read from the same pallet record, and the template test case compares decoded values from the two symbols field by field.

How to verify labels and test scanners before your partners do

Test two things: whether your printed codes meet the specification (a verifier answers that), and whether your scanners and software read every code you will receive (a test matrix of real devices and labels answers that).

Verification grades the print

The guideline describes a verifier as “a specialised device designed to assess and grade the quality of printed barcodes.” Unlike a scanner, it checks that the code meets the standard and “is encoded with a compliant data structure.” The General Specifications name ISO/IEC 15415 as the print quality test for 2D symbols and ISO/IEC 15416 for linear ones.

GS1 states quality requirements as grade, aperture and light, written like 1.5/20/660. That example means a minimum overall grade of 1.5, measured with a 0.020-inch synthetic aperture, under 660-nanometre light. The aperture number is “the diameter in thousandths of an inch,” per the General Specifications. Table 5 sets 1.5/10/660 for GS1-128 on logistic units and 1.5/20/660 for the 2D symbols.

A scanner that reads a code is not a pass. A marginal symbol may read on one device and fail on a partner’s, and a scanner will happily read a code that holds the wrong data structure. GS1’s readiness criteria for verifiers include checking syntax against the General Specifications and the Digital Link standard, or using the Barcode Syntax Resource (GS1, Solution provider 2D readiness).

A test matrix for receiving

GS1’s test suite (release 1.1, February 2025) was written so that industry can “accurately determine their current scanning capability.” It includes printable GTIN-only tests, non-retail barcode tests, AI tests for each 2D symbol, co-located 1D and 2D tests, and a results spreadsheet. Its audience explicitly includes “distributors, warehouse operators and solution providers.” Add your own cases for the data you actually receive:

Test case What it proves Pass condition
GTIN-only EAN-13 and GS1 DataMatrix Basic 2D read and GTIN padding Same 14-digit GTIN stored from both
(01)(17)(10) element string Fixed-length handling Expiry and lot in the right fields
(01)(10)(17) element string Group separator survives Lot ends before the expiry field
Digital Link URI with lot in path and expiry in query URI parsing Same result as the element string version
Lot containing / in a URI Percent-decoding Lot stored with /, not %2F
Expiry with day 00 Date rule Last day of the month stored
Serial (21) Serial capture and duplicates Second scan of the same serial is flagged
Plain marketing QR Code Non-GS1 rejection Scan refused with a clear prompt
1D and 2D on the same unit One set of data One unit received, not two
White-on-dark 2D code Reverse reflectance Reads, or is listed as unsupported

Run every case on every device model and every app that scans, and record the result per device. Our UAT test plan template has a structure for recording cases, expected results and sign-off.

A readiness checklist for distributors and manufacturers

Readiness upstream comes down to four lists: devices, data, labels and tests. In our engagements we start by writing the scan and data requirements down before any device or template is changed, because a written rule can be tested.

Devices

  1. List every scanning device by model, location and app, and mark which ones are imagers.
  2. Write one configuration profile per device class: 2D symbologies, symbology identifiers, group separator handling, reverse reflectance and Digital Link conversion.
  3. Push the profile and confirm it on each device with the same test labels.
  4. Plan replacement of laser-only units where 2D-coded eaches or returns are handled.

Data

  1. Load GTINs for every packaging level, stored as 14 digits.
  2. Check lot field length (20 characters), case sensitivity and allowed characters.
  3. Add separate fields for expiry, best-before and production dates where you need them.
  4. Decide where serials are stored and how duplicates are handled.
  5. Write the rule for scan versus ship notice disagreements.

Labels

  1. Generate every barcode on a label from the same record.
  2. Repeat every GS1-128 element string in any supplemental 2D code.
  3. Set module sizes in whole printer dots that meet the symbol specification table.
  4. Verify sample labels on a verifier, not only a scanner.

Tests and people

  1. Run the GS1 test suite and your own cases on every device and app.
  2. Update receiving and returns procedures, then train each shift on what the new prompts mean.
  3. Recheck after every scanner firmware update or app release.

If you are a manufacturer adding 2D codes to your own products, our manufacturing page covers lot and serial genealogy on the production side. If you would like help writing the scan specification, label templates and test plan, see our barcode, RFID and labeling service, or read how we scope and plan a project before any build starts.

Working on this problem?

If this field note describes a process you need to fix or build software around, tell us about it. We start with your process, your systems and your deadline.