Skip to app details
Back to app library
APPNEURAL APP FAMILYCommerce

Loyalty

Points and rewards your customers come back for

Give customers points and rewards: add members by phone, earn and redeem at the counter, and let them join and show their card on their phone.

01 / OVERVIEW

See where it fits in your day.

Members are added by phone with consent and get a card link and QR. Points are earned per bill, rounded down once, with tiers on rolling 12 months, a birthday bonus and expiry oldest first. The ledger is add-only, refused by the database to edit or delete, and never goes below zero. Redeeming is a hold that is committed or voided and lapses by itself. The counter page finds a member by phone or by scanning their QR. Rewards can issue one-use voucher codes through Coupons with the domain's own key. A daily run lapses holds, expires points, gives birthday bonuses and refreshes tiers. Reports show points and members by day. Public pages: /join for self sign-up, which staff confirm at the counter before any points count, and /m/<token> for a member's card. API /api/v1/members/lookup, members, earn, redeem and program with an API key or the workspace key; webhooks points.earned, points.redeemed and tier.changed. An optional Claude note suggests what to do next from totals only. Not built: SMS or messages, returns reversal, category multipliers from the counter. Shop and Store do not call Loyalty yet.

A LOOK INSIDEExample layout · sample content
Members
MemberTierPoints
AaravloyaltyEXAMPLE
MeerapointsEXAMPLE
RohanrewardsEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Loyalty does for you.

01

Programme

Points per bill rounded down, tiers on the last 12 months, a birthday bonus, expiry oldest first and rewards, set per business.

02

Counter

Find a member by phone or by scanning their QR, earn on a bill, redeem as a hold that is committed or voided; an add-only ledger that never goes below zero.

03

Members and reports

A public /join page and a member card at /m/<token>; reports by day for points and members; an API for the shop to earn and redeem.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Loyalty. What you can do depends on your access in the app.

01

Set up

Points rules, tiers and rewards.

02

Sign up

Add members at the counter or through /join.

03

Reward

Earn and redeem on every bill.

YOUR NEXT MOVE

Make Loyalty part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Members are added by phone with consent and get a card link and QR. Points are earned per bill, rounded down once, with tiers on rolling 12 months, a birthday bonus and expiry oldest first. The ledger is add-only, refused by the database to edit or delete, and never goes below zero. Redeeming is a hold that is committed or voided and lapses by itself. The counter page finds a member by phone or by scanning their QR. Rewards can issue one-use voucher codes through Coupons with the domain's own key. A daily run lapses holds, expires points, gives birthday bonuses and refreshes tiers. Reports show points and members by day. Public pages: /join for self sign-up, which staff confirm at the counter before any points count, and /m/<token> for a member's card. API /api/v1/members/lookup, members, earn, redeem and program with an API key or the workspace key; webhooks points.earned, points.redeemed and tier.changed. An optional Claude note suggests what to do next from totals only. Not built: SMS or messages, returns reversal, category multipliers from the counter. Shop and Store do not call Loyalty yet.

A points and rewards programme for a connected domain's customers: members by phone with consent, earn and redeem at the counter, tiers, expiry, rewards with one-use vouchers from Coupons, a public join page and member card, reports, and an API with webhooks.

Discount codes belong to Coupons; customer records to Customers and Contacts; billing at the counter to Shop.

Priority
P2
Portfolio
Commerce
Capability
Commerce
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:16
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

loyalty schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

loyalty.appneurox.com DEPLOYED

loyalty.appneurox.com

Worker
loyalty-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:16
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/loyalty-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app