What's the difference between the build record and the window sticker?

The build record is the factory's as-built data for one VIN — the options, packages, color and trim codes, assembly plant, and build date, exactly as the order was placed. The window sticker is the printed page generated from that data: the same facts laid out as the document the car shipped with, options named and line-priced. The build record is the source; the sticker is the document rendered from it. Reading the build record at build.vin is free, no account; the printed, line-priced sticker is one door away at sticker.vin.

That is the whole distinction, and it matters more than it sounds. Most people never see a build record — they see the sticker, or a retelling of the sticker, and treat the two as the same thing. They are not. One is data; one is a page. Everything below is how they relate, where they diverge, and why the record is the thing you actually want when a claim is on the line.

The record is the order; the sticker is the printout

When a car is built, the factory places an order against a serial number: this engine, this transmission, these packages, this paint code, at this plant, on this date. That order — the as-built data — is the build record. It exists as structured fields: an engine code, an option code, a color code, a plant identifier, a build date. It is not written in prose and it is not designed to be read across a showroom.

The window sticker (the Monroney label, the page taped to the glass) is what a human reads. It takes the same order and renders it: base model, each optioned package spelled out in words, the paint by name, the destination charge, and the MSRP totaled at the bottom. The sticker is a presentation layer. Strip the presentation away and what remains is the build record.

So the relationship is one-directional. The record can exist without a printed sticker — plenty of VINs have build data and no surviving physical label. But a sticker cannot exist without the record behind it; there is nothing to print from otherwise. That is why sticker.vin regenerates the window sticker from the build record rather than the other way around. The data is upstream. The document is downstream.

Why you'd read the record instead of the sticker

If the sticker is the friendly version, why go to the raw data at all? Because a claim traces to the record, not to a retelling of it.

An ad, an auction sheet, and an appraisal can carry three different equipment lists for one car — each a retelling, none a citation. "Sport package." "Towing prepped." "Loaded." The build record is the factory's order for that serial number, section by section. Either "sport package" appears in the order or it doesn't. A claim that traces to the record is verified; a claim that doesn't is the seller's word — and the delta between them is a fact, not an argument. When you are pricing equipment, that is the difference between an options premium you can defend and one you paid on a story.

The record reads in structured sections:

section	what it holds
identity	year · make · model · trim · body style
build	assembly plant · build date · port of entry, where the record states them
colors	exterior color code · interior color code
powertrain	engine · transmission · drivetrain, as ordered
options & packages	as ordered — named and line-priced on the sticker

Every line posts with its value, its source, and its timestamp. Where the OEM record for a field is unavailable, the page says so — reported, not yet verified — rather than filling the gap with a guess. A blank is a stated result, not an invitation to assume.

Build vs the specs — a related seam

There is a third thing people fold in, and it is worth keeping straight. The build record is one car, as ordered. The factory specifications — dimensions, powertrain ratings, capacities, standard equipment — are the vehicle, as designed. Specs describe the model resolved to the trim the car actually is; the build record describes the individual order behind this VIN. If you want the tow rating for the configuration, that is a specs question at specs.vin. If you want to know which packages the factory actually put on this serial number, that is the build record. Two different questions, cleanly split.

And where the car and its record diverge — an option deleted, one added after the sale — that delta is not a build question either. The build record is day zero: the car as ordered. What changed afterward belongs to the history. The record states the origin; the history states everything since.

The cost, stated plainly

Reading the build record is $0, on every VIN, on every visit, with no account. It is a free face by design. The printed, line-priced window sticker posts its own fee at sticker.vin — a number stated or absent, never implied. This door owns exactly one job: the as-built record, read free and traced. It does not re-quote the sticker's price, and it does not sell the document. The record does the work; the printed page is a separate step, one door over, priced where it lives.

So: the build record is the data, and it is free to read. The window sticker is the document that data prints to, at sticker.vin. Same facts, two faces — one you trace a claim against, one you hand across the desk.