How to build coupon and discount codes in Bubble

The simplest working way to build coupon/discount codes in Bubble is to create a Coupon data type, store things like code, amount/percent, expiration, and usage limits, then apply the discount at checkout by searching for a matching Coupon and adjusting the final price before you create an Order/Payment. You validate the code using conditions in the workflow (like “only when Coupon is not expired and is active”), and you update its usage count so each code behaves correctly.

Data structure that always works

Create a new data type called Coupon with fields:

• code (text) – what users type in
• type (text) – either "percent" or "amount"
• value (number) – discount value
• expires\_on (date)
• usage\_limit (number, optional)
• usage\_count (number, default 0)
• is\_active (yes/no)

This structure is enough for 95% of use cases and avoids overcomplicating things.

Validating a coupon

When the user clicks “Apply code,” run a workflow:

• Search for Coupon: constraints: code = Input Code’s value and is\_active = yes
• Add conditions: expires_on ≥ Current date/time and usage_count < usage\_limit (if you use a limit)

If the Search returns empty, the code is invalid. If it returns a Coupon, you move to calculation.

Applying the discount

Calculate a discounted price on the client side or store it on an Order object before you charge:

// Pseudo-calculation you'd do with Bubble expressions
final_price = coupon.type == "percent" 
  ? original_price - (original_price * coupon.value / 100) 
  : original_price - coupon.value

In Bubble, this is: original price − (original price \* Coupon’s value / 100) or original price − Coupon’s value.

After user successfully checks out

Add a workflow step to update the Coupon:

• Make changes to a thing → Coupon
• usage_count = usage_count + 1

This prevents overuse and keeps your system clean.