If you're evaluating loyalty infrastructure for the first time — or explaining it to the person who signs it off — start here: what a loyalty programme really is, why it's harder than it looks, and how VariaOS runs one end to end.
Strip away the marketing and a loyalty programme is a simple promise: spend with us, and we'll owe you something back. Customers earn points on orders, climb tiers that improve their rate, and redeem value — often as spendable store credit. The catch is in the word owe: every point you issue is a small financial liability with a real monetary value. Multiply it by a million members and loyalty stops being a marketing gimmick and becomes a balance your finance team owns, your auditors will test, and your customers will notice the moment it's wrong.
That's the lens VariaOS is built through. A loyalty platform isn't primarily a points widget — it's the system of record for a liability, plus the rules that grow it and the redemption paths that settle it.
The naive build stores a balance field and mutates it. Under concurrency, retries, and refunds, mutable balances silently lose or double-count points — and there's no history to prove what happened. The correct build is an append-only ledger where the balance is derived, every change is an auditable entry, and corrections are new entries, never edits.
GDPR's right to erasure says delete the customer; your auditors say never touch the history. The resolution is cryptographic: encrypt each customer's personal data under its own key, and honour erasure by destroying the key. The person becomes unrecoverable; the financial record stays intact.
Orders arrive from a storefront, an OMS, or both — with duplicates, cancellations, and partial refunds. Members expect to see points in your app, not ours. Marketing wants the data downstream. Most of the real cost of loyalty is integration, which is why VariaOS is headless and API-first rather than another front-end to adopt.
One canonical path, six stages. Everything below is live in the private beta except where marked.
A headless, API-first loyalty engine: the ledger, the rules, the credit lifecycle, and the reporting — run correctly so you don't spend six months building them and the next six proving they're right.
Not a point-and-click campaign builder with a bundled front-end, not a CDP, not a CRM, and not a Salesforce add-on. You keep your customer experience and your stack; we run the hard parts underneath.
Our open-source widgets for a working member view in an afternoon, the REST API for ingestion, or GraphQL for reporting. The build-vs-buy analysis covers when you shouldn't buy at all.
Earning points from an order, computed by your rules at ingestion.
Spending earned value — here, store credit — against a purchase.
The append-only record of every point and credit movement. Never edited, only added to.
The derived current balance, maintained transactionally with its entries — fast to read, provable from history.
The monetary value of everything you've promised and members haven't spent. Finance owns this number.
Value that expires unredeemed. Healthy programmes measure it; ours reports it by age cohort.
A status level (Bronze/Silver/Gold…) that changes earn rates. Auto-qualified from activity here.
Points converted into spendable currency-denominated value, with type and expiry.
First-expiring, first-out — spending the credit that dies soonest, so members lose the least.
Sending the same order twice changes nothing. The property that makes integrations safe.
Honouring GDPR deletion by destroying a customer's encryption key — PII gone, ledger intact.
No bundled front-end. APIs and widgets instead — your experience, our engine.
The features page covers each capability in detail, the beta-status page says plainly what's live and what's on the roadmap, and the sandbox waitlist gets you hands-on.