Top complaints about loyalty platforms

Loyalty platforms — Punchh, Yotpo and Paytronix most often in these interviews — draw complaints about programs that hit a ceiling, data and benefits that don't move across systems, support, changes that need a developer or the vendor, breakage members see, and reporting. Six complaints, which platform draws which, and which ones put the contract in play.

Based on verified interviews with the retention and ecommerce leaders who run loyalty programs, at DTC and enterprise brands. Buyers are anonymized before publication; vendor names and views are reported as given. No vendor paid to appear or could edit this page.

Ask buyers what frustrates them about their loyalty platform and the most common answer is that the program has hit a ceiling: offers, tiers, segments or point rules the platform cannot run. Close behind is loyalty data and benefits that don't move smoothly across systems — points that don't work in stores, loyalty that doesn't reach the email platform or the app, lists exported by hand — sometimes because of the loyalty product, sometimes because of the point of sale or other systems around it. Then come uneven support, changes that need a developer or a ticket to the vendor, outages and errors that reach members, and reporting that is hard to trust or use. The ceiling is the complaint most often behind a decision to look at alternatives, though many of those buyers have not switched; support and reporting rarely move anyone on their own. Most of the evidence comes from Punchh, Yotpo and Paytronix users, so restaurant brands are heavily represented; Shopify-focused tools such as LoyaltyLion, Smile.io and Rivo draw too few complaints here to rank. For the ratings and the pre-purchase view, see what loyalty buyers wish they'd known.

5.3/10
Punchh's buyer rating — the platform with the most complaints here, and one several of the same buyers call a strong, flexible core.
6/10
Paytronix's rating, rounded because too few buyers rate it for a decimal — its users raise the ceiling and data that doesn't connect across systems, but not reporting.
Ceiling
The most common complaint, and the one most often behind a look at alternatives: the program needs offers, tiers or segments the platform cannot run.
Which loyalty platform earns which complaint A qualitative map from the interview corpus. A filled dot marks a complaint commonly raised by a platform's own users; a hollow dot marks one raised less often; a dash marks one its users did not raise. Users of Punchh, Yotpo and Paytronix all commonly raise the ceiling, data and benefits that don't connect across systems, support, and breakage. Changes that need a developer or the vendor are commonly raised on Punchh and Paytronix and less often on Yotpo. Reporting is commonly raised on Punchh, less often on Yotpo, and not raised by Paytronix users. Punchh Yotpo Paytronix The program hits a ceiling Data and benefits don't connect Support and account management Changes need a developer or vendor Breakage members see Reporting hard to trust or use commonly raisedraised less oftennot raised
Where each platform's own users raise each complaint about its loyalty product — a qualitative read, not a score; a complaint counts as common when roughly a fifth or more of that platform's complaining users raise it. Most of the grid is filled, which is the finding: the same complaints follow buyers from platform to platform. Paytronix rests on few buyers, so its column moves with a single company. CrowdTwist, SessionM, LoyaltyLion and other platforms have too few complaining users here to chart.
This is the average buyer's picture. What does your stack need?A free, peer-powered checkup returns a shortlist for your stack and your next steps.
Start my checkup →

The six complaints — graded

Each complaint is classified by how buyers in these interviews typically respond: tolerating the issue, working around it, waiting for the vendor, or reconsidering the contract. These are observed responses, not fixed severity ratings; the same limitation may be manageable for one brand and unacceptable for another.

Complaint 01 Puts the contract in play

The program hits a ceiling

The most common complaint: the brand wants offers, tiers, segments or point rules the platform cannot run, or has simply grown past it. “We keep coming up against use cases that we just can't activate in CrowdTwist,” one buyer says. A restaurant brand on Paytronix puts it plainly — “I would say we have mostly outgrown the capabilities there” — and a Marigold user found that “they cannot be different expirations on points.” The program ceiling is one of the strongest triggers for reconsidering a loyalty platform. Roughly half of the buyers who raise this complaint have either completed a switch, are planning one or are evaluating alternatives. Those are different stages of a replacement decision, but together they show how unmet program requirements can put the contract in play.

Named for this: Punchh · Yotpo · Paytronix · CrowdTwist · SessionM · Marigold · Smile.io

Complaint 02 Mixed — in play when a larger project is already moving

Loyalty data and benefits don't move smoothly across systems

The complaint about connecting loyalty to stores, apps, marketing platforms and other customer systems. Buyers describe points that cannot easily be redeemed in-store, member data that requires manual exports and integrations that do not work as expected. Some limitations originate in the loyalty product; others involve the connected point-of-sale, ecommerce or marketing systems. “People couldn't easily use their points for in-store purchases,” says a former Yotpo user with its own stores; a SessionM user is “needing to export those lists and then upload from our marketing tools”; a Stamped user says of its loyalty program, “It only services the Direct-to-Consumer site.” For restaurant brands the edge is usually the point of sale: “the integration between Punchh and our point of sale vendor is just not great,” one says — and in the same breath that “most of that blame lays at the POS provider.” Many buyers tolerate these limitations until a larger point-of-sale, app or data project creates an opportunity to reconsider loyalty as well. In those cases, the broader replatform can influence the decision as much as the loyalty product's own shortcomings.

