Programme
Points per bill rounded down, tiers on the last 12 months, a birthday bonus, expiry oldest first and rewards, set per business.
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.
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.
What Loyalty does for you.
Points per bill rounded down, tiers on the last 12 months, a birthday bonus, expiry oldest first and rewards, set per business.
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.
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.
A suggested path for Loyalty. What you can do depends on your access in the app.
Points rules, tiers and rewards.
Add members at the counter or through /join.
Earn and redeem on every bill.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
Discount codes belong to Coupons; customer records to Customers and Contacts; billing at the counter to Shop.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
loyalties.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.