Loyalty glossary · 8. Technology and architecture (25)
Rules Engine
A rules engine is the software component that applies a loyalty programme's published conditions to member activity, producing points, qualification, or status changes through deterministic logic rather than probability.
A rules engine is not a forecasting tool. It answers one question at a time: does this specific member action meet the conditions for an accrual? If the condition is one point per one dollar spent, the engine checks the dollar amount and applies the multiplier exactly. No sampling, no probability distributions, no expected value. That directness is what makes the engine trustworthy.
Activity based qualification makes the software more complex but no less determinate. A programme might demand fifteen nights or ten stays inside one calendar year before awarding a higher tier. The component counts each stay and compares that running total against the threshold. It does not guess whether a person will stay again or whether the pattern suggests loyalty. It only logs what has already happened and reports whether the target is met.
The trap appears when operators treat a rules engine as if it were an actuarial model. Those two things answer opposite questions. An actuarial model estimates how many members will qualify under a future scenario. A rules engine already knows which members did qualify under the rules in force at the time. Blurring that line lets a programme change the past by silently editing the rules, because the old calculation disappears. That is not modelling, it is rewriting history.
The arithmetic exposes the real difference. Set an earn rate at 1.5 points per 1 dollar spent. A member who spends 200 dollars earns 300 points under that rule. Raise the rate to 2 points per 1 dollar and the same spend earns 400 points, a 100 point difference with no change in member behaviour. The engine does not predict which outcome is better for the programme. It just executes whichever rule is active, and the active rule is a decision someone must own.
A rules engine must be versioned. Every change to a condition, a threshold, or a tier requirement leaves a permanent record that auditors can replay against past activity. Without that record, the engine becomes an actuarial model in disguise: it can be tuned after the fact until the numbers tell whatever story the operator wants. Versioning is not a technical luxury. It is the difference between a loyalty programme that can prove its own rules and one that merely asserts them.