Decisions · Technology

Should loyalty accrual be real time or batch

Accrue loyalty points or miles in real time for any programme where a member can view, redeem, or transfer a balance immediately. Batch processing should survive only for internal adjustments and partner settlement. The main condition is that your ledger of record can accept idempotent real time writes; if it cannot, fix that before promising instant accrual.

The decision

Should loyalty accrual be real time or batch? The decision is whether the member's balance is updated at the moment of qualifying activity, or later in a scheduled run. The mechanism is the programme's ledger of record: a real time ledger uses idempotent writes and an event stream, while a batch ledger applies a daily or hourly file. Real time wins because accrual is a promise made at the point of sale or action; a delayed ledger breaks that promise silently. The exception is when the balance is not visible or spendable until statement, which is rare for modern programmes.

What it costs you

Real time accrual costs engineering capacity and a stricter transaction model, but batch costs you member trust and support burden. Illustrative calculation: suppose a programme runs 2,000,000 qualifying transactions per month and a batch delay causes one support contact for every 250 of them. That gives 8,000 support contacts per month. If each contact costs 4 dollars in agent time and 2 dollars in member goodwill, the monthly cost is 8,000 times 6 dollars, which equals 48,000 dollars. If real time reduces missing transaction contacts by three quarters, the avoided cost is 36,000 dollars per month, or 432,000 dollars per year. The same programme issuing one point per dollar on an average transaction of 40 dollars accrues 80,000,000 points per month. A real time ledger that costs 0.001 dollars per write would add 2,000 dollars per month in infrastructure, which is one eighteenth of the 36,000 dollars avoided monthly. The real cost of batch is this recurring member friction, not a one time project.

How to decide

Test: can your member open the app immediately after a purchase and see the points? If the answer is no and you are not an airline with a monthly statement, your accrual should be real time. Check your system of record for two properties: it must accept idempotent writes so a retried event does not double count, and it must expose a balance read that is consistent within one second of the write. If either property fails, the decision is not real time versus batch, it is replacing the ledger. Also ask whether members earn on external partner activity. If so, real time from partners may be impossible; the answer is to show a pending state immediately, not to move the whole programme to batch. For internal transactions, real time is the default.

What would change our mind

We would reverse this recommendation if the programme's primary interface is a monthly statement and members have no real time balance view, no instant redemption, and no transfer feature. In that case batch may be acceptable because the member never experiences the delay. We would also change our mind if the cost per idempotent write exceeded one cent at programme scale and transaction volume was high enough that real time processing would reduce margin below the value of member trust. A concrete threshold: if the incremental infrastructure cost of real time is more than 2 percent of gross margin and the programme has not measured any reduction in support contacts from instant accrual, batch is the cheaper honest choice. Right now, for a visible balance, real time is the only option that keeps the promise.

Related