Comparisons

Do You Need a POS With Loyalty Built In?

An honest answer to whether your cafe loyalty program should live inside your POS or beside it. When POS-native wins, when standalone wins, what integration really costs, and the question that decides it for most cafes.

Oscar·Co-founder, Back Again·
Do You Need a POS With Loyalty Built In?

If you have gone looking for a cafe loyalty program, you have probably hit the same fork we hear about constantly. Your POS provider has a loyalty add-on, or a rep has told you their system does loyalty too, and now you are wondering whether to just use that instead of another piece of software.

It is a reasonable question and the honest answer is "it depends", but not in the useless way. It depends on one specific thing, and once you know what that thing is the decision takes about a minute.

We are the team behind Back Again, which deliberately does not integrate with your POS, so read this knowing where we sit. We have tried to be straight about where the other approach genuinely wins.

Two different things get called "loyalty in your POS"

Worth separating, because they behave very differently.

Native loyalty is where your POS company sells loyalty as its own product. Square Loyalty is the clearest example. Points accrue at checkout, it is part of the same account, and the setup really is a couple of clicks. Loyverse works the same way, bundled with their free POS.

Integrated loyalty is a separate loyalty product that connects to your POS through an integration. This is where the marketing gets slippery. "Integrates with Lightspeed" can mean anything from a genuinely live two-way sync to a partner listing that is coming soon. If a vendor claims an integration, ask them which version of the POS, whether it is live today, and for one cafe on that combination you can call.

The rest of this post is really about native loyalty, since that is the actual fork most owners face.

When POS-native is the right call

Three situations, and they are real:

You are already on Square and staying. If your till, your online orders and your invoices all run through Square, adding their loyalty is the path of least resistance and points flow through checkout automatically. Nobody has to remember anything.

You want points tied to spend, not visits. POS-native loyalty knows what the customer bought and what they paid. That lets you do "one point per dollar" or "double points on food", which a system sitting outside the till simply cannot see. If your loyalty logic depends on basket value, the POS is the right home for it.

You have one location and no plans to change systems. The per-location pricing that makes POS loyalty expensive for a group is irrelevant to a single site, and the lock-in only bites if you leave.

If all three describe you, use your POS loyalty. Genuinely. Turn it on this afternoon and skip the rest of this.

When standalone is the right call

You are not certain about your POS. More on this below, because it is the one that decides it for most cafes.

You have more than one site. Square Loyalty is priced per location, from $49 a month per site at the entry tier and rising with loyalty visits, per their Australian pricing. Three cafes is $147 a month before a single customer engages. Standalone tools are generally flat.

You want the marketing, not just the stamps. This is the part owners underestimate. A stamp card records visits. What actually brings people back is emailing a regular who has gone quiet, or sending a birthday offer. Some POS loyalty products do this, many do not, and if yours does not you end up paying for two tools anyway. We wrote about the two emails worth sending separately.

You do not want a project. POS-integrated anything means account access, configuration, a test transaction, and usually somebody from support. Standalone loyalty means putting a sign on the counter.

The question that actually decides it

Here it is: how long do you expect to stay on your current POS?

Cafes change POS more often than they expect to. The system gets bought by someone else and the pricing changes. Your rates go up. You outgrow it, or the reporting frustrates you, or a new site comes with a different system attached.

When loyalty lives inside your POS, changing POS ends your loyalty program. Not pauses. Ends. Your customers' points are records in a database you are leaving, and there is rarely a clean export that another platform can read. You are asking four hundred regulars to start again from zero, and a good chunk of them simply will not.

That is the asymmetry. If you pick POS-native and never switch, you saved yourself a small amount of setup. If you pick POS-native and switch in two years, you lose the customer list you spent two years building. Standalone loyalty is indifferent to what happens at the till, so a POS change is just a POS change.

What "no integration" actually costs you

Being fair about the trade, because standalone is not free of downsides.

You lose basket data. A system outside the till does not know what they ordered or what they spent. You get visit frequency, which for most cafe loyalty is what you were using anyway, but "spend $50, get a reward" is off the table.

It is a second place to look. Your sales are in one dashboard and your loyalty is in another. Minor, but real.

Staff have one extra thing to point at. Although in practice this is smaller than it sounds, because the customer does the work themselves. With a tap-based card there is nothing for the barista to enter, which is the opposite of POS loyalty, where somebody has to ask for a phone number during the morning rush.

That last one is worth sitting with. POS-native loyalty sounds frictionless because the points are automatic, but the enrolment is not. Someone still has to ask for a phone number or an email at the counter, and that ask happens at your busiest moment, by whoever is on shift. It is the most common reason POS loyalty programs sit at a few dozen members a year in.

A one-minute test

Answer three questions:

  1. Will you still be on this POS in three years? Not sure, or no, means standalone.
  2. Do your rewards depend on how much people spend, rather than how often they visit? Yes means POS-native.
  3. Do you have more than one location? Yes usually means standalone, on price alone.

Most independent cafes get "not sure", "no", and "one site". That combination points to standalone, which is why we built what we built.

Before you commit to either

Four things worth asking your POS provider, or any loyalty vendor:

  • Can I export my customer list and their point balances, in a format something else can read? If the answer is vague, treat the program as non-portable.
  • Is it priced per location? Fine for one site, expensive for three.
  • Does it email customers, or only record points? If it only records points, you will end up buying a second tool.
  • How does someone actually join at the counter? Ask them to walk you through it during a rush. This is where most programs quietly fail.

The bottom line

POS loyalty is not a worse product. It is a product with a dependency, and the dependency is the thing to think about rather than the feature list.

If you are settled on your POS, running one site, and want spend-based rewards, use theirs. If you are less than certain about your POS, or you have more than one site, or you want the emails that actually bring people back, keep loyalty separate so a change at the till never costs you your customer list.

Back Again is the standalone version of this: a tap-to-stamp card with no app for customers to download, no POS integration to configure, and win-back and birthday emails built in. Free until you have 50 customers, then $39 a month AUD flat, whatever number of sites you run. See how it works or the pricing.

If you would rather compare the field, our best loyalty system for cafes roundup covers Square Loyalty and Loyverse alongside the standalone options, with pricing for each. And if you are coming from cardboard rather than software, paper punch cards vs a digital loyalty app is the more useful comparison.

Read next