Retail & GS1 QR codes
Create product-backed GS1 Digital Link QR and GS1 DataMatrix assets with standards-aware validation.
Retail & GS1 QR codes
Retail & GS1 helps Professional and Enterprise workspaces create product-backed 2D code assets from validated GS1 inputs. Open it from QR Codes → Retail & GS1.
Use it to:
- Create product records with brand, product name, target market, and GTIN.
- Add packaging variants for package size, format, artwork version, and print status.
- Validate GS1 Digital Link identifiers before generating assets.
- Generate conservative GS1 Digital Link QR codes and GS1 DataMatrix assets.
- Configure resolver rules for consumer, retail/POS, supply-chain, linkset, and fallback behavior.
- Queue ZIP exports for selected generated assets, with optional validation report files.
Nimriz provides standards-aware validation. It does not assign GTINs, replace your GS1 account, or certify that a printed code is accepted by a retailer, POS system, or supply-chain partner.
Supported identifiers
The current Retail & GS1 module supports:
| Application identifier | Field | Notes |
|---|---|---|
01 | GTIN | Required. Nimriz normalizes GTIN-8, GTIN-12, GTIN-13, and GTIN-14 to 14 digits and checks the digit. |
22 | Consumer product variant | Optional path qualifier. |
10 | Batch or lot | Optional path qualifier. |
21 | Serial | Optional path qualifier. |
17 | Expiry date | Optional path qualifier in YYMMDD format. |
The validator returns errors for invalid GTINs, malformed qualifiers, unsafe resolver hosts, unsafe render settings, and non-canonical URI shapes. It may also return warnings when an input is valid but needs review before printing.
Digital Link QR and DataMatrix
GS1 Digital Link QR encodes the canonical HTTPS resolver URI. Nimriz uses a conservative black-on-white style for these assets so branding does not weaken scan reliability.
GS1 DataMatrix encodes the validated GS1 element string. This is useful when a partner or workflow expects a DataMatrix symbol rather than a QR code.
Before printing, test every downloaded asset on the physical package, label, or proof. Scan performance depends on print size, substrate, contrast, lighting, and placement.
Export generated assets
Use the Generated Codes list to download one asset at a time or select multiple assets and queue a ZIP export.
Retail & GS1 ZIP exports appear in Exports with your other async jobs. The ZIP includes a manifest.json with each selected code, output file name, validation status, and any failed render details. When validation reports are included, they are added as JSON files under validation-reports/.
Resolver rules
Resolver rules decide what happens when a GS1 Digital Link URL is requested on your configured resolver host.
Supported modes:
- Consumer: redirect shoppers to a configured product or campaign URL.
- Retail/POS: return JSON for configured retail/POS use.
- Supply-chain: return JSON for configured supply-chain use.
- Linkset: return linkset JSON for available links.
- Fallback: provide a default when no more specific rule applies.
Rules use explicit request fields such as context, mode, linkType, language, and country. Nimriz does not guess retail/POS or supply-chain behavior from User-Agent strings.
API access
Retail & GS1 API endpoints are available to Professional and Enterprise workspaces with QR API access. They require the same workspace API key as other customer API calls.
Retail & GS1 endpoints can create products, packaging variants, Digital Links, generated code assets, resolver rules, and validation responses. There is no unauthenticated GS1 generation API.
Analytics and privacy
GS1 resolver activity is separate from standard short-link QR analytics.
Nimriz archives resolver activity with privacy-safe identifiers and rolls it up into aggregate reporting tables. Raw IP addresses and full User-Agent strings are not stored in Postgres, and GS1 resolver scans do not change existing short-link click or QR scan counters.
Related
Related next steps
Ready to test this setup?
Create an account to try the workflow, or compare plans when the setup needs higher limits, integrations, or team controls.