Accrual Flow

Compute with reward, commit with confirm-transaction — the two-step accrual, rewarding from the app, and bulk uploads from a sheet

Earning happens in two beats: the platform first calculates what a purchase is worth, then awards it when your till confirms. The customer-visible result is instant; the safety comes from the split.

Beat 1 — Calculate

Your till or website sends the purchase in (calculate points). The answer is a full preview:

The preview shows	Why it matters
Which rules matched	Staff can explain the math: base earning plus the festival bonus
Points per rule and the total	Show it on the bill or screen before anything is final
Any ceiling that trimmed the total	Transparent when a cap kicked in, and by how much

Nothing has been awarded yet — abandoning at this stage leaves no trace, and the preview costs nothing to repeat.

Beat 2 — Confirm

The till confirms using its own bill reference (confirm), and the points land — all at once, never partially.

Confirming twice? The second is acknowledged and ignored — points cannot land twice.
Took too long? After the confirmation window the calculation lapses; just calculate again — nothing happened.
If the customer owed points from an earlier reversal, the new points settle that debt first, automatically; only the remainder becomes spendable.
Points start their lifetime and any waiting period from this moment — see Maturity & Expiry.
When centres are separated, the confirmation names the centre, and the points belong to it — see Centres & Store Separation.

Beat 3 — Tell the Customer

The customer's WhatsApp message for this earning moment goes out automatically as part of the confirmation when Message the member is on (or per call over the API), or when the till triggers it (send notification) — sent once, with the template and schedule you configured. See Notifications.

Rewarding From the App

The same two beats run from Patient Profile → Reward: enter the bill number (also the key that prevents a double credit), amount and date, the centre when points are centre-specific, optionally the items (only needed when a rule earns on what was bought), and under Advanced the discount, tax, payment method, channel and your own fields for a rule to match on. Calculate points shows the total and the rules that awarded it; Confirm reward credits it. “No points matched this bill” means no earning rule fired — check the rules.

Points Without a Till: Upload Accruals

Points can also be credited to many members at once from a bill export — Upload accruals takes a CSV or Excel sheet up to 5 MB; download the template from the page.

Column	Required
phone, bill_no, bill_date, amount	Yes
store_code	When centres are separated; an unknown code rejects the row
category, sku, item_name, item_amount, item_category, quantity, item_discount, item_tax	Optional — rows sharing a bill number are treated as one bill with several items

Points are worked out by your earning rules, exactly as at the counter. The page tracks the sheet through Queued, Crediting and Done, counting bills credited, already credited, matched no rule, or failed, and lists the rows that were rejected with what to fix. Bills already credited are skipped on a re-upload, so nothing doubles up. Uploaded points fire their own notification event — Points earned from an uploaded sheet — so the message can differ from the counter one.

What You Configure

Setting	Your options	Default
The earning rules themselves	Events, rates, conditions, item awareness, priorities — see Earning Rules	—
Hold points for	Minutes a calculation stays confirmable	10
Stop after this many rules match	Highest priority first; blank lets every matching rule pay	All
Round awarded points	Whether awards are rounded to whole points, per rule or on the bill's total	Off
Share-of-bill caps	Points capped as a share of the bill, with overrides per tier, category, payment method and channel	None
Fixed ceilings	Per transaction, per day, per month — plus per-tier and per-category overrides	None
Combine caps by	No cap / percentage only / amount only / both — whichever caps lower / both — whichever caps higher	—
Tiers	Per-tier earning multipliers and optional per-tier ceilings — see Tiers & Multipliers	—
Point lifetime and waiting period	Per rule, with tenant defaults — see Maturity & Expiry	1 year / immediate
Message the member	Whether confirming also sends the customer's WhatsApp message	Off

For developers

The exact request and response formats for all three steps are in the interactive API reference — follow the inline links. `store_code` is required on every call while centres are separated; `auto_send_notification` on the confirm call overrides the tenant default.