Sunday evening, seven o'clock, showroom dark. A couple walks the front row, stops at a three-year-old crossover, circles it twice, cups their hands against the glass to read the mileage off the sticker, and leaves. Nobody at the dealership knows they were there. Monday morning they are looking at someone else's listing.
That walk-the-lot-after-hours visit is the single biggest thing a window sticker code is for. Everything else is secondary.
After hours is the main event
Salespeople naturally picture the code as a tool for the customer standing in front of them on a Tuesday afternoon. In practice that customer has a person to talk to and does not need a phone.
The visitor who needs the code is the one who came at 8 p.m. because that is when they are free, or on a Sunday when you are closed, or during a lunch break with no intention of talking to anybody yet. Those visits happen constantly and they are almost entirely invisible to you. A code turns some fraction of them into a page view you can count and a test-drive request you can act on.
Which means the code has to work with nobody there to help. No "ask us for details", no page requiring an account, no form that lands in an inbox checked only on weekdays. The retail rules apply with the staff removed.
One code per vehicle, tied to the VIN
The shortcut is a single lot-wide code pointing at your inventory page. Do not take it.
A person standing at a specific car wants that car. Handing them a search page with sixty units means identifying the one in front of them by trim and color, and half of them will not bother. Worse, you lose the only information the scan was giving you: which unit generated the interest.
Per-VIN codes mean:
- The scan lands on that unit's page with no navigation
- Scan counts attach to individual cars, so you can see which units pull attention and which sit ignored
- A car scanned twelve times with no enquiry is telling you something about the price or the photos
- Retiring one code affects nothing else on the lot
Generating a code per unit sounds like a data-entry job until you do it as a batch. Export the VIN list and detail-page addresses from your inventory system, run them through a batch generator, and get the set back named by VIN so printing and filing are unambiguous.
Make every one of them dynamic. That matters more on a lot than almost anywhere else, for reasons the last section covers.
Reading through glass, in daylight
A window sticker code faces the hardest optical conditions of anything you will print. Behind glass, often at an angle, frequently in direct sun, sometimes with a reflection of the sky sitting across it.
What survives:
- Size it for the real distance. People scan from where they are standing, not from six inches away, and a low window means holding the phone at arm's length. Work from the distance-to-size relationship and then go one step larger, because the glass costs you.
- Matte stock, never gloss, never inside a shiny sleeve. Gloss plus sun equals a white rectangle.
- Hard contrast, dark on light. Silver, gray, or a tinted sticker background looks premium and scans badly. The contrast rules stop being optional behind glass.
- Print quality high enough that the smallest squares stay square. A code from a tired office laser loses edge definition, and that loss shows up exactly when the light is bad, so the resolution guidance is worth following for a run this size.
- Position it low in the side window rather than on the windshield, where sun sits most of the day and where a person has to lean across the hood.
- Keep clear white space around the pattern. A code crowded by price text is a code that fails at an angle.
Test on the lot, not at a desk. Take a printed sample out at 2 p.m. on a clear day, put it in a car window, and scan it from where a customer would actually stand. Then do it again at dusk.
The page has about three seconds
Somebody in a parking lot on cellular data, possibly with one bar, will not wait for a heavy page. What has to be there fast:
- Photos, properly compressed, with the gallery loading after the first image rather than all at once
- Price, mileage, trim, year, VIN
- Vehicle history summary
- A finance calculator that works without a login
- A test-drive form taking a name, a phone number, and two time options
What to cut: autoplay video, chat widgets loading ahead of content, a 360 spin viewer as the first thing on the page, and anything that throws a modal over the photos. All of that works fine on a desk at home. On a lot it becomes a blank screen and a lost visit.
The booking form should say what happens next and when. "We will call you tomorrow before noon" is worth more than a submit button that produces silence across a weekend.
Retire the code the hour the car sells
This is where per-VIN codes earn the dynamic setup. A sold car's code points at a page that will soon be dead, and a scan landing on a 404 in a parking lot is the worst outcome in the whole system. The visitor concludes your inventory is stale and walks.
Build it into the delivery checklist:
- The sticker comes out of the window as the plates go on
- The code's destination is repointed before the car leaves the lot, to similar units in stock rather than to the homepage
- The code is marked retired in your records so the VIN is never reused by mistake
Repointing a sold unit to a similar-vehicles view keeps value in every sticker still circulating in a photo, a forwarded listing, or a screenshot on somebody's phone. People do scan codes off pictures.
Run a monthly sweep of the rows: walk the lot, scan every sticker with a phone, note anything that fails or lands wrong. It takes half an hour on a small lot and it catches the stickers that faded, peeled, or outlived their car.
Start with the fifteen units nearest the road. Print those stickers, get them in the side windows this week, and check the scan counts after two weekends against how many of those cars had somebody walk past them.