Named for this: Punchh · Yotpo · Paytronix · SessionM · Stamped · CrowdTwist

Complaint 03 Often tolerated

Support and account management

Turnover, slow answers, and a vendor that waits to be led. A Yotpo user says “every other month or every other quarter, we have a new CSM working with us.” A CrowdTwist user says “we hop on the calls and then we have to lead everything, they never present anything new,” and a restaurant group says of Punchh, “Their support is really poor. That's probably my biggest complaint with them.” A LoyaltyLion user, asked about support, says “I think that's where LoyaltyLion is lacking.” Most mark the vendor down and stay; in these interviews support alone is the reason for very few moves.

Named for this: Yotpo · Punchh · Paytronix · CrowdTwist · LoyaltyLion · Annex Cloud · Marigold

Complaint 04 Often worked around — with agencies or the vendor's team

Every change needs a developer, a ticket or the vendor

The complaint about who can actually run the program. “We manually build out all our segments in Punchh,” one restaurant brand says. On Paytronix, “anytime we need to have a promotion set up, we have to tell them to do it.” A CrowdTwist user says “A lot of the customization within CrowdTwist requires development work that we just don't have the resources for.” Most buy their way around it with an agency, their own developers or the vendor's managed service; for a couple of restaurant brands, a more automated rival is the reason they moved or plan to.

Named for this: Punchh · Paytronix · CrowdTwist · LoyaltyLion · Yotpo

Complaint 05 Tolerated when fixed fast — the trigger when it isn't

Breakage members see

Outages, points that don't credit, errors that reach guests. A SessionM user says “they've often made updates on their end without telling us that cause things to break on our side.” A Kobie user describes “blips, what feels like pretty frequently, where we have some outages” — fixed quickly, and tolerated because of it. Where the vendor is slow to respond, this becomes the complaint that moves people: a Yotpo user whose program went down during a migration says that “would be the main reason why we would consider moving away from Yotpo,” and another brand left Yotpo after member points went uncredited and its account managers kept changing.

Named for this: Punchh · Yotpo · Paytronix · SessionM · Kobie · Marigold · Thanx

Complaint 06 Often handled internally

Reporting is hard to trust or use

Mostly a Punchh complaint in these interviews. Buyers describe different reporting frustrations: numbers that do not reconcile, dashboards that require too much manual work and limited flexibility in how data is analyzed. One buyer says to “look at even a canned report inside the Punchh platform, none of the numbers match”; another says “It's just a very manual dashboard, I should say.” Elsewhere the fix is the same: a CrowdTwist user's platform “drops a file into SFTP, we pick it up, push it into BQ, and we use that data.” Buyers export to their own warehouse, analytics or finance team, and live with it — even the one buyer whose stated reason to leave was reporting has not left yet. These accounts establish problems with reporting reliability and usability, rather than showing whether the loyalty program itself produces incremental sales or retention.

Named for this: Punchh · CrowdTwist · Yotpo · SessionM

Who leaves, and why? Completed moves in these interviews run in every direction — off Yotpo, Punchh, SessionM, CrowdTwist, Paytronix, LoyaltyLion, Smile.io and a custom build, sometimes onto a platform another buyer is leaving. One brand left Yotpo for LoyaltyLion while another left LoyaltyLion. Completed moves involve several overlapping reasons, including program limitations, unresolved member-facing problems and the need to fit loyalty into a changing technology stack. The program ceiling stands out as a recurring reason to evaluate alternatives, although many buyers raising it have not completed a switch. Planned moves also frequently coincide with larger point-of-sale, ordering-system or data projects. And more buyers are evaluating than moving: several say the work of migrating members, balances and integrations is what keeps them in place — “I don't think switching is an option right now,” says a SessionM user with a long list of complaints.

Want this checked against your own stack?

Start my checkup →

The stories behind the complaints

A franchised restaurant brand catches its loyalty vendor's errors before the vendor does. It describes outages “where our app may go down and someone made an error on their side and we lose hours worth of sales,” and says “We catch most of the errors on our side.” A feature in the contract turned out not to exist at launch: “And then when we launched, they said they couldn't do it,” which delayed the launch by months while Punchh built it. The brand still calls the vendor responsive, escalates rather than leaves, and asks Punchh to treat its several products from the same parent company as one account. Brand marketing and loyalty leader · franchised restaurant brand
A retailer running points across its stores and website praises its enterprise platform for exactly that: “That is a very strong selling point of CrowdTwist, which is definitely not something to take lightly.” Anything new needs developers the team does not have, so promotions fall back to the basics — “We rely on double point weekends, which is a very basic promotion within loyalty.” The verdict on value is blunt: “it feels very bare bones for the cost of it and being an enterprise tool.” The team talks about leaving but has not. CRM and loyalty leader · multi-channel retailer
A small specialty brand with its own stores moved off Yotpo loyalty a few years ago. The suite looked unified — “everything had a Yotpo logo slapped on it and was still completely separated in the back end” — and “People couldn't easily use their points for in-store purchases.” The fast replacement was worse: “there was a lot of drop-off in capabilities,” and the program went quiet. “Our loyalty program was functional on our website, but we stopped marketing it.” The brand has since replatformed again, and the buyer adds that Yotpo has probably come a long way since then. Digital director · specialty brand with stores

