QR codes for property: sales boards, lettings and holiday lets

One code per listing, not one code reprinted

The test that decides everything else is whether each code needs a different destination. A single agent selling one house can reuse the same design principles as any other sign. An agency cannot reuse the same code: every listing has its own address, its own photos, its own status, so every board needs its own code pointing at its own page. Thirty live listings is thirty codes, not one code printed thirty times.

• One per for-sale or to-let board, pointing at that property's listing page
• One per window card, so a browser outside opening hours reaches the right gallery
• One per brochure cover, linking to that property's virtual tour
• One per let unit, opening check-in instructions rather than a listing
• One per holiday-let unit, covering appliance manuals and the wifi password instead

Import the book instead of typing thirty destinations by hand

Most agencies already hold the source data: a portal export or a CRM listing feed with an address and a URL for every live property. The bulk generator takes that CSV directly, maps address to label and URL to destination, and shows you the mapping before it generates anything. That last part matters: pasting a portal export the wrong way round produces thirty labels that scan to the word “Address”, and you want to catch that on screen, not on a printed board.

Repoint the board the day it sells, not the day someone notices

A printed board stays up for weeks after the sale completes. Agreeing the sale doesn't take the sign down, conveyancing doesn't take the sign down, and a busy branch reprinting every board the day contracts exchange is not realistic. With a dynamic code, none of that matters: the physical board stays exactly where it is and the destination changes underneath it. A scan on Monday opens the live listing; the same scan on Tuesday opens “Sold, see similar properties” instead of a 404 or a listing that has quietly vanished from the portal. See the dynamic codes guide for how repointing works.

A number you can take to a vendor

Every scan is logged with a date and a rough location, and that turns into something an agent can actually say to a client: your board was scanned 40 times this week. No vendor has ever heard that sentence from an agency before, because until now nobody could produce it. It costs the agency nothing to say and it is a stronger reason to relist with the same branch next time than anything in the fee structure.

That is the most useful idea on this page, and it is worth being precise about what it proves and what it doesn't. A scan means someone stood in front of the board and pointed a phone at it: real, local, physical interest, which is a genuinely different signal from a portal click from a browser three counties away. It does not prove the scanner liked the property, could afford it, or is going to call. Sell it as footfall evidence, not as a lead count, and it holds up.

Sizing a board, a V-board and a window card

Size follows how far away the code will be read from, and property signage covers a wider range of distances than almost anything else on this site. A window card is read from the pavement, close to the glass. A V-board on a verge is read by someone walking past on the pavement too, but often from further back to take in the whole board. A large estate-agency V-board on a busy road is sometimes read from a stopped or slow-moving car, which is a different job again: the code needs to be legible at a glance from several metres, not studied.

Those figures follow the 10:1 rule: the code should be at least a tenth of the distance it needs to read from. The full working, including error correction and printing at an exact millimetre size, is in the print size guide. Get the V-board wrong and the effect is invisible until someone tells you the sign never worked from the road, which is exactly the scan count this page just told you to start checking.

Lettings and holiday lets: codes at the unit level

A letting agent or a holiday-let owner has the same set-shaped problem, one level down. Instead of one code per listing, it's one code per unit, and instead of pointing at a property page, it points at whatever a tenant or guest needs on arrival: check-in instructions, the appliance manuals for a kitchen full of things a guest has never used before, and the wifi. A wifi QR code handles the last of those on its own, but for a holiday let the more useful move is one dynamic code per unit that opens a short welcome page covering all three, so a guest scans once on arrival rather than hunting for a laminated card.

This is where the set-shaped argument is clearest. A holiday-let owner with six units needs six different destinations, because unit 3's boiler instructions are not unit 5's, and the bin day is different on the other side of the building. Bulk-generating six codes from a short list of unit names takes the same shape as bulk-generating thirty listing codes: paste the list, check the mapping, print.