Marketing
The onsite loyalty engine: points, rules and a ledger you can audit
Loyalty plugins usually fail an audit for the same reason: they show a balance but cannot explain it. GoGee's loyalty engine is a ledger first, every points movement is a row with a reason attached, and a rewards programme second.
It is native to the platform, so points, vouchers and combo deals share the same customer record, the same order data and the same admin.
GoGee feature series · 23 of 33
How it's actually built
- Ledger
- One row per points movement with a running balance
- Earning actions
- Configurable actions with point values, enabled per store
- Programme settings
- Store-level loyalty settings record
- Redemption
- Points converted into vouchers issued to the customer
- Voucher link
- Loyalty-issued vouchers carry their source, so discount is traceable
- Customer view
- Balance and history in the member account area
- Admin
- Loyalty administration screen (beta)
- 01Input
Ledger
One row per points movement with a running balance
- 02Deterministic
Earning actions
Configurable actions with point values, enabled per store
- 03Deterministic
Programme settings
Store-level loyalty settings record
- 04Deterministic
Redemption
Points converted into vouchers issued to the customer
- 05Output
Voucher link
Loyalty-issued vouchers carry their source, so discount is traceable
Onsite loyalty engine, data flow, generated from the shared GoGee feature diagram template.
Points are ledger entries, not a counter
Every award and every redemption is written as its own entry with a reason and a resulting balance. That means a customer service query, "why do I have 240 points?", is answered by reading rows, not by trusting a number.
It also means loyalty liability is reportable. You can see what has been issued, what has been redeemed and what is still outstanding.
- Every movement is attributable to an action or a redemption
- Balances are derived from history, so they reconcile
- Nothing depends on a third-party loyalty vendor's API being up
Earning rules are configuration
Which actions earn points, and how many, is configuration rather than code: actions can be enabled, disabled and repriced from the loyalty settings without a deployment. Start with purchase-based earning and add the behaviours you actually want to encourage.
Redemption reuses the voucher system
Points are redeemed into vouchers, which means redemption inherits everything the voucher system already enforces: minimum subtotals, expiry dates, usage caps per customer and QR redemption at a counter. Because vouchers record their source, loyalty discount can be separated from campaign discount in reporting.
One honest boundary: tiered business loyalty is not implemented as an automatic tier engine, business pricing is handled through the catalogue's trade and quantity-break pricing instead, and the loyalty admin is still marked beta.
Questions we get asked
Is this a third-party loyalty plugin?
No. The ledger, earning rules and redemption all live in the same database as your orders and customers.
How do customers spend points?
Points are redeemed into vouchers, which carry the usual minimum-spend, expiry and usage rules.
Are there automatic business loyalty tiers?
Not as a tier engine. Trade and quantity-break pricing on the catalogue covers business-account discounting.
Read next
Marketing
Promotions engine
How GoGee runs promotions: fixed, percentage and store-credit vouchers with usage limits and QR codes, fixed-p…
Platform
Member sections & client logins
GoGee's member area gives each customer their own orders, invoices, vouchers, addresses, saved baskets and bus…
Ecommerce
Product catalogue at scale
How GoGee models thousands of SKUs: variant rows, quantity-break price tiers, role-gated business pricing and …