NFC Tap vs. QR Code: Which Should You Use?

"Which one should I use, NFC or QR?" is usually the wrong question, because it assumes you're picking a winner. You're not — you're picking where a stamp needs to happen, and the honest answer for most businesses is both, doing different jobs. NFC and QR are two separate ways of recording the same event (a customer visited, give them credit for it), and each one is built for a different physical situation.

Neither requires the customer to download anything. A modern phone reads NFC natively — no app, just tap and the browser opens on its own — and a QR code opens with the phone's own camera. The only "app" involved is the one the customer already has: their camera or their phone's NFC reader. That's worth saying up front because it's the part people assume is different between the two methods, and it isn't.

How each one actually works

An NFC tap card is a physical object: a small card, usually sitting on a wooden base at the counter, that a customer taps with their own phone. The tap triggers a native NFC read, which opens the loyalty card in the browser and records the stamp. It's tied to a specific station — the same card, in the same spot, every time — and a tap is logged as its own event type, separate from anything scanned. There's no camera involved and no code to line up in a viewfinder; the customer taps and the stamp is already recorded before they've put their phone away.

A QR code is the opposite kind of object: it's not a device, it's a print job. A merchant generates it and puts it wherever it needs to be — taped to the counter, printed on a poster, dropped into a bag. The customer opens their camera, points it at the code, and their card updates. Ruffus supports two distinct flavors of this: a static join code used for the general "scan to get your card" flow at the counter, and single-use codes generated in batches for situations where a fixed station doesn't reach — more on that below. Both feed the exact same stamp card and reward logic as an NFC tap. A stamp is a stamp; the system doesn't care which method collected it.

Where NFC earns its spot

NFC's advantage is entirely about the counter. Once the card is sitting there, collecting a stamp is about as close to zero-friction as this gets — tap, done, no camera to open and no code to hunt for in a cluttered field of view. For a business with one clear point where every visit passes through — a register, a till, a single spot by the door — that's the ideal case. A barbershop with one chair and a counter, a café with one till, a boutique with one wrap desk: the card lives in one place because the transaction always happens in that place too.

The tradeoff is that an NFC card is exactly that — one card, sitting in one spot. It can't follow the transaction anywhere else. If your business has more than one place a stamp might reasonably get collected — a second register, a takeout window, a delivery bag — the NFC card only covers the spot it's physically sitting in.

Where QR reaches further

QR's advantage is the mirror image: it's not tied to a location, because it's not a physical device at all — it's ink. A merchant can self-print as many QR codes as they need and put them anywhere a customer might see one: a poster on the wall, a table tent, a mailer, a receipt. That reach is exactly what NFC structurally can't do, since a tap card only exists in the one place it's mounted.

The single-use batch codes matter most for orders that never pass a counter. A restaurant running takeout or delivery can print a batch of single-use codes and drop one in every bag, so a customer who never stood at the till still gets credit for the visit — which is the same gap covered in more depth for DoorDash and Grubhub orders and for Uber Eats customers, where there's no counter interaction to tap an NFC card against at all. Because each code in the batch is single-use, one bag can't be scanned twice to farm extra stamps, and a lost or forwarded code doesn't leave a standing hole a customer could exploit.

A comparison, briefly

• NFC tap — needs a physical card at a fixed spot; near-zero friction once it's there; can't move to a second location or leave the counter.
• QR (static join code) — printed once, sits at the counter for onboarding; works as a day-one fallback while NFC cards are in transit.
• QR (single-use batch codes) — printed in bulk, one per code; goes anywhere print can go — bags, posters, mailers — and can't be reused once redeemed.

Running both

Most setups that work well don't pick one and stop. NFC handles the default in-person tap — it's the fastest interaction once a customer is standing at the counter, and it's what a POS-free setup is usually built around in the first place. QR fills in everywhere NFC structurally can't reach: a new card that hasn't shipped yet, a takeout bag, a poster by the door for people who walk past without stopping. Neither is a workaround for the other — they cover different physical situations, and a business that only has one of them has a gap the other one exists to close.

The short version

NFC is a physical object that lives in one spot and makes the in-person tap nearly instant. QR is print, not hardware, so it goes wherever a customer might be — a bag, a wall, a mailer — but takes an extra step of opening the camera. Both record the same stamp, on the same card, with no app for the customer to install either way. The practical answer for most counters is to run NFC as the primary tap and let QR cover the reach it can't.