Promotion and coupon engine: the right promotion, decided at payment
Promotion and coupon engine
Qurable's promotion engine picks, in ~150 ms, which discount, coupon or bonus points each customer gets at the register, online or in the app. Your team sets the goal, the limits and the budget; Qurable decides, applies the promotion at payment and records the trace and cost of every decision.
In production
Fuel, restaurant and retail programs already decide their rewards at payment with Qurable.
Shell Box, ON by Axion Energy and MostaClub, among others.
- ~150 msReward decisionInside the authorization
- < 50 msMember identificationp95, server-side
- 99.5%SLACommitted availability
- 18MMembersIn programs running on Qurable
The difference
One promotion for everyone or the right promotion for each customer.
Choosing who gets a promotion is half the job. The other half is applying it at payment, protecting the budget and knowing what it cost.
| Same promotion for everyone | Decided at payment, with Qurable | |
|---|---|---|
| Who gets it | Everyone who goes through the register | The customer who fits, wherever they buy: at the register, identified by QR, wallet pass or card; in your ecommerce or in Qurable's white-label checkout, with their account |
| When it is decided | Loaded into the POS and applied the same to everyone | At payment, in ~150 ms, with the receipt, payment method and history |
| When the reward arrives | At the register, the same discount for everyone | At payment or after it, as a coupon for the next purchase, based on each customer's profile and to bring them back |
| Who executes it | One tool picks who gets it and another system applies the coupon | The same engine decides, applies the promotion at payment and deducts it from the budget |
| If several qualify | They stack, or the first match applies | The best available promotion, with priorities and exclusion groups |
| Budget | Known at month end | Budgets and caps per campaign, checked before the reward is given |
| Before going live | Tested in production | Simulation on the last 7 real days and A/B tests |
| How it's measured | By redemptions: how many coupons were used | Against a control group: the extra sales it drove and what it cost |
| Coupons | Codes that circulate and get reused | Single-use QR coupon, validated at the POS |
| Supplier promotions | Settled in spreadsheets | Each brand's contribution, recorded per campaign |
Camila case
Camila does her grocery run. She gets the promotion that fits her.
A supermarket, a coffee brand that wants new buyers and a campaign co-funded by both. The promotion does not go to everyone: it goes to people who buy coffee but not that brand yet.
Camila: shows her QR at the register and pays USD 45
The register does not change: the POS sends the receipt by API.
Qurable receives the itemized receipt and the payment method
Camila: does nothing; the promotion applies itself
If several qualify, each campaign's priorities and exclusion groups decide.
Qurable picks the best available promotion for Camila: the coffee brand's 2-for-1
Camila: sees the discount on the receipt
The trace stays: which condition matched and which effect applied.
Qurable records the brand's and the store's contribution per campaign, within budget
Camila: gets a single-use coupon for her next purchase
Based on her profile, the reward can arrive at payment or afterwards, to bring her back. The brand sees how many members of the audience bought the product.
Qurable delivers the coupon on the purchase confirmation screen, ready to validate at the POS
Simulation based on a hypothetical case.
How it works
What it solves for each team.
Marketing wants to launch fast, finance wants to know the cost and the register cannot slow down. The same engine answers all three.
Audiences by purchase
Built from what each customer bought and the attributes your program defines, for example people who buy the category but not the brand.
Coupons by day and time
Coupon books with validity, weekday and time window, with a cap and budget per campaign.
AI Campaign Agent
Describe the promotion in one sentence and it drafts the rule, audience and coupon book on your catalog; your team approves it.
Referrals and contests
Referrals that reward both sides and contests with their own rules, on the same engine.
Capped budget
Budget per campaign, limits per journey and exclusion groups, checked before the reward is given.
Test before scaling
Simulation on the last 7 real days, A/B tests and a control group that doesn't get the promotion: you see the extra sales, not just the redemptions.
Each brand's share
When a supplier brand funds part of the promotion, its contribution is recorded per campaign.
A trace of every decision
Which event arrived, which condition matched, which effect applied, and what did not fire and why.
No POS change
API integration with the POS and ecommerce: Qurable decides the promotion and the register applies it.
Single-use coupon
Single-use QR coupon validated at the POS.
The sale never stops
If the service does not respond, the sale still goes through.
Every event, by webhook
Coupon redeemed, points earned or mission completed go out as signed webhooks to your systems.
No stack rebuild
Connects to your POS, ecommerce, CRM and messaging tool; it replaces none of them.
Your data, in your warehouse
Every promotion, redemption and contribution is exported daily to your data warehouse.
The pieces
How a promotion is built.
From audience to measurement, every piece lives in the same engine as the points program, cashback and games.
| Piece | How it works |
|---|---|
| Who | What each customer bought, their tier in the program and the attributes your program defines. |
| Identification | A QR that changes every 30 seconds, an Apple Wallet or Google Wallet pass, a card or an account, in under 50 ms (p95). |
| Conditions | The itemized receipt, payment method, channel, validity, weekday and time window. |
| Across campaigns | Priorities and exclusion groups: the best available promotion applies. |
| Effects | Discount, coupon, points, partner points, badge, or an email or WhatsApp message. |
| At payment or after | A discount at payment or a coupon for the next purchase: Qurable picks the moment based on the customer's profile, aiming to bring them back. |
| After payment | A reward for the purchase or an upsell on the purchase confirmation screen. |
| Control | Budgets and caps per campaign, limits per journey and program guardrails. |
| Who pays | The retailer, or the retailer plus one or more brands, with each one's share per campaign. |
| Simulation | On the last 7 real days: how often it fires, how often it does not match and what it grants. |
| A/B | Two versions of the same promotion head to head, in the builder. |
| Approval | Nothing that affects members goes live without human approval. |
| Trace | Each decision stores which event arrived, which condition matched and which effect applied. |
| Data | Signed webhooks and a daily export to your data warehouse. |
| Incrementality | The control group is designed with each program, starting in the pilot. |
More than discounts
One engine for every way to reward.
Rules, missions, games and journeys use the same effects, budget and ledger: adding a mechanic is not a new project.
Gamification
Spin-the-wheel, scratch cards and five more mechanics, plus missions, badges and stamps, with the prize decided before the animation.
- Timing
- A game reaches your app in less than a week.
Supplier-funded promotions
The brands that sell to you pay part of the promotion and see their contribution per campaign.
- Example
- Brand 50% and retailer 50%.
Shared coupon books
Share a coupon book with a partner brand, with a term sheet stating which part of the cost each one pays.
- In practice
- The partner accepts or rejects it from its console.
Cashback
When the customer pays by card, the reward can be cashback decided inside the authorization.
- Live
- With Pomelo, Santander Peru and Banisi.
Points and tiers
Bonus points, multipliers and missions on the points program, with every movement on the ledger.
- In practice
- Double points for a segment, with a cap.
Measure the result
Simulation, A/B tests and a control group to know what each promotion sold on top and what it cost.
- Guide
- Incrementality, cost and ROI.
Questions
What people ask about the promotion engine.
How it decides, how it is controlled and how it connects.
It is the software that decides which promotion applies to each purchase: a discount, a coupon, bonus points or a partner reward, based on rules, budget and the customer. In Qurable that decision is made at payment, in ~150 ms, and each decision leaves a trace of which condition matched and which effect applied.
One that decides at payment with the customer identified, checks budgets and caps before giving the reward, integrates with the POS without replacing it and records each supplier brand's contribution. Qurable meets all four and runs fuel, restaurant and retail programs in Latin America.
A points program builds value for future purchases; a promotion engine decides the reward for this purchase. In Qurable both share the same customer profile, rules and ledger, so a promotion can give bonus points and a game can reward with a coupon.
Qurable picks the best available promotion based on each campaign's priorities and exclusion groups. The decision is stored: which event arrived, which condition matched and which effect applied, so if a customer complains you know why one applied and not another.
Both. Based on each customer's profile, Qurable can apply the discount at payment or deliver a single-use coupon for the next purchase afterwards, on the purchase confirmation screen, by email or by WhatsApp. The goal is to bring them back, with the cost of every reward inside the campaign budget.
Each campaign has a budget and caps, and the program adds limits per journey, exclusion groups and guardrails. Before going live, the promotion is simulated on the last 7 real days to see how often it fires and what it grants, and nothing goes live without human approval.
Yes. A promotion can be paid by the retailer and one or more brands according to an agreed percentage, and each one's contribution is recorded per campaign. Qurable does not move funds: it calculates the contribution and gets it ready for settlement.
With a single-use QR coupon validated at the POS. The customer gets it in the app, in the wallet pass or on the purchase confirmation screen, and every redemption goes out by webhook to your systems.
Yes, by API. Qurable is already live with clients on POS systems such as Oracle, Microsoft and Napse (TOTVS) and ecommerce such as VTEX. The register system doesn't change: Qurable decides the promotion and the register applies it. If the service does not respond, the sale still goes through.
Yes, in the promotion builder, with the budget included. To know how much a promotion sold on top versus not running it, you need a control group: in Qurable it is designed with each program, starting in the pilot.
Yes. With the AI Campaign Agent you describe the promotion in plain language and it drafts the rule, audience and coupon book on your program's catalog. Anything the platform cannot do is rejected before saving, and nothing goes live without your team's approval. With the MCP server, your AI agents can also operate the program.
Yes. Referrals that reward both sides, contests with their own rules, surveys, missions, badges, stamp cards and seven game mechanics run on the same effects engine, with the same budget and the same ledger.
They work together. Tools like Hightouch or Braze choose which offer to send to whom and leave execution to another system. Qurable decides at payment, applies the promotion at the register, online or in the app, deducts it from the budget and records its cost in the ledger. It takes your audiences by API and sends every event back by webhooks and to your data warehouse.
Talon.One and Voucherify are promotion engines with a global focus. Qurable decides the promotion inside the payment, records each supplier brand's contribution and has clients live in Latin America. We publish a comparison with each one, with public sources and dates.
Updated
How we start
You set the goal, Qurable runs it and measures it.
We start with one real campaign before deciding the full scope. Then, in stages: more campaigns, supplier brands and games. Live in 1 to 3 months.
- GoalA concrete target, like more frequency in a category or new buyers for a brand, with receipts from your POS or ecommerce reaching the engine by API.01
- Limits and budgetAudience, cap, budget and who pays each part, simulated on the last 7 real days before going live.02
- Go live and measureYour team approves; Qurable decides at every payment and measures against the control group we design together.03
Related guides
All resources- ConceptSupplier-funded promotions
A supplier-funded promotion is paid, in full or in part, by the brands that sell to the retailer.
- GuideLoyalty gamification with real prizes
A game with prizes has two layers: the one that shows it and the one that decides what it can pay and records it.
- GuideMeasure program results
Measuring a program means separating what it sold on top from what would have happened anyway.
Compare alternatives