Customers
A lightweight CRM to target benefits at specific people or segments, check eligibility and keep a history of what each customer has already used.
Promotions, coupons, wallets, gift cards, referrals and loyalty, managed from a single platform by a single team.
Each module solves a different problem, but they all read the same rules, the same customers and the same catalog.
A condition is met. A benefit is triggered.
Every rule, in every module, runs on the same model and goes live instantly across all your channels.
You change what you configure, never how you configure it. A 3-for-2, a gift with purchase and double points all follow the same logic: a condition and a benefit.
For your merchandising team, that means launching new campaigns without learning a new tool. For your engineers, it means one set of logic to maintain.
IF order.subtotal >= 150 && customer.segment == 'vip' AND NOT order.items.contains('restricted_category') THEN trigger.benefit({ type: 'gift_with_purchase', sku: 'premium_glass' }) > STATUS: rule evaluated and approved for checkout #9012
IF item.category == 'dairy' && item.quantity >= 3 THEN trigger.benefit({ type: 'nxm', buy: 3, pay: 2 }) > STATUS: applied at line level on cart #8821
IF order.channel == 'in_store' AND item.category == 'personal_care' THEN loyalty.earn({ multiplier: 2 }) > STATUS: earn recorded as an independent transaction
Pick a module to see what it can do and what it looks like in day-to-day operation.
Any promotion retail runs today, with the controls to keep it from leaking margin.
Sample promotion settings
| Type | 3 for 2 on dairy |
|---|---|
| Schedule | Friday to Sunday |
| Region | All stores except Monterrey |
| Channel | In store |
| Limit | 2 uses per customer |
When an order changes after payment, the promotion is re-evaluated automatically.
Sample order events
Reward the whole relationship, not just the purchase, in any channel.
Sample ways to earn
Illustrative values. Every business sets its own.
The recommendations already happening among your customers, rewarded and measured.
Sample referral loop
Test every rule before it reaches a customer, and understand what each promotion really costs.
Sample simulation
Promotions, products and customers are the three most-used areas in Payloot. Two supporting modules keep that data in order.
A lightweight CRM to target benefits at specific people or segments, check eligibility and keep a history of what each customer has already used.
Your catalog, mapped in so every rule knows which products it covers, and every cart validated before a benefit is calculated.
Promotions show up at every step, calculated at the line-item level, so customers know what they'll pay before they pay it.
For engineers: messages are exposed on product listing pages (PLP), product detail pages (PDP), cart, checkout and your order management system (OMS).
| Without Payloot | With Payloot |
|---|---|
| Promotions, loyalty and coupons scattered across tools | One engine that handles transactions and rewards together |
| Each channel with its own rules | The same rules on web, app and in store |
| Changes that take hours to show up | Changes live instantly |
| Campaigns set up store by store | Rolled out through your ERP's store hierarchy |
| Orders that lose their discount when they change | Orders that recalculate themselves |
| Promotions published without knowing what they'll cost | Every rule tested in the simulator before it goes live |
The two ways to implement Payloot, what you need to get started and what happens behind every promotion.
Architecture, REST API, live evaluation, field mapping, security and the real scope of the platform.
We'll show you what your rules, your channels and your customers look like on Payloot.