Loyalty is an available module with separate programme, member, redemption and
adjustment responsibilities. It is a governed value ledger: published policies
and exact source purchases determine points, liability and reversals.
Screens and setup
At /app/[orgSlug]/loyalty, the operator sees Overview, Members,
Rewards, Rules and the permissioned Ledger. Settings and Series/Group
surfaces support the appropriate policy scope.
Overview leads with the four source-backed totals and a gallery of programme cards. Cards show current policy, activation and reward evidence; their Rules and Rewards links select that exact programme. Totals that require an aggregate roll-up remain unavailable rather than showing zero. Drafts retain their draft label and do not imply active earning. When no active organisation primary exists, an authorised manager can open the New programme pane with a live points-policy preview, then the first funded reward and the separate publication review. Closing the pane or changing tabs preserves the current local fields; it does not publish. The native earning model supports points per currency amount. The Brew+Ferment coffee integration adds a venue-scoped stamp programme beside these points programmes. Programme join codes and member till-scan credentials in design references remain outside this workspace.
Brew+Ferment Coffee Club, live from 19 November 2026. Its programme card shows the actual source stamp threshold and reward, customer count, current stamps, rewards earned and rewards redeemed. Members and history opens the coffee directory with exact email search, available rewards and paginated stamp/reward history. Source event IDs prevent duplicate imports; history is retained as evidence and does not award stamps again. Accounts excluded from Brew+Ferment reports remain visible with their exclusion, while programme totals omit them. Customers without a coffee card remain identifiable in the directory.
The dedicated server connection copies all source customers and coffee cards in pages of 50, followed by the complete coffee event history. Every 15 minutes it refreshes current customer/card snapshots and imports subsequent events. Updates replace each source account’s contribution to the saved totals. Unchanged snapshots avoid rewrites. A failed page retains its committed cursor for retry, and concurrent refreshes use one expiring lease. The initial totals remain provisional until a complete cycle finishes; the card displays the completed refresh time and a source error when necessary.
The source is bound to Brew+Ferment’s venue under its owning organisation. Programme totals require Loyalty view access; identities and history require Loyalty member access. An existing email match retains the source membership separately and shows CRM match needs review; an unverified source email cannot establish a cross-system identity link. New contacts carry no Soupy marketing consent or email-verification claim; the source preference is retained separately. Brew+Ferment continues to own stamping and coffee reward redemption. The synchronised balance is used for viewing and reporting in Soupy.
Staff-reviewed coffee customer links. A deployment administrator can apply a bounded review under an active staff identity with current CRM view/manage and Loyalty member access for the business and venue. Each selected membership must have one existing exact-email CRM candidate and corroborating full-name evidence or an explicitly confirmed name variation. Missing names, conflicting identities, shared emails and competing memberships remain separate until resolved. The operation rejects changed identity evidence, retains an audit receipt and safely replays the same request. It changes only the membership's CRM association and review flag; it creates no customer, profile edit, verification, marketing consent, purchase or reward entitlement. Ordinary 15-minute refreshes retain the reviewed association. There is no new web or native linking control in this support operation. Applying the reviewed Brew+Ferment links in production is a separate, separately approved data operation that has not run yet, so no membership has been linked this way; see Brew+Ferment coffee CRM review.
Implementation and release requirements are recorded in Brew+Ferment coffee import validation.
- Open the first-programme setup, choose the earning policy and create a concrete funded reward with cost, inventory, validity and fulfilment meaning.
- Review the exact earning, funding, liability and reward summary, then publish.
- Activate the intended organisation, Series or portfolio programme deliberately.
- Inspect Overview/Rules and an eligible canonical purchase to understand which primary programme and explicit promotion apply.
One deterministic primary programme applies to a purchase; only named published promotions add awards. Ticketing/Bookings completion supplies the earning fact. Policy changes do not reinterpret historical point lots. Pausing activation stops new earning/reward issue while existing claims retain evidence. Re-enabling the module does not revive an old activation automatically.
Serve a member and redeem a reward
In Members, find the exact customer and select their row. The layout keeps Member Loyalty service beside the list, stacking below it on narrow screens. Review balance, debt, eligible rewards and history, and choose an eligible reward. Review and confirm issue. The issued claim reserves points/inventory and returns a receipt showing the balance change.
The member directory lists only admitted account fields. It does not infer a programme, last-award date or dormant status. Rewards use voucher cards showing their exact points cost, value, terms and current availability. Remaining inventory is not a count of fulfilled claims. The workspace has no command to edit published reward terms or top up an existing reward version. Rules retain immutable policy versions and distinguish activation dates from publication. Ledger is the selected member's bounded history, with actual order or redemption references; it is not an organisation-wide ledger or a recomputed monetary value.
To fulfil a claim, use its service reference/QR, review the reward and explicitly
confirm Reward fulfilment. A pass or scan alone does not redeem value.
The workspace places the permissioned claim-reference field and
Review claim action in the header, retaining the separate confirmation.
The customer wallet at /org/[orgSlug]/loyalty verifies access to the
organisation-owned account; it does not infer marketing consent.
Refunds reverse the original earning lots even after Loyalty is disabled. Spent points may become explicit account debt, and later earning repays the relevant obligations. Naturally expired points are not treated as spent debt. Long ledger operations can show processing while an account is fenced; partial processing does not make a claim usable.
Point lots without an expiry date remain outside automatic expiry processing. Dated lots still expire when due. This prevents new incorrect claims; it does not itself repair historical ledger state or change the programme's frozen expiry policy.
Adjustments, portfolio links and permissions
For a correction, request a points adjustment with reason and evidence. An independent authorised approver reviews the frozen request and decides it. Legacy opening balances require governed evidence and approval; there is no editable balance field that bypasses the ledger.
Portfolio participation uses verified reversible links between organisation customers and a portfolio identity. Email matching is a discovery hint, never an automatic merge of balances, consent or tenant records. Revoking a link stops future reach while retaining history. Cross-Series conversion is not generally available without a separately governed conversion model.
| Responsibility | Capability |
|---|---|
| Programme/liability aggregates | loyalty.view |
| Member identity and service | loyalty.members.view |
| Policy and reward publication | loyalty.manage |
| Reward fulfilment | loyalty.redeem |
| Adjustment request / approval | loyalty.adjust.request / loyalty.adjust.approve |
| Settings | loyalty.settings.view / loyalty.settings.manage |