Scanning a VIN from a photo
Customers send photos, not typed VINs. Zeno reads a VIN from any of them:- the VIN plate in the windshield corner
- the door-jamb sticker
- a registration card
- an insurance ID card
Why a scan gets rejected
A VIN that looks right is the expensive failure in a glass shop: it reads as authoritative, nobody re-checks it, and the wrong glass ships. So a scanned VIN has to prove itself before Zeno will put it in the field. Three checks, widening:- The check digit. Free and instant. It catches almost every misread.
- A decoder round-trip. This catches the character collisions the arithmetic structurally can’t see —
Jagainst1,Sagainst2. When the decoder can pinpoint the bad character, the rejection carries a suggested correction. - Agreement with the document. The year, make, and model printed on the page are read far more reliably than the VIN itself. If the VIN decodes to a 2019 Honda and the card says 2024 Jeep, something is wrong.
J into a 1 that passed every check — the two characters share a check-digit value, so nothing downstream could catch it.
You’ll see four outcomes:
A decoder outage doesn’t become a VIN outage — the read degrades to unverified on the strength of the check digit rather than blocking your work.
When the photo shows a plate
Half the photos a front desk gets never show a VIN — a rear-end damage shot, a claim photo, a plate close-up. The plate is a perfectly good handle. Enter the plate and its state. Zeno tries GlassBiller first, since that’s already authenticated and costs nothing, and falls back to AutoBolt, which also returns year, make, and model with the VIN. The VIN that comes back is still only a claim, so it goes through the same three checks a scanned one does. A plate service can hand back a VIN that fails its own check digit, and decoding that lands the wrong glass just as surely as a misread photo.When you don’t need a VIN at all
Plenty of vehicles take the same glass across the whole model run. Walk year → make → model → style instead and skip the VIN entirely. It resolves to the same vehicle record the VIN would have. Reach for the VIN when the glass varies within a model — a windshield with a rain sensor, a heated wiper park, an ADAS camera bracket — because that’s where the trim-level detail decides which part fits. If you already have the part in hand, the know the part number? search takes a bare NAGS number straight to the vendor grid and skips identification altogether.From vehicle to price and availability
Once the vehicle is identified:- Pick the shop. GLAXIS accounts and warehouses are per-shop, so pricing and availability follow the location.
- Pick the glass position and part. No need to re-walk the cascade the VIN already answered.
- Read the pricing and availability. NAGS list and OEM pricing, plus a live three-vendor GLAXIS grid.
- Add to a vendor cart. Carts are reviewed and ordered from the Carts tab.
When to use AutoBolt instead
The AutoBolt tab is a different question. NAGS identification answers “which vehicle is this, and what glass does it take.” AutoBolt decodes a VIN or plate into glass part numbers and the ADAS calibrations the windshield requires. Go there when:- You need to know whether a windshield triggers an ADAS calibration before you quote it. The requirement is called out on the result.
- NAGS identification is ambiguous and you want a second read on the part number.
- A repeat decode is free. Zeno stores every decode and serves the same VIN from its own record without calling AutoBolt again.
- The history is Zeno’s. AutoBolt has no history of its own, so every decode your shop has run is listed under the tab — searchable later.