GS1 Coupon Code Architecture — Implementing North American Retail Coupon Layouts
Coupon barcode types and use-cases
Retail coupons use a mix of linear and 2D barcodes depending on retailer requirements. In North America, UPC-A and GS1-128 are common for printed coupons; some retailers also accept or require 2D codes for mobile coupons to carry more complex redemption metadata. Choose the symbology that matches the retailer integration plan and supports required data fields.
Data fields and AI mapping for coupons
Coupon payloads commonly include these elements:
- Offer identifier (unique coupon ID)
- Expiration date
- Discount amount or percentage
- Redemption rules (one-time use, SKU restrictions)
- Issuing company ID (GS1 Company Prefix)
When using GS1-128, map these into Application Identifiers (AIs) or into a structured internal format agreed with the retailer. For variable-length fields, ensure proper FNC1 placement and, where necessary, use AI wrappers so back-office systems can parse redemption data reliably.
Retailer-specific constraints and integration
Each retailer may enforce different barcode dimensions, verification checks, and data format expectations. For example, grocery chains often require coupons to include an offer code that links to a specific SKU with a fixed-length field. Drugstores may require manufacturer IDs and specific expiration formatting. Work with your retail partners to obtain sample payloads and verification criteria.
Testing and fraud prevention
Implement these controls to limit coupon fraud:
- Use unique, non-sequential offer IDs per campaign.
- Include expiration and usage counters encoded where supported.
- Maintain redemption logs and reconcile POS scans against issued offer lists.
- Consider 2D signatures or cryptographic tokens inside 2D payloads for high-value coupons.
Verify coupons with both simulated POS and actual retailer test environments before distribution.