Loyalty glossary · 8. Technology and architecture (25)
Middleware
Middleware is the software layer that sits between a loyalty engine and the systems that record member activity, translating transaction data into a format the engine can process.
Middleware is not a neutral pipe. It decides what counts as a member activity, and that decision feeds accrual calculations and activity-based-qualification rules. A programme that treats middleware as plumbing will find its earn rates and tier thresholds being silently rewritten inside code that nobody reads.
The trap is that middleware absorbs rules that should live in the loyalty engine. A promotion that requires three stays in six months might be coded in middleware as a filter, not in the engine as a configurable rule. When the promotion ends, the filter remains, and the active-member-rate drops because qualifying activity is missed.
Work the arithmetic. A programme should post 1,000,000 points each month. If the middleware error rate is 5 percent, then 50,000 points never reach member balances that month. Move the error rate to 2 percent and the programme recovers 30,000 points per month. That shift can change the active-member-rate by 3 percentage points for members whose activity was lost.
The active-member-rate is a lagging indicator of middleware health. A member who earns points but sees no balance update stops engaging, and the programme records inactivity that was caused by infrastructure, not by disinterest. That misclassification makes the rate useless for decisions.
Middleware should be thin, configurable, and audited. Every rule it enforces must be visible in the loyalty engine, and any change to middleware must be treated as a change to member-facing terms. Programmes that buy a middleware product to avoid custom integration are often buying a second codebase that must be maintained forever.