NFC Airbnb Welcome Tags: From Wi-Fi to Checkout in One Tap

A single NFC tag by the door or on the counter gets a guest onto Wi-Fi, into your house manual, and through checkout. No printed card, no typed password.

Quick answer

Write a Wi-Fi record and a link to your house manual onto one NTAG21x tag, lock it read-only, and stick it somewhere a guest will actually tap on arrival. Hotels already use the same tap-based pattern for in-room and lobby Wi-Fi onboarding, and it's quicker to set up than laminating a new card every time the password changes. Stack it against a QR code on the fridge and the tap wins — no camera app, no "allow access to photos" prompt.

Step-by-step

Choose a chip

For a short Wi-Fi record plus one link, NTAG213 has enough memory and costs the least. Want a longer, multi-language house manual, or a chain of records — check-in code, Wi-Fi, house rules — on one tag? Step up to NTAG216; it holds meaningfully more data than NTAG213. Our buying guide covers indoor stickers versus weatherproof tags, worth a look if this one's headed for a lockbox or gate that'll see rain.

Write the Wi-Fi record

Write the network name and password as a standard Wi-Fi NDEF record. Any NFC-capable phone reads it the same way — one tap joins the network. No typing, no texting a co-host to ask for the password. Android already exposes this exact mechanic for tying a Wi-Fi login to a tag instead of a printed sheet.

Chain the house manual and lock the tag

Add a second record — or a second tag — linking to your digital house manual or appliance instructions. Once it reads correctly on both an iPhone and an Android phone, lock the tag to read-only. That's permanent: a guest can't erase or overwrite the Wi-Fi record or the link mid-stay, the same way Type 2 tags can be set read-only after programming to stop accidental changes. See our breakdown of password protection versus permanent locking for the difference.

Common problems and fixes

A guest's iPhone won't read it. Confirm the Wi-Fi record is standard NDEF, not a proprietary format, and that the phone's recent enough — iPhone XS or later on a current iOS build reads a tapped tag by default.

A guest thinks it's an automation, not a Wi-Fi tag. It isn't. A passive NDEF tag works for any phone that taps it, no setup on the guest's end. That's different from an iOS Shortcuts NFC trigger, where the automation fires off the tag's unique ID and ignores everything else stored on it — and only runs on the one iPhone that originally scanned and named the tag.

The tag stopped working after a few months. Check it wasn't locked before a Wi-Fi password change — once locked, the record can't be rewritten. Also worth checking it isn't mounted on or near metal without a metal-rated tag; that alone can block the read.

You expect to change the Wi-Fi password soon. Don't lock a tag you'll need to rewrite. Leave it unlocked, or put anything likely to change on a second tag.

Doing this on NFCore specifically

We write the Wi-Fi record from a template: enter the network name and password once, and NFCore builds the NDEF record, then locks it with the same in-app action once you've confirmed it reads correctly. Handing a property to a co-host or cleaner? The Tag Inspector shows exactly what's stored on a tag, so nobody's guessing. Get NFCore on the App Store or Google Play and write your first welcome tag in a couple of minutes.

Frequently Asked Questions

What NFC chip should I use for an Airbnb welcome tag?

NTAG213 is enough for a short Wi-Fi record plus a link to your house manual. Step up to NTAG216 if you want to fit a longer multi-language manual or several linked records on one tag, since it holds significantly more data.

Can any guest read the tag, or does it need an app?

Any NFC-capable iPhone (XS or later) or Android phone can read a passive NDEF tag out of the box — no app, no pairing. That's different from an iOS Shortcuts NFC automation, which only runs on the one iPhone that scanned and named the tag.

Will guests be able to overwrite the Wi-Fi info by accident?

Not if you lock the tag read-only after writing it. Locking is permanent — the Wi-Fi record and any other NDEF data on the tag can't be changed afterward, though the tag's unique ID was never writable in the first place.

Should Wi-Fi, house rules, and checkout instructions be on one tag or several?

One tag can hold multiple chained NDEF records — Wi-Fi plus a link — but a second tag placed near the door for checkout steps is easier for guests to find at the right moment than scrolling through one long record.

Conclusion

One locked NFC tag — or two, if checkout steps get their own spot by the door — replaces the printed instruction sheet and speeds up every turnover. A guest taps in, gets online, and finds the house manual without texting you first. Once it works for one property, the same template scales to every unit in a portfolio.