Loyalty without Apple Wallet: do you even need it?

Apple Wallet passes have an obvious appeal. They sit next to boarding passes and bank cards, they can pop up on the lock screen, and they look like something a serious business would have. It is easy to assume a loyalty scheme without one is second rate.

It is worth taking that assumption apart, because a wallet pass costs more than it looks like it should, and buys less than most shops expect.

What a wallet pass actually is

A pass is a signed bundle of files. To create one you need an Apple Developer account, a Pass Type ID, and a signing certificate that has to be renewed. To update a pass after it has been issued, you need a web service Apple can call, and push certificates to notify devices. Google Wallet is a separate system with its own account, its own API and its own approval step.

None of that is impossible. It is just an ongoing engineering commitment, and it is why wallet-pass loyalty products tend to sit at a higher price point than link-based ones.

The three real advantages

• Lock-screen presence. A pass can surface when someone is near your shop. This is genuinely good, and it is the one thing a web link cannot match.
• It survives everything. No browser history to clear, no tab to lose. It sits in the wallet until removed.
• It feels official. There is a perception benefit, particularly with older customers who already use the wallet for boarding passes.

The costs nobody mentions up front

The interesting problems with wallet passes are not technical, they are operational.

Adding the pass is still a step

The customer still has to scan something, still has to land on a page, and then has to tap "Add to Apple Wallet" and confirm. It is a shorter journey than an app store download, but it is longer than "here is your card". And on Android the flow is different enough that staff cannot give one set of instructions.

Updating stamps is asynchronous

When you stamp a wallet pass, the update goes through Apple's push service. Usually that is quick. Sometimes it is not, and the customer is standing at the counter looking at a card that still says 6 while your staff member insists it says 7. Web cards do not have this failure mode because the page simply reloads.

Two platforms, two systems, one support burden

Every quirk has to be handled twice, and your staff need to know both. For a shop with four part-time staff, that is a real cost.

When a wallet pass is worth it

There are cases where it clearly pays for itself:

• You are a chain with dozens of sites and a marketing team, and lock-screen proximity is a channel you will actually use.
• Your average transaction is large enough that a small lift in repeat visits covers a much higher software cost.
• You already have an app and the wallet pass is a companion to it, not the whole scheme.

If you are a single shop, or two, the honest answer is that a wallet pass is a nice-to-have that will not move your numbers as much as getting more people signed up in the first place would.

What to do instead

A web-based card gets most of the way there for a fraction of the complexity:

1. Make it installable to the home screen, so the customers who want an icon get one.
2. Make it work offline, so it opens in a dead spot.
3. Email the link on sign-up, so it is recoverable from an inbox forever.
4. Brand it to the shop, so it does not feel like a generic third-party thing.

That is the approach we took with Regulars, and the trade has been comfortable: sign-up rates that a wallet pass flow cannot match, in exchange for giving up lock-screen proximity.

If lock-screen proximity is the single thing your business needs, buy the wallet product. If what you need is more customers on the list, buy the one with the shortest sign-up.