NFC Restaurant Menus: Tap to See the Menu, No App Needed
A tap-to-see NFC restaurant menu is one passive tag storing a single web link — nothing more. Here's what happens on the customer's phone when they tap it, why both platforms need an extra tap before the page opens, and how to write and lock the tag with NFCore.
Quick answer
An NFC restaurant menu is a small passive tag on the table that stores exactly one thing: a web link. Tap a phone to it, and the phone reads that link and opens the menu page in the browser — no app to install, no account. Contactless dining leans mostly on QR codes today because a printed code costs almost nothing to deploy, worth naming honestly rather than declaring NFC the winner for menus, Wi-Fi, and business cards. What NFC brings is durability. The tag itself is a battery-free coil and memory chip, so it survives lamination and thousands of taps without fading — a real advantage on a surface touched hundreds of times a week.
Step-by-step
What goes on the tag
The tag doesn't hold your menu — it holds a pointer to it. NFC Forum's guidance for any "tap for information" deployment matches what restaurant table displays use: write a single NDEF URI record to a passive tag, then place it somewhere a phone can comfortably reach — a table tent, a coaster, or the corner of a placemat.
Writing the tag
Open NFCore, choose Write Tag, pick the URL/URI record type, and paste the link to your menu page. Tap the finished tag with an Android phone and an iPhone both before it goes anywhere near a real table. The two platforms don't behave quite the same way.
What happens when a customer taps
On Android, the tag dispatch system inspects the tag's payload and routes it to the highest-priority matching intent. URL tags have historically opened the browser immediately; Android 16 and 17 route the same tap through an "open link" notification first — a small added step, not a broken tag.
iPhone works a little differently. Background tag reading kicks in whenever the screen is on, no app running required. A notification appears; tapping it opens Safari to the menu page.
Common problems and fixes
"Nothing happened when I tapped." Start with the basics: screen on, NFC enabled. On iPhone, background tag reading only activates after the device has been unlocked once since its last reboot — a phone fresh out of Airplane Mode won't read a tag until that happens.
"It showed a notification instead of opening the page." Expected, not a fault. iPhones have required a notification tap since the first models that supported background reading, and current Android versions now do the same thing — a deliberate guard against a phone in someone's pocket silently opening a link.
"Tap doesn't work near the register." Background tag reading pauses during an active Apple Pay or Wallet session, or while a camera is open. Moving the tag a table-width from the payment terminal usually clears this up.
"We changed the menu but the tag feels stale." Don't touch the physical tag. If it points at a URL you control, editing that page updates every table at once. Reprinting tags should never be part of a routine price change.
Doing this on NFCore specifically
NFCore's Write Tag flow handles the process above: pick URL as the record type, paste your menu link, and tap to write. Once the link is confirmed working on a couple of test phones, lock the tag read-only so another NFC app can't overwrite it by accident. NFCore is available on the App Store and Google Play.
Frequently Asked Questions
Do customers need to download an app to see an NFC menu?
No. The phone reads the tag's stored link through its built-in tag-reading system — Android opens the browser (or shows a notification first on newer versions), iPhone shows a notification the customer taps to launch Safari. No app install is involved on either side.
What's actually stored on an NFC restaurant menu tag?
One small NDEF URI record pointing at your menu's web page — not the menu itself. The tag is a passive coil and chip with no battery; tapping it just hands the phone a URL.
Can I update prices or dishes without touching the physical tags?
Yes, as long as the tag points at a stable URL you control. Edit the page behind that URL and every table's tag reflects the change instantly.
Why did my phone show a notification instead of opening the menu immediately?
Both platforms now require an explicit tap before opening a link from a tag — iPhone since its first background-reading models, Android starting with 16 and 17. It's a deliberate anti-accidental-tap safeguard.
Is NFC or a QR code sticker better for a restaurant menu?
QR codes are cheaper since they're just printed ink, which is why they dominate adoption. NFC tags cost more per table but survive lamination and heavy handling indefinitely — worth it for a table tent touched hundreds of times a week.
Conclusion
The entire mechanism behind a tap-to-see NFC menu is one URL record on a passive tag. Both Android and iPhone route that tap to the browser without an app, just with a confirmation step neither used to require. Once the tag is written and tested, the only upkeep is keeping the page it points to current. Pair it with a Wi-Fi tag at the same table, and a single tap covers two of the most common things a customer asks a server for.