Provider Guide to Universal Digital Coupons

Distribution providers are responsible for the management (deposit and distribution) of the serialized data strings on behalf of their manufacturer partners and the consumer experience. 

This article should serve as a guide to the management of serialized data strings as well as required and optional consumer experience components. 

At the end of the article, we will review the certification process required to become a Certified Universal Coupons Distribution Provider. This certification serves as a functional requirements check to ensure all distribution providers are adhering in compliance with all required functionality.

Management of Serialized Datastrings 

It is the responsibility of the distribution provider to serialize the base data string and deposit that serialized data string into the Master Offer File on behalf of the manufacturer. The format of the serial number is as follows: 

To review technical documentation regarding the management of the serialized data strings, click here. 

Consumer Experience: Required and Optional Functionality 

Presentment: Barcode selection

Universal Digital Coupons do not have a barcode standard at this time, the purpose of this stance was to provide all industries room for future innovation as new scanning capabilities gain market traction. Our current recommendation is the use of a QR Code with a secondary code-128 barcode for optimal consumer experience.

Time Bound Fetch Code

Fetch code is a required function. 

A Time-bound Fetch code, or Fetch Code, gives the shopper an alternative shortened code in the event that the barcode cannot be scanned by a cashier.  The fetch code is a short-lived 16-digit code that customers can manually provide to the cashier for redemption.

For Time-bound Fetch Code technical instructions, click here. 

Real-time Webhooks

Real-time webhooks are strongly recommended. 

The real-time webhook function provides real-time distribution and redemption event notifications for serialized data strings: Deposit of serialized data string, delete data string, redeem data string, rollback data string.* These notifications are intended to help to enhance the consumer experience. The most important recommendation is to use the redemption notifications remove the coupon from the consumer’s wallet or app so that they cannot attempt a second redemption. 

For webhook technical instructions, click here.

Bundling

Bundling is optional. 

The bundling feature allows multiple serialized data strings to be “bundled” into one data/barcode to scan. This feature was created to aid in lane time speed and prevent consumers from displaying coupons one by one at the time of checkout. Barcode presentation recommendation for bundled coupons in a QR Code.

Bundling is accomplished by simply appending serialized data strings one after another. For example, if you have deposited two serialized gs1s (8112001222228888849444370980731766,8112001222228888849445147407548997) you can create a bundle just by appending two serialized gs1s one after another (81120012222288888494443709807317668112001222228888849445147407548997).

Up to 10 serialized datastrings can be bundled together. Should the shopper have more than 10 coupons, another bundle should be created and displayed in a second QR Code. 

In the event a bundled QR Code cannot be scanned, a fetch code can be generated for the bundled coupons. 

Metadata

Metadata can be added to the Master Offer File so that additional campaign details can be passed to partners to aid in the display of the coupon in the consumer experience. Metadata includes:

• Title - This text is intended to be used as the title of the coupon 
• Description - This text is intended to be used as the offer details of the coupon (ex. Valid on any TWO products, excluding travel-sized products)
• Terms - This text is intended to provide the legal terms and conditions of the coupon.
• Mobile Image URL
• Desktop Image URL
• Dollar amount - This text is intended to provide the savings value to the consumer.

E-commerce redemption with Fetch Code

Time Bound fetch can be used to generate alpha-numeric codes to facilitate e-commerce transactions. For more information on e-commerce redemption implementation, visit this blog post. E-commerce redemption application is still in beta testing, if you have an interest in contributing to the in-market implementation of e-commerce redemption, please reach out to your TCB representative. 

Coupon Display Requirement

At the request of a national retailer partner, TCB will require all distribution providers to include “SCAN FROM PHONE TO REDEEM” into the AI (8112) consumer experience.  This language is included on the only mobile coupons they currently accept which are their own distributed mobile coupons. To maintain consistency with cashier recognition, we agreed to incorporate this language. The language must be present near the barcode.

Additional Coupon Display Guidelines

The following is an excerpt from the JICC Voluntary Guidelines for Digital Coupons as it pertains to recommended components of a mobile coupon display:

*The JICC recommends the following data elements be contained within the visual display of the offer
on an internet website or mobile device.

• Clear identification of the product to be purchased (for example brand name and/or variety)
• Image of the product to be purchased
• Face value
• Expiration date
• Offer short description - this is typically a brief explanation of the offer
• Offer long description (optional) — this may include additional qualifiers or details about the product. Availability may be dependent on whether the website allows or has room for this additional verbiage.
• Purchase Requirements — often this is also included in the offer short descriptions, but it can be noted again in relation to face value (e.g., $0.50 off 2)
• Legal Copy— these are often provided via a link, a “hover” or “pop-up
• Limitations — this may be contained within short description, terms and conditions, or states separately (e.g., “Limit 2 per household” or “Excludes trial size”)
• Issuers should also consider associating each offer with a product category to support search and filter capabilities.*

Provider Certification

Our Provider Certification ensures all providers have appropriately developed the minimum functionality required to distribute AI (8112) coupons to consumers.  The components of certification are as follows: 

1. Ability to successfully deposit non-sequential serialized data strings 
2. Proof of consumer experience for each presentment methodology (Ex. mobile coupon application, native phone wallet, PWA) that includes serialized data string presented in a barcode with fetch code functionality. 
3. Documentation of consumer authentication, bundling capabilities, and security and performance.

For more information regarding Distribution Provider requirements or certification, contact us now!