Owning your loyalty data matters more than your platform choice

The argument

Among the 217 schemes profiled, tier status is known for 214, and 112 run tiers. The split is not random across software, it is concentrated by industry. Airlines run tiers in 61 of 61 with known status, hotels in 18 of 18. Grocery runs tiers in 0 of 18, restaurants in 2 of 22. If the software choice were the main cause of programme behaviour, industry would not predict the presence of a status ladder this cleanly.

Member histories are created before any platform is selected. An operator cannot know a customer's level without stored transactions, and it cannot store transactions without owning the records. The act of collecting this information precedes the act of picking a vendor. No application creates the raw material; it only reads what already exists.

The platform is a tool. The asset is the member file. A status level is not a feature bought from a vendor; it is a rule applied to data that the operator controls. Moving from one system to another without the histories destroys the ladder logic, but moving with them preserves it. The tool can be swapped. The information cannot be rebuilt from a competitor's dashboard.

The vendor market confirms the asymmetry. Of the 87 vendors profiled, only 48 publish full or partial pricing. Where price sheets are hidden, evaluating alternatives is expensive and uncertain. The one thing a business can control before signing is the data itself: what gets captured, where it resides, and how it can depart. Ownership is a contract and data model decision, not a software feature.

The strongest counter-argument

Selecting software can decide whether possession is genuine or nominal. A restricted package might show only aggregated numbers, demand a fee for raw export, or keep files in a layout that is costly to move. Under those conditions, the vendor pick is the ownership pick, because an open package is the only route to practical control. This is not a weak objection: some suppliers deliberately make integration and transfer hard, and a business that signs up may find its histories locked. If the package choice is the sole practical lever for portability, then the platform decision matters first.

What would change our mind

If a scheme migrates between systems and loses access to its historical member files, yet after one year its level assignment, recognition rate, and redemption values match the pre-migration baseline, the claim is wrong. That outcome would show features, not possession, drive performance. Specifically, the member ladder would remain unchanged without the old files.

What follows if we are right

Write ownership and export rights into the platform contract before signing. Require raw access to member records, transaction history, and level logic on departure. Treat the system as replaceable plumbing and invest in your data model, not in vendor-specific features. If the supplier cannot guarantee export, change the terms or choose a different supplier. A business that controls its data can switch tools without losing the asset that drives loyalty.