Retailer AI (8112) Coupon Processing Requirement Overview

AI (8112) Process Overview

The new GS1 coupon application identifier 8112 was created to provide the coupon industry with a retailer agnostic digital coupon format. The AI (8112) was particularly needed to identify digital offer within the retailer invoicing file, distinguishing offers between paper and digital formats. As the AI (8112) coupon offer process was developed, several other major benefits emerged including enhanced security through serialization and separation of data, enhanced product validation, more automated adjudication by removing cashier intervention options/ 992 offer capabilities.

AI (8112) coupon offer industry process

  1. Brand receive AI (8112) data set: a base AI (8112) data string with additional required/ optional offer data
  2. Brand/ Authorized partner create Master Offer File, MOF, with offer data in Universal Positive Offer File.
  3. Brand authorizes Provider to distribute AI (8112) data sting. When distributed to consumer, Provider deposits serialized AI (8112) data string into MOF.
  4. Serialized data string is presented by consumer at Point-of-sale (POS).
  5. POS calls out to Universal Positive Offer File via API connection to check offer status.
  6. If serialized AI (8112) data string is valid and unused, Universal Positive Offer File will send the purchase requirements to POS to validate against basket data.
  7. POS will apply discount or deny discount based on basket. POF will automatically apply a YES to redeemed coupon unless there is a rollback API call (did not meet purchase requirements, payment not complete, therefore transaction was not complete).

Point-of-sale technical requirements

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:

  1. API Connections: API connections are used to send and receive AI (8112) coupon data from The Coupon Bureau, see
  2. 8112 Callout:
  • For AI (8112) offers, the Point-of-Sale will use an API to call out to The Coupon Bureau to authenticate the offer – Is the offer a valid offer? Has it been used?
  1. Receive Offer Data: Via API, AI (8112) purchase requirements will be received in field format for POS mapping
  • In current AI (8110) offers, the Point-of-sale receives ALL the coupon data in data string format. For new AI (8112) coupons, the data will be sent to the Point-of-sale via API in fields.
  1. Coupon processing logic: AI (8112) processing logic is based on AI (8110) processing logic. For coupon processing logic references, please see the North American Point-of-Sale Implementation Guide for Coupons.
  • 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.

Scanning and Accepting AI (8112) Universal Digital Coupons

  1. Mobile phone symbology - Due to current GS1 barcode availability, scanning limitations, and mobile wallet requirements, the primary symbology used to carry AI (8112) offers is a code-128 barcode, see example below.
  1. 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.
  1. 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.

All three potential data string formats (standard data string, fetch code, and bundled data string) will behave the same with regard to the call out in the retailer API process. All data string formats fulfill the API request to authenticate the offer or offers represented by the data string.

Additional References

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).

Did this page help you?