Coupon, Voucher, and Pass Validation
Notably, it’s a challenge for brands and merchants to validate mobile coupons, vouchers, or passes. Nevertheless, it’s important that they do so because these mobile media ‘objects’ are easy for consumers to copy. For example, a consumer can simply take a screenshot of a barcode and then share it with anyone.
What about ‘print-at-home’ coupons, vouchers and passes, received by consumers via email? Also, you can easily copy and share those many times. Fortunately, codeREADr’s apps for iOS and Android devices can scan and validate both printed and mobile objects. Also, the platform is not for the exclusive use of any single service provider or POS system. In that way, we can support many service providers and achieve an economy of scale. Therefore, we can inexpensively offer sophisticated validation services that are easy to deploy.
Validation Against a Database
For this type of service, you need a database of valid coupon, voucher or pass IDs – a ‘validation database’. When the app user scans the barcode ID, you can deploy a simple valid/invalid redemption approval procedure with codeREADr. Also, in the ‘response text’, you can give the app user directed information about the marketing program or transaction. For example, you can show them general terms and conditions for redemption. Also, you can show specific information about the unique code, such as VIP treatment, awards, etc. Moreoever, you can present the response text in simple text, HTML or link(s). In addition, developers can create web and contextual content (see Advanced below).
<< Step by Step Instructions. >>
Validation Without a Database (or with a Partial Database)
In some cases, the database of coupon, voucher, or pass IDs is not readily available to validate against. Perhaps that data (or a portion of it) is confidential, or the file is too large. Also, it could be difficult to make available to a third party. Generally, such difficulties come from the system creating the IDs in real-time without our APIs.
Essentially, you can follow the instructions above for validating against a database. Also, instead of uploading all or some of the values to our server, you can create and name an initially empty or partially complete database.
After electing to create a Validation service, look for the ‘Pattern Validation’ option. You do not need to create a pattern, though it’s better if you do because it reduces the potential for ‘fake’ IDs. However, you can leave the pattern field blank. See here for details on validation patterns.
To check for duplicate scan, you do need to check the box that says, ‘Add scanned value and response to the database when a match is made’. This will auto-insert all unique ID scans to the database that you created. You can add a default response as text or HTML (Webify).
The app will first check online or on-device if the scanned ID is in the associated database. First, if it is, it will validate against that. Secondly, if it isn’t, but it matches the defined pattern, it will be validated and auto-inserted into the database. Also, if you checked the ‘Add scanned value…’ box, then it will automatically add itself to the database if it’s not already there.
Conditional Validations based on Duration, Days, Dates, Counts
In some cases, you may need more than just Valid, Invalid and Invalid Duplicate responses. Optional, conditional validations include:
- Minimum and/or maximum number of scans to make a scan valid.
- Start and end date range and/or a start and end time for when scans are valid.
- Duration from the first scan after which scans will be valid.
- Day ranges when scans are valid.
- Option: Validation Over-Ride where a condition can be different for certain values scanned.
These options offer a simple way to add somewhat complex validations to your services without requiring a developer. For detailed instructions please look here.
Custom On-Device Validations
Increment/Decrement against a Database Value
With this option, you can use the associated database to include a specific value. This can be incremented or decremented based on a scan (1:1) or on input from the user (including decimal inputs). Before entering a new increment or decrement value, the user will see the current status after each scan so they can choose whether or not to enter a value. Please look here for instructions.
Integration via the Zapier API Connector to Third Party Databases and Services
The Zapier API Connector enables the use of third-party databases and services to send database values to codeREADr servers and codeREADr servers to send scan records to those databases and services. In that way, you can help automate the flow of data. Please look here for further information.
IT/Developers can seamlessly integrate codeREADr into their existing POS and CRM applications and back-end systems using our extensive set of APIs. The can also use advanced features such as Postback URL, regular expression, contextual variables and Webify for special interaction with the consumer via the app. For example, you could alert the app user that certain barcode IDs when scanned receive special consideration (discount, prize, etc.).