Loyalty glossary · 8. Technology and architecture (25)
Headless loyalty
Headless loyalty is a loyalty architecture that separates programme logic and data from the member-facing presentation layer, allowing the programme to be delivered through different channels.
Headless loyalty puts programme logic behind interfaces rather than tying it to one member-facing application. The architecture is composable, so a team can connect loyalty capabilities to the channels and products it operates.
API-first is the governing implementation choice. Programme actions and data are exposed for other systems to call, which lets the member experience live in more than one presentation layer. The loyalty programme remains the source of the underlying rules and records.
A rules engine is one of the components that makes this separation useful. It evaluates the conditions for earning, rewards or other programme actions independently from the screen where a member sees the result. That keeps a change in presentation from requiring a rewrite of the programme logic.
A promotion engine handles a different concern. It supports promotional behaviour inside the architecture, such as a temporary offer or a campaign-specific incentive. Keeping promotion logic distinct from the general rules engine makes the source of a member outcome easier to identify.
Composable loyalty names the broader architecture. Headless loyalty describes the separation between the programme services and the front end. API-first describes how systems access those services. Rules engine and promotion engine describe two kinds of logic that can operate behind the experience.
The practical test is whether a new channel can use the same programme capabilities without rebuilding the currency, rules and promotion logic. If the answer is yes, the architecture has the separation that headless loyalty requires.
If one rules service records 2,000 earns from a mobile channel and 500 earns from a web channel, the shared service holds 2,500 earn events in total. If each event awards 10 points, the member ledger receives 25,000 points, illustrating how one programme capability can serve several presentation layers.