Plan the Divorce Before the Wedding

In January, PAR Technology paid $27.5 million for Bridg, an identity-resolution company. Five years earlier, it paid roughly $500 million for Punchh.

Two acquisitions, one playbook: buy the engagement layer, then buy the data layer underneath it, and sell the combined stack. It is a good strategy for PAR. The question is what it means for you, sitting inside the suite that just got bought.

I mapped the three architectural paths for loyalty on Medium this month: buy the suite, build on an open core, or plug into partnership APIs. This post is about the question buyers ask last and should ask first. Not which vendor to pick, but what it costs to leave them.

Your vendor is someone's acquisition target

Loyalty tech is consolidating because the value moved into infrastructure. A Chicago startup called Benji raised $6.25 million to become, in its own words, the Plaid of loyalty programs: a universal API for loyalty partnerships. Lucra raised $20 million led by ARK Invest to sell competition-based loyalty as infrastructure. When the money moves into the layer you rent, expect the layer to change owners.

Every acquisition is roadmap risk for the customers inside. Features get merged. Interfaces change. Pricing gets "simplified," which is vendor language for raised. Punchh customers bought a standalone loyalty platform in 2021 and woke up inside the PAR Engagement suite. Some of them are happy. All of them had a roadmap decided for them.

Ask what happened to the last product they bought

There is a simple diligence question that cuts through every sales deck: what happened to the last company this vendor acquired? Then ask for the answer in writing.

You want specifics. Did the acquired product keep its own roadmap for two years or get folded in six months? Did pricing stay or get "harmonized"? Did the API contracts survive? A vendor with a clean record will answer directly. A vendor that squirms is telling you everything.

This is not cynicism. It is pattern recognition. PAR bought the engagement layer, then bought the data layer. That is the consolidation playbook, and it will run again with someone else's logo on it.

Four clauses that buy your freedom

Score every contract on reversibility before you score it on features. Four clauses matter more than the demo.

First, data export. Can you take members, balances, tier status, and full history out, in a usable format, on demand? If the answer involves a professional-services quote, you do not have data portability. You have a hostage situation with better branding.

Second, API standards. Are the interfaces documented and standard, or proprietary? Headless engines like Open Loyalty expose their mechanics through REST APIs with webhooks for real-time events. Talon.One ships a server that lets AI assistants query campaign data in plain language. The more standard the interface, the less rework a future migration needs.

Third, term and termination. What is the real contract length once auto-renewals and notice periods are counted? A three-year deal with a 90-day non-renewal notice is a three-year deal. Know which one you are signing.

Fourth, migration assistance. Will the outgoing vendor cooperate with the incoming one? Put it in the contract now. Nobody volunteers for this after the fact.

Migrations are normal. Budget like it.

Blaze Pizza moved more than five million rewards members onto Thanx. Cheba Hut moved from Punchh to Thanx and grew revenue capture 2.65x and active member engagement 2.7x afterward. Switching platforms is no longer an emergency. It is a lifecycle event.

A real migration has five workstreams, and the technology is only one of them. Member porting: every record moves, duplicates get merged, fraud-flagged accounts get reviewed. Balance and liability migration: points are a liability on someone's balance sheet, and finance signs off, not just marketing. POS and channel reintegration: the new platform has to read transactions everywhere the old one did, and for franchised brands with mixed estates this is the hardest part. Member communication: over-communicate or eat a week of angry app-store reviews. Measurement continuity: freeze the KPI definitions before the switch, not after, or you cannot prove the migration was worth it.

Budget for all five explicitly. Migration services are routinely underestimated because the platform demo never shows them.

Own the data, rent the engine

The most durable answer I have seen is the hybrid: buy the suite or the headless engine for the mechanics, plug a partnership API where coalition earn matters, and keep the member data in your own warehouse no matter what. No vendor holds you hostage if the data already lives with you.

One caution on the network bet. A partnership API with few partners is just another integration with better marketing. Benji's network already covers more than 50 million members across names like JetBlue's TrueBlue, Cook Unity, and 1-800-Flowers, and the company says integrations that took months now go live in days. Evaluate the network that exists, not the one in the pitch deck.

The cheapest contract is the most expensive to leave

Loyalty infrastructure in 2026 gives you real choices for the first time: managed suites, headless engines, open-source cores, partnership APIs. That freedom is only real if you can exercise it later.

So run the decision backwards. Before you ask what the platform does, ask what happens the day you want out. The vendors worth signing are the ones who answer that question well. The rest are selling you a wedding with no prenup, and you know how those end.