Solutions

Retention that does not depend on a plastic card

Turn the transactions you already record into a reward programme customers can actually see, across every channel you sell through.

Business problem

Loyalty programmes fail at the edges

Most retail programmes work in one channel and break in the others. The card works in store, the account works online, and the two disagree about the balance.

Meanwhile the rules live in a checkout integration nobody wants to touch, so the programme never changes and customers stop noticing it.

Solution

One balance, every channel

Your systems record what happened — an order, a return, a visit — and reward rules decide what it is worth. The customer holds one wallet regardless of where the transaction occurred.

Marketing changes rules without a deployment, and every issuance stays attributable to the rule version that produced it.

Architecture

How it fits together

  1. Checkout01

    Order events from web and store

  2. Rules02

    Spend, frequency and category logic

  3. Wallet03

    A single customer balance

  4. Redemption04

    Applied at the till or basket

Representative scenario

A multi-location retailer with an online store

Point-of-sale and ecommerce both send order events. A rule issues a base rate on spend, with a category multiplier and a monthly cap. Refunds emit a reversal event, so the balance corrects itself without manual adjustment.

Redemption applies at checkout as a discount, and the ledger records both the redemption and the retirement of the asset.

This is an illustrative scenario showing how the platform would be applied. It is not a customer reference, and no figures in it are measured results.

Benefits

What changes for the business

One customer view

Store and online activity resolve to the same customer and the same balance.

Rules without releases

Campaign changes are configuration, not an engineering ticket.

Refunds handled

Reversals are part of the model rather than a support task.

Explainable balances

Any balance can be traced to the events and rule versions behind it.

Implementation time

A realistic sequence

Setup
Days 1–3
First rules live
Week 1
Customer-facing
Weeks 2–4
Optimising
Ongoing

Want to see this mapped to your business?

Describe what you run today and we will come back with the specific configuration rather than a generic deck.