Real-time engine for complex promotions, decided at payment
Qurable’s promotion engine decides complex promotions in real time, in ~150 ms (stackable, buy X get Y, bundles, tiered, basket, and bank or card conditions), at the POS, online, in the app, and at the kiosk. 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.
Fuel, restaurant, and retail programs already decide their rewards at payment with Qurable.
Read the MostaClub case- ~150 msReward decisionInside the authorization
- < 50 msMember identificationp95, server-side
- 99.5%SLACommitted availability
- 3,000/sPeak in a single programMostaClub: 2.7M requests in 15 min

+0Every reward, inside the campaign cap
3,211USD
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 right customer, at the register (QR, wallet pass, or card), in your ecommerce, or in Qurable's white-label checkout |
| When they get it | At the register, the same discount for everyone | At payment, decided in ~150 ms, or afterward, as a coupon for their next purchase, based on their profile |
| Who runs it | One tool picks who, and another system applies the coupon | The same engine decides, applies it at payment, and deducts it from the budget |
| If several apply | They stack, or the first match wins | The best one available, with priorities and exclusion groups |
| Complex promotions | One simple discount at a time, or custom development for each combination | Stackable, buy X get Y, bundles, tiered, basket, and bank or card conditions, evaluated in real time |
| Channels and integration | Tied to the POS or to a vendor portal | API-first: the app, ecommerce, POS, and kiosk use the same engine through the API |
| Budget | Known at month-end close | Caps per campaign, checked before the benefit is granted |
| How it's measured | By redemptions, and tested in production | Simulated before launch and measured against a control group |
From data to results
From each customer's data to the promotion that pays off.
Qurable decides at every purchase which promotion to give, to whom, and when, and shows you the incremental sales and what it cost.
01 · Data + AI
Behavioral audiences
What they bought, in which channel, with which payment method, and their tier; AI builds one-to-one audiences.
02 · AI Journey
The best promotion, at payment
With the receipt and the profile, AI Journey picks the promotion in ~150 ms, within your priorities.
03 · Simulation
The cost, before you spend
Simulated on the last 7 days of real data: how often it fires and what it grants.
04 · AI Journey
AI builds it, your team approves
Describe the campaign in one sentence and it's built; nothing goes live without your approval.
How it decides
Which promotion each purchase gets, and when to give it.
At every purchase, the engine filters the campaigns that qualify, applies your priorities and budget, and, based on the customer's profile, decides whether the reward comes at payment or on the next purchase.
- 2-for-1 on the coffee brandCo-funded campaign · priority 1Inside the cap
- 15% off her favorite categoryMoves to her next purchase, to bring her backNext purchase
- 10% off the whole purchaseSame exclusion group as the 2-for-1, lower priority
- Birthday couponDoesn't qualify: not her birthday month
- Weekend promotionDoesn't qualify: the purchase is on a Thursday
Cost and the brand's contribution in the ledger, with the trace of which condition matched and what didn't fire.
Simulation based on a hypothetical case.
Camila’s 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 doesn't go to everyone: it goes to people who buy coffee but not that brand yet.
Camila: shows her QR at the register and pays $45
The register doesn't change: the POS sends the receipt via 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 afterward, 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.
Promotion types
For everyone, for members, or one-to-one, in the same engine.
Every promotion has its own audience, budget, and cap. All four live in the same program and are measured the same way.
For everyone
A general promotion at the register or online, with its budget and cap.
- Example
- 10% off the whole purchase on Thursdays.
For members
A member price for whoever identifies at the register, in the app, or online.
- Example
- Club members: special price on coffee.
Targeted, one-to-one
For a behavioral audience, at payment or as a coupon for the next purchase.
- Example
- 15% off her favorite category.
Co-funded with a brand
A supplier brand pays part of the promotion and its contribution is recorded per campaign.
- Example
- Brand 50% and retailer 50%.
How it works
What it solves for each team.
Marketing wants to launch fast, finance wants to know the cost, and the register can't 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 dates, weekdays, and time windows, plus a cap and budget per campaign.
AI Journey
Describe the promotion in one sentence and it drafts the rule, audience, and coupon book from 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 days of real data, 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 didn't 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 doesn't respond, the sale still goes through.
Every event, by webhook
Coupons redeemed, points earned, and missions 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 days of real data: how often it fires, how often it doesn't 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 isn't 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 show the incremental sales from each promotion and what it cost.
- Guide
- Incrementality, cost, and ROI.
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.
Questions
What people ask about the promotion engine.
How it decides, how it's controlled, and how it connects.
It's 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.
Yes. The engine evaluates, in ~150 ms, stackable promotions, buy X get Y (2-for-1, 3-for-2), bundles, tiered discounts, basket rules, and payment-method conditions such as the bank or card. MostaClub applies them in its app checkout, at the POS, and at the self-service kiosk, and Shell Box uses them with bank and card conditions. At peak, MostaClub alone processed 2.7 million requests in 15 minutes, about 3,000 per second.
Yes. The whole engine is used through the API: the app, ecommerce, POS, and kiosk ask the same engine for the promotion and get the decision in real time. The API is public and accessed with authorized credentials, and every promotion applied goes out by signed webhook.
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 afterward, 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 days of real data 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 doesn't 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, via API. Qurable is already live with clients on POS systems such as Oracle, Microsoft, and Napse (TOTVS) and on ecommerce platforms such as VTEX. The register system doesn't change: Qurable decides the promotion and the register applies it. If the service doesn't respond, the sale still goes through.
Yes, in the promotion builder, with the budget included. To know how much a promotion sold compared with not running it, you need a control group: in Qurable, it's designed with each program, starting in the pilot.
Yes. With AI Journey you describe the promotion in plain language and it drafts the rule, audience, and coupon book from your program's catalog. Anything the platform can't 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
Related guides
All resources- ConceptAPI-first, headless loyalty
API-first means all of the program logic lives in the API before any screen; headless means each channel runs its own frontend.
- ConceptReal-time loyalty
Real time means earning, balance, rewards, and events happen while the customer is buying, not in an overnight batch.
- ConceptSupplier-funded promotions
A supplier-funded promotion is paid, in full or in part, by the brands that sell to the retailer.
More guides
Compare alternatives