The new GS1 coupon application identifier 8112 was created to provide the coupon industry with a retailer-agnostic digital coupon format. As the AI (8112) coupon offer process was developed, several other major benefits emerged including enhanced security through serialization and separation of data, paper and e-comm compatibility, enhanced product validation, and more automated adjudication by removing cashier intervention options/ 992 offer capabilities.
- Brand receive AI (8112) data set: a base AI (8112) data string with additional required/ optional offer data
- Brand/ Authorized partner create Master Offer File, MOF, with offer data in The Coupon Bureau's centralized database.
- Brand authorizes Provider to distribute AI (8112) data sting. When distributed to consumer, the Provider deposits serialized AI (8112) data string into MOF.
- Serialized data string is presented by consumer at Point-of-sale (POS).
- POS calls out to centralized database via API connection to check offer status.
- If serialized AI (8112) data string is valid and unused, purchase requirements are sent back to POS to validate against basket data.
- POS applies discount or deny discount based on basket.
Coupon processing changes
The following coupon processing changes are required for the POS to appropriately process AI (8112) coupon offers. Changes will vary based on the POS system and Retailer business rules. There are no hardware updates required. The following list is not intended to provide the full guidance required to make these changes, for complete guidance, please see the North American Point-of-sale Implementation Guide for Coupons, see Section 1.1.
Primary Processing Changes:
API Connections: API connections are used to send and receive AI (8112) coupon data from The Coupon Bureau. APIs here.
Coupon processing logic: AI (8112) processing logic is based on AI (8110) processing logic but does require some updates as some logic components have been adjusted. For coupon processing logic references, please see the North American Point-of-Sale Implementation Guide for Coupons. Examples include:
- Validate eligible GTINs instead of Company Prefix/ Family Code validation. In current AI (8110) offers, the Point-of-Sale uses Company Prefix and Family Code field to validate product purchases. With AI (8112) offers, PoS will use the GTIN list sent via API to find a 1:1 match in the basket.
- AI (8112) does not support Family Code 992 offers or Cashier Intervention offers.
- PoS will no longer be required to evaluate the start/expiration date typically found in the barcode.
- Mobile phone symbology - Accepting A( 8112) coupons from mobile devices will require a scanner capable of reading the barcode presented on the mobile screen. QR Codes are available for use but because of their limited acceptance in the market, a code-128 barcode will always be available to the consumer.
- Fetchcode - A Fetchcode is a 14-digit code beginning with 8112 that is retrieved in real-time from a consumer’s phone in the event that the barcode cannot be scanned by a cashier. This code is valid for 5 minutes and will then expire. This code will need to be keyed in by the cashier.
- Bundled barcode – Distribution providers have the ability to add 2 or more coupons into a single data string. This data string will be contained in the same code-128 barcode. The data string representing the coupon bundle will be a 27-28 digit data string that begins with 8112.
For more information on processing AI (8112) data strings, visit our Technical Guides.
The following documents are references for use with the Retailer AI (8112) Coupon Guide:
• North American Point-of-Sale Implementation Guideline for Coupons - guidance on how coupon offers utilizing application identifiers (8110) and (8112) should be processed at POS to those already familiar with the fundamentals of North American couponing.
• GS1 AI (8112) Coupon Data Specifications - components and overall structure of application identifier (8112).
• Joint Industry Coupon Council Voluntary Guidelines for Digital Coupons – voluntary guidelines and best practices for both retailer delivered digital offers and universal digital offers using AI (8112).
Updated 5 months ago