Eligibility and Validation
An offer applies at checkout only when all eligibility checks pass. These checks are driven by what you configure across the offer Details, Payment Modes, and Setup tabs. This page explains each check so you can understand why an offer was or was not applied.
Eligibility Criteria at a Glance
| Check | Condition | Configured In |
|---|---|---|
| Validity period | Transaction time must fall within start and end dates | Details |
| Payment mode targeting | Payment mode must match targeting rules | Payment Modes |
| Product matching | Cart must contain eligible products (if specific products are configured) | Setup |
| Order amount | Order total must be within min/max order amount constraints | Details |
| Order quantity | Order quantity must be within min/max quantity constraints | Details |
| Usage limits | Total, per-user, per-card, and per-UPI limits must not be exceeded | Setup |
| Priority uniqueness | Active offers must have unique priority per sub-merchant | Details |
| Coupon code | If the offer has a coupon code, it must be provided | Details |
Validity Period
The offer's start date and end date define when it is active. A transaction must occur on or after the start date and on or before the end date. Offers outside their validity period are automatically excluded.
Payment Mode Matching
The payment mode used by the customer must match the offer's payment mode targeting. This includes the payment mode itself and all sub-criteria (card network, BIN, UPI flow, bank, wallet provider, and so on). For details on each payment mode's targeting options, see Payment Mode Targeting.
Product Matching
If the offer targets all products, the product check passes automatically. If it targets specific products, at least one SKU in the cart must match the offer's product list, and all product-level constraints (min/max amount, min/max quantity) must be satisfied. For product configuration details, see Product Configuration.
Order Amount and Quantity
If you set a minimum order amount, the order total must be at least that value. If you set a maximum order amount (with a value greater than 0), the order total must not exceed it. The same logic applies to minimum and maximum order quantity constraints.
Usage Limits
Usage limits prevent an offer from being redeemed more than the configured number of times:
- Max usage -- total redemptions across all customers. A value of 0 means unlimited.
- Max usage per user -- maximum redemptions by a single customer. A value of 0 means unlimited.
- Max usage per card -- maximum redemptions using a specific card. A value of 0 means unlimited.
- Max usage per UPI ID -- maximum redemptions using a specific UPI ID. A value of 0 means unlimited.
Usage is tracked in real time during order processing. Each limit is checked independently, and all must pass.
Priority and Offer Selection
Each active offer must have a unique priority (greater than 0) within the same sub-merchant. When multiple offers are eligible for a transaction, the system selects one based on priority and the sub-merchant's tiebreak strategy.
The tiebreak strategy (highest offer, lowest offer, or priority-based) is configured at the sub-merchant level. Contact Nimbbl support to set or change this configuration.
Validation at Creation
The UI enforces validation rules when you create or edit an offer:
- Construct-based required fields (percentage requires a value, random requires a min and max range).
- Allowed combinations (some constructs may not be available with certain offer types).
- Ranges and relationships (max must be greater than or equal to min, values must be positive).
- End date must be on or after the start date.
- Priority must be greater than 0.
For the creation workflow, see Creating Offers. For management workflows, see Managing Offers.