The Forecourt Browsing Problem
A customer walks around a car dealership forecourt outside business hours — or when staff are busy with other customers. Without QR codes, they read the window sticker, note down the model, and leave without further engagement. With a QR, they access the full vehicle details, finance options, and a contact form in 10 seconds.
QR on Every Vehicle
Each vehicle on the forecourt should have a unique QR code linking to that vehicle's full listing page. The QR goes on:
- The windscreen sticker (alongside the price and key specs)
- The side window (if the windscreen is not accessible from outside)
- A door hanger or vehicle-specific card in the window
What the Vehicle Detail Page Should Include
- Full photo gallery (exterior: all angles; interior: dashboard, seats, boot)
- 360° interior view or video walkthrough
- Detailed specifications (engine, transmission, fuel type, mileage, service history)
- ULEZ and emission zone compliance status (increasingly important in UK urban areas)
- MOT history link (via GOV.UK vehicle enquiry service)
- Finance calculator (with current APR and term options)
- Vehicle history check status (HPI clear / finance outstanding indicator)
- "Book a test drive" button
- "Make an enquiry" button
Inventory Management with QR
As vehicles sell, their QR should redirect to a "This vehicle is now sold" page with three similar available alternatives. Never allow a high-scan QR to reach a dead page — buyers who scanned with intent should be redirected to a relevant alternative.
Use dynamic QR codes for all forecourt vehicles so you can update destinations without reprinting windscreen stickers.
After-Hours Lead Capture
Outside business hours, every vehicle QR page should have a prominent "Save this car" button (email or bookmark the listing), a "WhatsApp us about this car" button, and a "Book a test drive — pick your time" calendar link. After-hours browsing generates after-hours leads — capture them with a low-friction action.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
- The [blog](/blog) collects more guides on sizing, printing, security, and payments for QR codes.
