QR Codes for Wedding Invitations
RSVP before the day, the album after it, from the invitation already in the post.
Nora and Thomas post ninety invitations in June for the fifteenth of October. The same code is on the save-the-date and the table plan, and the album will not exist until November.
The rule engine
What the scanner gets
The invitation, counting down to the ceremony, with the RSVP form open. Every reply lands in the dashboard as a lead.
The rule reads one instant, in UTC, and compares the scan to it. It knows the date somebody put on the rule, not whether the ceremony happened. If the date moves, move the date. The album branch can point at a holding page until the photos arrive, and repointing it later costs nothing.
Get this wrong and a card in a drawer still asks for an RSVP a year after the wedding, and the album nobody could find was one edit away.
no subscription · pay per scan · nothing to cancel
The invitation is printed in June and answered in October
Ninety cards go into the post months before the day. Replies arrive by text, by email and through the mothers; after the day the same card is the only link most guests kept, and it still asks for an RSVP to a wedding that has happened. A wedding website fixes some of that at the price of a subscription for one weekend.
- RSVPs arrive by text, email and word of mouth, and somebody reconciles them by hand.
- The printed card cannot change once it is in the post.
- After the day the card still asks for an RSVP.
- A dedicated wedding site is a subscription for one weekend.
What Nora and Thomas set before the cards went out
One code on everything
The same code goes on the invitation, the save-the-date and the table plan, so every piece of print shares one destination you control.
RSVPs land in your dashboard
The invitation page carries a form. Each reply is a lead at 5 credits, and it exports at any time.
Set the instant once
Before it, the invitation and the RSVP. After it, the album. The switch is a moment on the rule, not something to remember on the day.
when at the ceremony · before, the RSVP · after, the albumPhotos land weeks later
When the album is ready, repoint the after-branch at it. A destination edit costs nothing.
What one card in the post can do
- Two phases from one card
whenThe invitation before the instant, the album after it, on the same printed code.
- RSVPs you can export
Replies collect on the page and export at any time; nothing is locked behind a plan.
- A second switch for the deadline
Rules compose: a second instant can close the RSVP before the day itself.
- The album as a real page
A gallery page the same code opens once the instant has passed.
- No subscription for one weekend
1 credit to create the code, 1 credit per scan, and nothing that renews.
- Credits outlast the engagement
Credits are valid 18 months, and any top-up rolls the whole balance forward.
Real previews
The pages an invitation opens
The invitation with its RSVP, the same shape for another celebration, and the album for after.
These are not screenshots. Each frame is the page itself, rendered by the same code that answers a scan.
Questions
What does the code open after the wedding?
Whatever you put on the after-branch of the date switch: the album, a thank-you page or the registry. Until the photos arrive it can point at a holding page, and repointing it later costs nothing.
Where do the RSVPs go?
Into your dashboard as leads, one per reply, at 5 credits each, and they export at any time.
Can the RSVP close before the day itself?
Yes. Add a second date switch at the deadline; before it the form is open, after it the page says the list has closed. Rules compose in order.
Do guests need an app to scan the invitation?
No. Any phone camera reads the code and opens the page in the browser.
What does an invitation code cost for a hundred guests?
1 credit to create the code, 1 credit per scan, 5 credits for the date switch, and 5 credits per RSVP submitted. There is no plan and nothing renews.