Most couples hear "NFC wedding invitation" and picture something plastic and a bit cold. The reality is the opposite: the card is the same heavy cotton stock with the same foiling your stationer would have produced anyway. The technology is a sheet of film inside it that nobody can see.
The short version
An NFC invitation is a printed card with a paper-thin chip laminated inside. A guest holds their phone to it and your event page opens — RSVP, directions, running order, dress code, registry and later a shared photo gallery. Every card also carries a discreet QR code and a short written address, so guests with any phone can get in. You can change the details on the page at any point after the invitations are posted, which is the feature couples end up valuing most.
What they actually are
Two things:
The card. Printed stationery, designed however you like. The NFC inlay sits between layers of board during production, which is why it does not show and does not create a bump.
The event page. A private web page at a short address, designed to match the invitation, holding everything about the day. This is where the real work happens.
The invitation posts and behaves exactly like a traditional invitation. Nothing about the etiquette changes. It simply also answers questions.
How the card is made
- The inlay — a chip and antenna on a film roughly the thickness of a sheet of paper.
- Lamination — the inlay is placed between two or more layers of board, which are bonded. On duplexed cotton stock this happens at the duplexing stage, so it is structurally invisible.
- Print and finish — letterpress, hot foil, blind deboss, edge painting, vellum wraps and wax seals all work normally. Only foil directly over the antenna area needs a small amount of planning.
- Encoding — each card is written with your event address and locked so it cannot be altered.
- Testing — every card is read before packing.
If you already have a stationer you love, we can supply encoded inlays to them rather than taking over the print. Most are happy to work this way once they have seen one.
What goes on the event page
The test for every item: has a guest ever asked you this, or will they?
Always
- RSVP — attending or not, number of guests, names.
- When and where — ceremony and reception, with one-tap directions for each.
- Running order — arrival, ceremony, drinks, dinner, speeches, dancing, carriages.
- Dress code — written in plain language with two or three reference images. This single section eliminates more messages than anything else.
Usually
- Meal choices and dietary notes, captured per guest in the format your caterer wants.
- Travel and parking — shuttles, taxi numbers, parking restrictions, hotel blocks with the booking code.
- Gift registry — on its own screen, where it reads as information rather than a request.
- Children — whether they are invited. Say it clearly and nobody has to ask awkwardly.
Worth considering
- Song requests — your DJ gets a list that is already in their format.
- A note to the couple — guests write lovely things at RSVP time that you would otherwise never read.
- Your story — a short how-we-met for the guests who only know one of you.
- Accessibility notes — step-free routes, seating, quiet spaces.
The RSVP problem, solved
Paper RSVP cards fail in predictable ways. They need stamps. They get lost. They arrive with illegible handwriting and no meal choice. Roughly a third of your guest list will need chasing by text anyway, which means you end up running two systems and reconciling them at eleven at night.
A tap-to-RSVP page replies the moment the guest reads the invitation, which is the moment they are most likely to act. The list maintains itself, it is legible, every field you need is mandatory, and you can filter and export it for the caterer, the planner and the venue without retyping anything.
Two practical notes. First, you can still include a paper reply card for the guests who would prefer one — the two lists merge. Second, keep the form short: attending, how many, meal choice, dietary notes, one optional message. Every extra field loses replies.
Guests who cannot tap
This is the first question every couple asks, and it deserves a straight answer rather than reassurance.
Some guests will have older phones. Some will have NFC turned off on Android. Some will simply not be comfortable holding a phone to a card. So the card never relies on tapping alone:
- A discreet QR code on the details card or the reverse.
- A short written address — something like amara-and-elliot.events — that anybody can type.
- A card that works perfectly as a printed invitation on its own, with the essentials on the board.
Our practical advice: put the date, time and venue in print, and treat the page as the place for everything beyond that. Then no guest is ever excluded from what matters.
Etiquette
A few conventions hold up well.
- Keep the formal wording on the card. The host line, the invitation line, the names, the date and the venue belong in print.
- Do not print the registry on the invitation. Put it on the page, a tap away, where it is available without being presented.
- Add a line explaining the tap. Something gentle on the details card — "Tap this card with your phone, or scan the code, for directions and to RSVP."
- Tell the people who will be asked. Parents and the wedding party will field questions. Walk them through it once.
- Send save-the-dates as normal. They can carry the same chip and the page can open as a holding page that fills in later.
Timeline and budget
Allow eight to twelve weeks before you want to post. That covers design of both card and page, a physical proof in your hands, print, encoding and one round of changes. Rushing the proof is the only genuinely risky shortcut.
On budget, think of it as two lines. The event page is a one-off project cost that does not change with guest count. The cards are priced per unit, like any stationery, with the NFC inlay adding a modest amount per card on top of your print and finishing. For a typical wedding the technology is a small fraction of what the stationery costs anyway — the paper, the foil and the postage dominate. Our pricing page gives indicative starting points.
On the day
The page keeps earning after the invitations have done their job:
- Timings in every pocket. No guest asks what time the speeches start.
- A pinned announcement for last-minute changes — a shuttle running late, the ceremony moving indoors.
- Place cards and table numbers can carry the same chip, opening the seating plan or the menu.
- The shared gallery opens. Guests upload from their phones all day, and you wake up to several hundred photographs from angles your photographer could never have covered.
Afterwards
The page becomes the thank-you: the gallery, a note from you both, and the professional photographs when they arrive. Hosting usually runs for a fixed period after the event and can be extended if you want to keep it. Guest data is yours, is not shared, and is deleted on request.
