Skip to main content
Question

Loyalty Program

  • July 3, 2025
  • 4 replies
  • 84 views

Forum|alt.badge.img+1

I’m building a simple, secure voucher-based loyalty points tracking system using Airtable. It will collect submissions from a Tally form where users enter their details and a unique voucher code. In Airtable, I want to have two tables: one for all voucher claims submitted by users, and another for pre-issued voucher codes that hold the actual point values. When a new claim is submitted, Airtable should automatically check if the voucher code exists and hasn’t been used before. If valid, it should award the correct number of points from the voucher code and link the claim to that voucher to prevent reuse. If the code is invalid (not found) or already used, the system should mark it clearly as invalid and award 0 points. I want to see which codes are used, track user submissions, and be able to calculate each user’s total points. The whole system should be ready to grow later — like adding referral bonuses or leaderboards — but for now, it just needs to cleanly verify codes, stop duplicates, and assign correct points.

4 replies

ScottWorld
Forum|alt.badge.img+35
  • Genius
  • July 3, 2025

Yes, that would be extremely easy to build in Airtable. If you’d like to hire the best Airtable consultant to help you build this, please feel free to contact me through my website: Airtable consultant — ScottWorld


Mike_AutomaticN
Forum|alt.badge.img+28

Hey ​@Zeee!

Do you have any specific questions we can help with?

Feel free to grab a slot using this call using this link, and we can further discuss your idea and I can show you around the ideal database architecture and best practices. 

Mike, Consultant @ Automatic Nation


TheTimeSavingCo
Forum|alt.badge.img+31

Does this look right?  If so, I’ve set it up here for you to check out

When the form gets submitted, the automation will look for an unused voucher code as well as a user with the same email address.  If it finds one of both, then it’ll link it up, and we use a rollup field to sum up the points

When someone uses a voucher code that’s already been redeemed, the automation will update that Submission record’s Status to be ‘Error’

Here’s how the automation looks and you can duplicate the base above into your own workspace to try it out!

 


MilhoanDesign
Forum|alt.badge.img+10

@Zeee you could try using this prompt for Airtable Omni and see where that gets you:

I'm building a secure, voucher-based loyalty points system. I need Airtable to help me set up the foundational structure. Users will submit a Tally form with their name, email, and a voucher code. In Airtable, I want two tables. One table will store all voucher claims submitted by users. This table should include fields for the user's name, email, voucher code, submission date, validation status, and points awarded. The second table will contain a list of all pre-issued voucher codes. Each record in this table will have a unique voucher code, a point value, and a status field to track whether it has been used. When a new claim is submitted, Airtable should automatically check whether the voucher code exists in the voucher code table and whether it has already been used. If the code is valid and unused, Airtable should mark it as used, award the correct number of points, and link the claim to the voucher. If the code does not exist or has already been used, the claim should be marked as invalid and assigned 0 points. I want to be able to track which codes have been used, view all user submissions, and calculate each user's total points by grouping or filtering by email. The system should also be designed in a way that allows me to expand it later to include referral bonuses and leaderboards. For now, it just needs to verify codes, stop duplicates, and assign points correctly. Please help me create the structure and logic to support this.