One code on the fridge door: the holiday-let welcome page done properly
Guest questions cluster at three moments, and the page should be organised the same way. On arrival: how to get in, where to park, the wifi. In the middle of the week: how the oven works, where the fuse box is, bin day, what to do if the trip switch goes. Before leaving: checkout time, keys, stripping beds or not. A page structured by moment answers the question a guest has at 9pm without the owner's phone being involved, which is the actual product: fewer messages, calmer guests, better reviews. Keep each answer two lines long; this page gets read on a phone, often with wet hands.
| Section | What belongs in it |
|---|---|
| Arrival | Door code or key safe location and code, parking, a photo of the entrance at night |
| Wifi | Network name and password, and the one restart trick that fixes it |
| The house | Heating and hot water, oven quirks, the fuse box, where spares live (lightbulbs, bin bags, the second key) |
| Outdoors | Bin day and which bins, recycling rules the council actually enforces, the BBQ, the gate latch |
| Local | The nearest shop and its Sunday hours, two places to eat, the beach access that is not obvious |
| Leaving | Checkout time, keys, what to strip, and the lock-up sequence |
OpenQR provides the code and the redirect, not the page
There is no hosted house-manual page here: the welcome page is yours, whether that is a page on your own site, a section of your booking listing, or a single shared document. What OpenQR contributes is the code on the wall and a destination you can change at any time without reprinting anything, which matters when the door code changes between guests or the boiler is replaced in February.
The fridge door earns its reputation: guests stand in front of it, it is at hand height, and it is the traditional home of exactly this information. An internal acrylic or laminated plate at 40 to 60mm scans comfortably from arm's length; the print size guide has the full working for other spots. Put one code on the fridge or hallway, and consider a second on the back of the front door facing outward for arrivals with arms full of cases. A single dynamic code per property keeps the story simple: scan anywhere in the house, land on the same page.
An owner or manager with several properties has the set-shaped problem in miniature: unit 3's boiler is not unit 5's, and the bin day differs across the road. One code per unit, each opening that unit's own page. The list is short enough to type, but the bulk generator still earns its use: one row per property, label and destination, generating the whole set named by property so the right acrylic plate goes in the right cottage. Free covers three dynamic codes; a real portfolio is Pro at £9 a month, which is less than one reprint of laminated cards across a portfolio, once.
The fixture outlasts the information, which is the whole arrangement: a plate screwed or strongly adhered to the fridge survives years of cleans, while the door code, the wifi password and the cleaner's phone number live on the page behind it and change as often as needed. Changing the door code between guests is good security; printing it on a laminate is the reason most let cards go stale. There is one deliberate exception worth keeping: a small printed wifi card handed to guests at check-in suits guests who never scan anything, and costs nothing to include in the welcome folder.
A dynamic code counts scans, and on a let that number answers one useful question: did guests find and use the guide. A property with forty guest-nights and four scans is telling you the fridge plate is not working, or the printed wifi card answered everything and the page is redundant, and both are worth knowing before the next season. It will never be a large number, because one party scans once and then has the page saved. No individual guest is identified: the analytics carry a date and a rough location at most, and nothing that links a scan to a booking.