Best Practices
This section is for the programme owner and for finance, before go-live and every month after: the decisions the product leaves to you, and the jobs it does not do. Each item is a consequence of something recorded on an applet page or in the backend; if the product changes, the item goes with it.
The five things most worth knowing before go-live, in one place:
- The company member-point configuration has no screen and defaults to FINAL sales orders. Set it through the company API to the document type you actually sell on, or cash bills earn nothing (The setting with no screen).
- Points expire per lot, and only if the lot has an end date. An adjustment without a Valid Date To or a CSV row without one creates points that never expire (31 December 9000), and storefront points are written valid to 31 December 9999. A POINT treatment without a Validity Period awards nothing through the server’s fill-in pass; what the till records for it is not established (Points Expiry). Give every source a validity, then schedule the elimination processor, or nothing expires anyway.
- Nothing posts. There is no points liability, voucher liability or breakage journal — so somebody in finance carries it by hand, every month (what you owe your members). Reports for Finance come from the balance and transaction queries.
- Member Label rules do not filter — on the price book the counter calculator ignores them, on a commission scheme they pass for any labelled member. Tier logic goes on the class (Member Labels).
- Do not rely on a voucher’s dates alone to stop a late redemption. The till and the step at
FINAL check them, not every redemption route does, and nothing moves a lapsed ticket to
EXPIREDon a schedule. Have the expiry check called on a schedule, or expire the tickets by hand when a campaign ends (Voucher Management).
| Page | What it covers |
|---|---|
| Program design | What your two rates cost you, the terms you publish, what one bill may earn — and then the records that carry them: classes, price sets, point currencies and their validity, vouchers, the company configuration |
| Data management | What a member record holds, how members are created from four places, answering a member who asks what you hold, the CSV uploads, duplicates, and what the wiki says about PDPA |
| What you owe your members | Points are a promise, not a marketing cost — and nothing posts. The month-end accrual somebody runs by hand, breakage, the release at expiry, and which company in a group owes it |
| Security and compliance | The three ways points are stolen and the evidence that catches each, who to separate from whom, the permissions and settings that gate points edits and redemptions, what is audited, what is not a certification |
| Troubleshooting | Walking the chain when a member’s balance is wrong, putting points back the right way, and symptom / cause / fix for the rest |
The previous version of this section was a loyalty-programme playbook — value-return percentages, tier maturity models, RFM segments, session timeouts, incident-response plans — none of which described a control in the product.