The counter-current: what keeps loyalty buyers in place

Specific strengths survive the complaints. The same buyer who calls Punchh's support poor says “Punchh is a really good core platform, very flexible,” and another adds “I will give Punchh credit, their IT teams have been pretty good to work with.” A Shopify brand calls LoyaltyLion “the standard of loyalty in the e-comm world,” and a Kobie user tolerates outages because its service team is excellent. Switching cost is a stated brake, not just inertia. And buyers often put part of the blame on their own side: a Punchh user says “I think our website and online ordering platform that we build has a lot of issues,” and another brand says “we shut down our loyalty program just because we weren't seeing a huge return” — a program-design problem, not a platform one. Before you conclude the platform is the problem, separate what the vendor controls — program logic, support, reliability — from what depends on your point of sale, your data and your program design.

What this means — whether you run one or you're buying one

If you already run a loyalty platform, most complaints are lived with or worked around: buyers export data to fill reporting gaps, hire agencies or lean on the vendor's team for changes, and escalate breakage. The ceiling is different, because a platform that cannot run the program you need is not something you can work around for long. If you're evaluating one, our recommendations — not practices buyers describe — are to write down the offers, tiers and point rules you expect to run in two years and make the vendor demonstrate them; to test how points and member data move to your point of sale, app, stores and email platform before signing; to ask who on your team can change a promotion without a ticket; and to agree how outages that reach members will be reported and fixed. For what triggers a move, see why brands switch loyalty platforms; for cost, what loyalty buyers actually pay; for rollout, why loyalty program launches slip.

Common questions

What are the most common complaints about loyalty platforms?

Among the loyalty-platform users in these interviews, six complaints recur: the program hits a ceiling on the offers, tiers and segments it can run; loyalty data and benefits don't move smoothly to the email platform, point of sale, app or stores; support and account management are uneven; changes need a developer, a ticket or the vendor; outages and errors reach members; and reporting is hard to trust or use. The ceiling is the most common, and the one most often behind a decision to look at alternatives.

What are the biggest complaints about Punchh?

Punchh users in these interviews, mostly restaurant brands, most often raise reporting that is hard to trust or use, integrations with the point of sale and messaging tools, segments and campaigns that take manual work, errors and outages that reach guests, support, and a slow roadmap. Several also call it a strong, flexible core loyalty platform.

What are the biggest complaints about Yotpo loyalty?

Yotpo loyalty users in these interviews most often raise support and account-manager turnover, loyalty that does not connect with their other tools or their stores, programs they have outgrown, and outages or points that did not credit members correctly. Reporting and self-service draw fewer complaints than on the restaurant platforms.

Why do brands switch loyalty platforms?

In these interviews, completed moves involve overlapping reasons: a program the platform cannot support, member-facing problems the vendor did not resolve, and the need to fit loyalty into a changing technology stack. The program ceiling is the most common reason to evaluate alternatives, though many buyers raising it have not switched, and support or reporting complaints alone rarely move anyone. Planned moves often coincide with a larger project such as a new point of sale or data warehouse, and several buyers say switching cost is what keeps them where they are.

Do complaints differ by loyalty platform?

Less than you might expect. In these interviews the same complaints, a ceiling, data that doesn't connect across systems, support and breakage, are raised by users of Punchh, Yotpo, Paytronix and smaller platforms alike. The differences are narrower: reporting is mostly a Punchh complaint, changes that need the vendor are raised on the restaurant platforms more than on Yotpo, and support is Yotpo users' most frequent complaint.

Get a checkup on your tech stack

A physical for your marketing stack, built from hundreds of verified buyer interviews: what matters most to you, a shortlist for your stack, and your next steps.

Start my checkup

Free · no password · your answers are anonymized before they inform research like this.

Want to come back to this?We'll email you a link to this page, so it's easy to find later or forward to your team.
Methodology. Alium conducts verified interviews with software buyers — the CRM, loyalty, lifecycle, digital and ecommerce leaders who select and run these platforms. This page aggregates what users of loyalty platforms say about the platforms they run, in interviews conducted through October 2026, focusing on the complaints they raise about a named platform in their own words and what they did about them. Only complaints about a loyalty product are counted; remarks about a vendor's email, reviews, referral or gift-card products are excluded, as are prospects, evaluations and second-hand reports about platforms a buyer never used. Most of the evidence comes from Punchh, Yotpo and Paytronix users, and restaurant brands are heavily represented. Complaints are counted by company and coded by theme; they are editorial codings of interview content, not survey scores. Ratings are averages of verified buyer ratings; the full table is on the loyalty lessons page. Buyer identities are verified at interview time and anonymized before publication; vendor names are reported as given. No vendor paid to appear or was able to edit this page.