Loyalty Register

Loyalty glossary · 8. Technology and architecture (25)

Composable Loyalty

Composable loyalty is an architecture where a programme's core functions, such as accrual, qualification, and ledgering, run as independent modules that can be replaced or reconfigured without rebuilding the whole stack.

Composable loyalty gets its power from separation. An accrual engine that is a standalone service can be swapped without touching the activity based qualification rules, but the two only stay coherent if they share an event contract. The contract is the product, not the modules.

The trap is not technical, it is organisational. A team that buys a composable stack and then runs it as a monolith, one deployment pipeline, one shared database, has bought modularity and thrown away the benefit. The architecture only pays off when you actually replace a module under live load, and very few operators ever do.

A programme with 1 billion points on a legacy accrual engine decides to move 20 percent of that liability to a composable partner ledger. That is 200 million points. The migration takes 12 months if done properly, and the actuarial model must reprice the remaining 80 percent on the old engine while the new module accrues at a different rate. The arithmetic is trivial, the governance is not.

Activity based qualification becomes the first casualty of composability because it is the one function that must see the whole member history to compute a tier. When that history is split across modules, the operator has a choice: rebuild a centralised query layer, which defeats the purpose, or accept that tiers update with a delay. Most accept the delay. That is a hidden cost no vendor quotes.

The actuarial model is where composability is finally judged. A modular ledger that updates in real time produces a liability stream that a monthly actuarial model cannot consume. The result is a forecast that is always a month behind the actual liability, which is worse than a monolith that was always wrong in the same direction. Operators should demand a streaming actuarial model before they sign the composable contract.

Related