Wedding RSVP QR Codes: Wording and Timing

Why the reply card is going away

A stamped reply card costs postage twice, arrives over six weeks in an order nobody can track, and still leaves you phoning the four people who never sent it back. A QR code on the invitation sends guests straight to a form, and the answers land in one list with a timestamp.

The technical setup is genuinely quick, and the wedding RSVP QR code page has the generator on it. This post is about the parts that decide whether it works: what you write next to the code, when you print it, and what you do when something changes.

Print the invitations before the form is final, and use a dynamic code

This is the single most common mistake, and it is expensive. Invitations are ordered months ahead. Between ordering and posting, plenty of couples switch from a Google Form to a wedding website, move the venue, or discover a typo in the form URL. A static code encodes that URL permanently, so a change means reprinting a hundred invitations.

A dynamic code encodes a link you own and can re-point at any time. Same printed square, new destination, no reprint. It also counts scans, which is how you know whether the code is being used at all before the replies start arriving.

What to write next to the code

Guests scan when the instruction is specific and the deadline is visible. Compare:

• Weak: "RSVP" with a bare code underneath.
• Better: "Scan to RSVP by 12 June" with the code below it.
• Best: "Scan to RSVP by 12 June, or reply to hello@example.com" - the code plus a human fallback.

The fallback is not optional. Some of your guests do not have a smartphone, and older phone cameras will not open a code without an app. Printing an email address or a short typed URL under the code costs one line and removes the only real objection to the whole approach.

Placement and size on the card

Put the code on the details card or the reply card, not on the main invitation. The main invitation is the keepsake and a black square in the corner of it ages badly in photographs. On a details card, bottom-right with the deadline beside it reads naturally.

Size it at 2 x 2 cm minimum on paper held at reading distance. Print it in dark ink on the pale stock, never pale ink on dark. If your stationery is heavily textured or foiled, ask the printer for a proof and scan it, because texture scatters the contrast that a scanner needs. The print size guide covers the maths.

What the code should open

Whatever the destination, it has to work on a phone, in one hand, possibly in a hallway. A Google Form is perfectly good and free; see how to make a QR code for a Google Form. A wedding website RSVP page is nicer if you already have one. What does not work is a PDF the guest has to pinch-zoom, or a form that demands an account before it accepts an answer.

Ask for the fewest fields you can live with: name, attending yes or no, meal choice, and one free-text line. Every extra field loses replies.

After the wedding, the code has a second life

If the code is dynamic, it does not become rubbish on the day. Re-point it at your photo gallery and the invitations sitting on guests' fridges quietly turn into a link to the album. That is the same trick as a wedding photo QR code, without printing anything new.

A short checklist before you order

• The code is dynamic, so the destination can still change.
• The deadline is printed next to it, not only inside the form.
• There is a non-QR fallback: an email address or a typed URL.
• The form has been opened on an actual phone, not just a laptop.
• You have scanned the printed proof, not the screen preview.