How to Move a Paper Loyalty Card to a Digital Program

The moment the old card meets the new system

A customer arrives at the bakery with a card bearing seven stamps. Your new digital program needs eight purchases for a free coffee. Do you simply give them seven digital stamps? Only if the qualifying purchase, reward and expiry rules have not changed. Otherwise, an automatic one-to-one transfer can make a promise you never intended, or take away a reward the customer fairly earned. That uncomfortable conversation happens at the counter, with other people waiting. It belongs in the migration plan, not in a later support ticket.

This guide is for a business moving an existing paper scheme online. If you are still choosing the channel, compare a wallet loyalty card with a dedicated app. If you need to design the underlying purchase and reward logic, see the loyalty app development guide. Here we focus on what happens to existing customers on the day the new system starts. The bakery examples are illustrative, not client results.

Inventory the promises already printed on the card

Put an actual paper card next to the proposed digital offer. Write down what counts as a purchase, how many marks earn a reward, which products qualify, whether there is an expiry date and which branches honour it. Photograph the front and back for the project team. Store managers sometimes know about exceptions that never made it into the original marketing copy: a stamp given for a large order, or a free item that cannot be combined with a discount.

Decide whether existing cards finish under the old rule or transfer into the new one. The easiest policy to explain is often to honour the old promise for cards already issued, while new customers enter the digital program. If you change the reward, choose a conversion that is no worse for the customer and say so plainly. Get the customer-facing wording reviewed by whoever owns your legal and consumer policy; a software team should not silently redefine an earned benefit.

Pick the smallest useful digital channel

You do not need a new app just to record visits. A till-connected loyalty platform, a web account or a Wallet pass may be enough. An app starts to make sense when the customer also orders, books or manages a recurring service. The pass or app is only what the customer sees; the customer record and reward ledger must remain reliable behind it. Check which devices, tills and branches you actually serve before deciding.

The practical test is a busy checkout, not a pretty mockup. Can a cashier find the right account without asking the customer to recite personal details aloud? Can they see that the transfer already happened? What happens when the scanner is offline? A program that works only when the manager is present will not survive the first weekend rush.

Transfer a card without counting it twice

Choose one verification procedure before opening the program to customers. For example, the cashier checks the physical marks, enters the count, and records a card reference or a photo where your privacy policy permits. A supervisor handles damaged or ambiguous cards. Once transferred, the paper card is stamped "converted," collected, or otherwise retired under a documented policy. Do not hand it back as a valid card if it can be presented again at another location.

Keep a record of who performed the transfer, when, from which branch and how many marks were credited. Treat a second attempt as a review case, not as another automatic award. In a digital ledger, the underlying operation should have its own stable reference; the same operation submitted twice must not double the balance. Square's documentation on loyalty-point adjustments is a useful technical illustration of recording earned and manually adjusted points. It describes Square's product, not a universal policy for every loyalty platform.

Suppose a customer brings seven of eight old stamps and then buys two coffees. The transfer gives seven, the qualifying purchase gives one, and the reward is available once. The second coffee should not generate an extra stamp unless the old rule says it does. If the purchase is refunded, reverse the stamp earned on that purchase; do not wipe out the seven transferred marks. Walk through this example with the cashier before you write code.

Tell customers what will happen, and when

There are two workable transition patterns. You can convert cards whenever people next visit, or offer a clearly announced trade-in period. Stamp Me's migration guide describes both approaches from the perspective of its own service. That makes it a useful example, not evidence that one policy suits every business. A fixed end date may speed up adoption but can upset infrequent visitors; an indefinite overlap is kinder at first but demands longer fraud controls and staff training.

At minimum, the sign by the till and the message on the website should answer four questions: Will my existing stamps count? Do I need a phone? When does the paper card stop working? Who fixes a missing reward? Tell customers before their next purchase if you can. Keep the explanation short and the detailed terms accessible. An early-switch bonus can help, but it should never be used to hide a worse conversion of rewards they have already earned.

Do not force an account on a person who cannot or does not want to use a smartphone unless that is genuinely necessary for the service. Consider a phone-number lookup, a printed receipt or an assisted option, with consent and privacy safeguards appropriate to your market. Separate permission to run a loyalty account from permission to send marketing. Moving to a digital channel is not a reason to assume that everyone agreed to promotional messages.

Rehearse the awkward cases with the team

Before rollout, give staff a one-page procedure with the normal transfer and the exceptions. One person brings two half-used cards; another has a photograph, not the card; a third has already redeemed the old reward. Decide which cases the cashier can resolve and which need a supervisor. Then practise on a test register. The customer should not watch employees negotiate policy for the first time in front of them.

Test purchases, partial refunds, cancelled orders, lost phones, duplicate scans and a temporary network outage. A customer balance should be explainable from its history: original paper transfer, eligible purchases, reversals and redeemed rewards. If staff can manually change points, require a reason and retain an audit trail. This is the same operational discipline discussed in our guide to loyalty-app mechanics, but migration adds the old paper record as a temporary source of truth.

For a small pilot, choose one branch and a short observation window. Record transfer attempts, errors, average time added at checkout and support contacts about missing progress. Review a few real cases with staff every day. A high signup count is not success if the queue slows down or existing customers lose their rewards. Fix the procedure first; only then expand to other branches.

Choose the next step after the pilot

If transfers work and customers mainly need a code at checkout, a digital card may be enough. Apple's loyalty-pass overview and Google's loyalty-card documentation show what their respective pass formats support. Availability and setup vary, so test your actual devices and scanners. If customers repeatedly ask to order or book, consider a website or app for those jobs rather than loading a simple card with unrelated features.

The development brief should contain the old and new rules, a handful of anonymised card examples, the exceptions staff encountered and the pilot numbers. That is far more useful than a request for "a modern loyalty app." You can prepare that brief for Appfyl or read about building a customer loyalty product. Neither route requires you to promise an app before you know which channel solves the problem.

Questions people ask