Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.omneo.io/llms.txt

Use this file to discover all available pages before exploring further.

How you configure redemption rules shapes customer behaviour as much as how incentives are earned. A well-designed redemption strategy drives the right actions at the right time.

​
In-store redemption

In-store redemption happens via Clienteling or direct API integration at the POS:
  1. Staff identify the customer (card scan, name/email search)
  2. Clienteling displays available balance and benefits
  3. Customer decides what to redeem
  4. Staff applies the redemption before processing payment
Key design decision: Do you allow staff to process redemption, or do customers self-serve via a barcode/QR at checkout? Staffed redemption is more reliable but creates dependency on staff knowledge and willingness.

​
Online redemption

Online redemption happens in the checkout flow via your eCommerce integration:
  1. Customer authenticates (account login)
  2. Checkout shows available reward balance or applicable benefits
  3. Customer opts in to apply their balance
  4. Redemption is created via API, discount applied in cart
  5. Order completes and transaction is recorded with redemption linked
Key design decision: Should redemption be automatic (always applied if available) or opt-in (customer chooses to apply)? Most brands use opt-in — customers feel the value more when they actively choose to redeem.

​
Minimum redemption thresholds

You can configure a minimum transaction value for redemption (e.g., rewards can only be applied on purchases over $50). This prevents redemption being used on trivial purchases and encourages meaningful transactions.

​
Maximum redemption per transaction

Limit how much of the cart value can be covered by rewards. Common caps:
  • 50% of cart value (ensures customer always pays something)
  • A fixed dollar cap (e.g., max $25 per transaction)
  • No cap (full wallet coverage)

​
Expiry and urgency

Reward expiry creates urgency and drives return visits. Key settings:
  • Send an expiry reminder email 2 weeks before expiry
  • Show remaining validity in the customer’s Profile Portal
  • Configure a “last chance” push notification if the customer has a mobile app

​
Benefit redemption

Benefits require explicit redemption — the customer (or staff) must actively select a benefit to apply. Unlike rewards, benefits are not auto-applied and do not pool. Configure max_redemptions per benefit instance to control whether it can be used once or multiple times.