Get a build sheet for your Saab

If you’re buying, selling, owning, or restoring a Saab, the most dependable way to confirm how it originally left the factory is to rely on its build documentation. A build sheet functions as the vehicle’s official record of its original configuration, detailing factory trim and package content, paint and interior codes, major powertrain specifications, axle/gear information, and the production codes assigned during assembly.

Availability isn’t consistent across manufacturers, and Saab is no different. What can be retrieved depends on the model year and on the internal systems Saab (and, in later years, its corporate parentage) used when the vehicle was built. To eliminate the guesswork, we offer a Saab Build Sheet by VIN lookup tool. Enter the Vehicle Identification Number (VIN) and, when manufacturer data is available, you’ll receive the vehicle’s documented factory configuration. If a complimentary build sheet can’t be pulled, the tool automatically tries to retrieve a free Saab window sticker as a fallback. And if neither document is accessible, we can route the request through a vetted provider that reconstructs the build sheet or sticker from VIN-linked official data, giving you access to the most readily available vehicle documentation.

The FAQ below explains where Saab build information may come from, what each type of document can verify, and how to use them to validate a vehicle’s true factory specifications.

Saab Build Sheet FAQ

Core concepts and terminology

What is a Saab build sheet?

A build sheet is a factory production document tied to a single VIN (or chassis number on older cars) that describes how that exact vehicle was configured as it went down the assembly line—powertrain, paint/trim, and factory-installed options and equipment.

Why do people mean different things when they say “build sheet” for a Saab?

Because Saab’s U.S. era spans multiple record-keeping systems and corporate parents, people often use “build sheet” as shorthand for any factory configuration record, including:

a VIN decode + option list from an online tool
a “service parts / option” label on the car (common on later GM-based Saabs)
a dealer/service system “vehicle profile”
original sales paperwork or window sticker

Only some of those are true assembly build sheets in the factory sense.

Is a VIN decoder output the same thing as a build sheet?

Not automatically. A VIN decoder (including official tools) can reliably decode what’s encoded in the VIN (make, model line, year, plant, some drivetrain identifiers), but a real build sheet usually goes further into option/package content and internal production codes that are not all embedded in the VIN.

What info is typically on a Saab build sheet or “build-data” record?

Common fields you may see (varies by era/model):

VIN/chassis number, build date, assembly plant
engine/transmission identifiers
exterior paint code and interior trim code
option codes and package content
market/configuration identifiers (U.S. vs other markets)
production sequence/serial number

For GM-platform Saabs, the factory option label explicitly calls out VIN, paint info, and “production options and special equipment.”

What’s a “production card” and is that a build sheet?

In enthusiast terms, “production card” can mean a factory build/production record (or a paper sheet/tag used during assembly). Some Saab owners report finding factory sheets in the vehicle during interior/headliner work, but that’s not a consistent, standardized “you will find it here” situation for Saab the way it is for some classic American cars.

I heard “Saab build sheets don’t exist.” True?

Not really—what’s true is that availability is uneven:

Later cars often have retrievable digital configuration data (sometimes indirectly via service/parts systems or third-party databases).
Some models (notably GM-based Saabs) have an on-car option label that functions like a build/options manifest.
Many older Saabs in the U.S. won’t have an easy “order a certificate and get everything” pathway like some heritage brands do.

How to obtain Saab build information in the U.S.

What’s the most practical “start here” path for U.S. Saab owners?

Start with what you can verify from the car and the VIN, then escalate:

Read VIN from the car (not just paperwork) and confirm it’s valid.
Decode VIN basics using NHTSA’s VIN decoder for models with a 17-character VIN.
Pull Saab-specific VIN breakdown rules (by model/year) to interpret Saab-only characters.
Look for on-car option labels (especially 9-7X; sometimes other late cars).
Use reputable Saab parts/service systems (Orio WebEPC/WebWIS/TIS2WEB) or a Saab specialist who has access.

Who “owns” Saab service/parts infrastructure now?

Orio AB (Saab Automobile Parts) operates the Saab technical information systems site and positions itself as the exclusive supplier of original parts and technology required to service Saab cars.

What is Orio TIS2WEB / WebWIS / WebEPC, and why does it matter for build data?

Those are official workshop/diagnostic and parts catalog tools sold by subscription:

TIS2WEB: applications needed to diagnose/program Saab vehicles
WebWIS: official diagnostic measures + service/repair documentation
WebEPC: official electronic parts catalog

Even when they don’t hand you a neat “build sheet PDF,” these tools are often the best path to confirm a vehicle’s original configuration for parts and service purposes.

Can Orio sell me a build sheet?

Orio publicly markets workshop tools and subscriptions (diagnostics, WIS, EPC) rather than a consumer-facing “heritage build sheet” product. In practice, you’re usually using these systems (directly or via a Saab specialist) to reconstruct configuration info rather than ordering an official “build sheet certificate.”

Can I still ask a Saab dealer for build data?

Some independent Saab specialists and former dealers can access Saab tooling and databases depending on what they maintain. Don’t assume every shop can do it—ask specifically whether they can pull a vehicle “configuration / option list” from Saab systems (and for which years). Orio’s model is subscription-based access to workshop tools, which is why capability varies shop to shop.

Are there online tools that generate a “Saab build sheet by VIN”?

Yes, but treat them as database outputs, not gospel. For example, iSeeCars’ Vehicle Build Sheet Lookup lists Saab among makes where it may return a build sheet when available. Also, some Saab parts sellers run VIN-based configuration pages that show included equipment codes and descriptions for specific VINs (useful, but still a third-party presentation layer).

What do I need before I start requesting anything?

At minimum:

The VIN (17 characters for 1981+ cars; older may be chassis numbers)
Model/year and U.S.-market context (Saab VIN meanings change by era/model)
Photos of the VIN tag and any option labels (to avoid chasing a typo)

How do I find the VIN on the car (not paperwork)?

VIN placement varies by era, but commonly includes windshield plate, B‑pillar/door area labels, engine compartment stampings/labels, and interior stickers/plates depending on model/year.

What about pre‑1981 Saabs that don’t have 17-digit VINs?

Before 1981, VIN formats varied by manufacturer; many tools require a standardized 17-character VIN and will fail or get confused if you input older chassis numbers. For classic Saabs, you typically decode using model-specific chassis-number references rather than a universal VIN decoder.

Can I recover build info if the VIN tag or label is missing?

Sometimes you can reconstruct from:

title/registration + stamped body numbers (varies by model/year)
on-car option labels (if present)
parts/service system lookups once you’re confident you have the correct identifier

A missing vehicle label on a GM-based Saab can be problematic, and the owner’s manual explicitly warns not to remove these because they are helpful for ordering parts.

Is there anything Saab-specific that’s “U.S.-only” regarding build data?

Two big U.S.-market realities:

You’re often chasing documents because of U.S. resale/restoration norms (window stickers, originality verification).
For some models, Saab published U.S.-distribution service information that includes VIN breakdown rules for the U.S. market.

Saab build sheets across eras and models

Which U.S.-market Saabs are easiest to decode from the VIN alone?

Later cars with detailed published VIN breakdown rules are easiest:

1999–2011 Saab 9‑3 and 9‑5 have published VIN breakdown bulletins that map characters to a car line, body type, gearbox, engine, plant, etc.
2005–2008 Saab 9‑7X also has a clear VIN system breakdown.
2005–2006 Saab 9‑2X has Saab-issued VIN system sheets (Subaru-built WMI).

Why are classic U.S. Saabs harder (Sonett, 96/99, classic 900)?

They predate VIN standardization and often rely on chassis numbers plus separate option/trim documentation. You’ll generally decode via Saab-focused chassis references rather than a universal VIN tool.

What’s special about “non-traditional” U.S. Saabs like 9‑2X and 9‑7X?

They’re Saab-branded but built on other manufacturers’ platforms, and their identifiers/labels reflect that:

9‑2X uses a Fuji Heavy Industries/Subaru WMI (JF4) and Saab-specific line/trim coding.
9‑7X is U.S.-built and follows a GM-style VIN system and GM-style service/parts identification practices.

If you assume “all Saabs start with YS3,” you’ll decode these wrong.

Decoding a Saab build sheet or build-data record

What’s the fastest way to confirm whether my VIN is valid and decodable?

Use NHTSA’s VIN Decoder (vPIC). It accepts VINs (and even partial VINs) and will flag invalid attempts, including “Pre‑1981 Year Decode Attempt” scenarios.

How do I decode the model year from a 17-character Saab VIN?

For standardized 17-character VINs (1981+), the 10th character represents the model year. Before 1981, formats vary by manufacturer.

How do I decode U.S. 1999–2011 Saab 9‑3 and 9‑5 VIN characters?

Saab published a VIN breakdown for these cars that maps positions to car line, model series/restraint type, body type, gearbox, engine, model year, plant, and serial number. You can decode it character-by-character using that mapping rather than a generic “Saab VIN decoder” page.

Can you give me a concrete example of decoding a 2007 9‑3/9‑5 VIN (VIN anatomy?

Using Saab’s published 2006–2007 mapping for 9‑3 and 9‑5 VINs:

Pos. 1–3: YS3 = Saab Automobile AB, Sweden
Pos. 4: car line (F=9‑3, E=9‑5)
Pos. 5: market/equipment (D=2.0T/2.3T w/ airbags; H=Aero w/ airbags)
Pos. 6: body type (4=4‑door; 5=5‑door; 7=Convertible)
Pos. 7: gearbox (1=6‑speed automatic; 5=5‑speed manual; 6=6‑speed manual; 9=5‑speed automatic)
Pos. 8: engine (examples include U=2.8L turbo V6; Y=2.0L turbo high output; G=2.3L turbo high output)
Pos. 10: model year (7=2007)
Pos. 11: assembly plant (examples include Trollhättan, Graz for certain convertibles)

That gets you the “hard facts” encoded in the VIN; it still doesn’t enumerate every option package.

How do I decode a Saab 9‑7X VIN (2005–2008)?

Saab published a VIN system breakdown for the 9‑7X. Example elements include:

Pos. 1–3 WMI: 5S3 = U.S.-built Saab
Pos. 8 engine type (varies by year; includes inline-6 and V8 variants)
Pos. 11 assembly plant: 2 = Moraine, Ohio

Where do I get the 9‑7X “options list” if I need more than VIN basics?

The 9‑7X owner’s manual states there’s a Service Parts Identification Label inside the glove box, and it lists:

VIN
model designation
paint information
“production options and special equipment”

For GM-platform vehicles, that label is often the closest thing to an on-car build/options manifest.

How do I decode a Saab 9‑2X VIN (2005–2006)?

Saab published VIN system sheets for the 9‑2X:

WMI JF4 indicates Fuji Heavy Industries (Japan) / Saab passenger car context
line code identifies Saab 9‑2X
body type and engine/trim codes differ by year
transmission/plant coding is explicitly tied to Fuji Heavy Industries

What’s the difference between decoding the VIN and decoding the option codes?

VIN decoding: specific mapping of characters (what’s encoded in the VIN).
Option-code decoding: translating internal production/parts codes to equipment descriptions—often requires a code list, a parts/service system, or a vendor tool that already translates them.

What if my “build sheet” is just a list of numeric codes?

That’s common. Your job becomes translation:

If it’s a GM-style RPO/options label, you decode each code against an RPO code list.
If it’s a Saab equipment-code list, use Saab parts/service systems (WebEPC/WebWIS) or a reputable Saab vendor tool that maps code → description.

Can you provide a step-by-step guide to decoding a Saab build sheet or build-data printout?

Yes—use this sequence so you don’t “decode” nonsense:

Confirm the identifier type
- 17-character VIN (1981+) vs pre‑1981 chassis number
Validate the VIN from the car
- Read it from the vehicle (windshield plate / labels) and confirm it matches paperwork.
Decode the VIN using authoritative mapping
- For 1999–2011 9‑3/9‑5, use Saab’s published VIN breakdown.
- For 9‑7X, use Saab’s 9‑7X VIN system sheet.
- For 9‑2X, use Saab’s 9‑2X VIN system sheet.
Identify what “build sheet” you actually have
- GM-based option label (SPID/RPO-style) vs Saab equipment-code list vs third-party database output
Translate option codes
- If your source already includes descriptions next to codes, preserve both the code and description for documentation.
- If it’s code-only: translate via a trusted parts/service system (Orio WebEPC/WebWIS) or a vendor tool that maps Saab codes.
Cross-check with physical evidence
- Paint/trim and major equipment should match what’s on the car (and any factory labels). The 9‑7X manual is explicit that its label includes paint information and production options.
Save your decoded output
- Store as PDF + photos of VIN/labels so a future buyer (or you, later) can verify you didn’t transpose a character.

Can you show a fully worked decoding example?

Here’s an illustrative example that mirrors how real Saab build-data decoding works, without pretending we’re looking up a specific owner’s VIN.

Example A — VIN-level decode (2007 Saab 9‑3 Aero, U.S.-market pattern)

Suppose your VIN begins like: YS3 F H 4 6 Y … 7 1 xxxxxx Using Saab’s published 2007 VIN logic:

YS3 = Saab Automobile AB, Sweden
F (pos. 4) = 9‑3
H (pos. 5) = Aero market/equipment bucket (w/ airbags)
4 (pos. 6) = 4‑door
6 (pos. 7) = 6‑speed manual
Y (pos. 8) = 2.0L turbo high output engine code (per Saab’s mapping)
7 (pos. 10) = 2007
1 (pos. 11) = Trollhättan assembly plant for 9‑3 (per Saab mapping)

That tells you: 9‑3 Aero, 4‑door, 6MT, 2.0T HO, MY2007, Trollhättan, plus the serial sequence.

Example B — Option/equipment-code decode (what people call the “build sheet”)

Now imagine your build-data source lists equipment codes like the vendor-style format below (example structure shown in real VIN-based config pages):

309‑010 — Passenger seat maneuvering: manually maneuvered passenger seat
313‑010 — Seat ventilation: without seat ventilation
319‑020 — (code continues…)

If your source already gives the description next to the code, your “decoding” task is to:

Keep the code + description together (the code matters for parts).
Group by subsystem (seats/interior, audio, chassis, etc.).
Cross-check any “big ticket” items (engine, gearbox, body style) against the VIN decode.

If your sheet is code-only (no descriptions), you need a translation source—typically Saab parts/service systems (Orio WebEPC/WebWIS) or a Saab specialist/vendor tool that maps those codes.

Build sheet vs. window sticker (Monroney label)

What is the difference between a Saab build sheet and a Saab window sticker?

They serve different purposes:

Build sheet: factory production tool/record with technical configuration and internal codes (often not consumer-friendly).
Window sticker (Monroney label): consumer-facing disclosure required by federal law for new cars, emphasizing MSRP, equipment, and regulated disclosures rather than internal production codes.

Why do people confuse them?

Because both can list options, colors, and packages. The difference is that the build sheet is “how it was built,” while the window sticker is “how it was marketed and priced at sale,” and they won’t always match perfectly if port/dealer items were added later.

Is a window sticker “better” than a build sheet for originality?

Neither is universally “better”:

For factory authenticity, a build sheet / factory option record is the stronger reference.
For original pricing and sales presentation, the Monroney label is the reference document.

Can I get a window sticker for any Saab VIN today?

Sometimes, but don’t assume that you can:

Saab as a manufacturer is defunct, so you’re often relying on third-party databases or platform-parent systems (GM-based cars tend to be easier in the broader GM ecosystem than pure Saab-era cars).
Availability depends on whether that VIN’s label data was retained and is accessible through the provider you’re using.

Model-specific “gotchas” U.S. owners run into

Do all Saab VINs start with YS3?

No. Example: Saab 9‑2X uses JF4 as WMI (Fuji Heavy Industries, Japan) per Saab’s own VIN system sheet. Saab 9‑7X uses 5S3 (U.S.-built Saab) per Saab’s VIN system sheet.

If I have a 9‑7X, where’s my “build/options” label?

Inside the glove box: the owner’s manual says the Service Parts Identification Label is there and lists VIN, model designation, paint info, and production options/special equipment.

If I have a 9‑3 or 9‑5, what’s the most authoritative VIN decoding reference?

Saab’s published VIN breakdown bulletins for 1999–2011 9‑3 and 9‑5, which explicitly map VIN positions to car line, body type, gearbox, engine codes, model year, and assembly plant.

If I have a classic Saab (Sonett/96/99/900), what’s the realistic best approach?

Use chassis-number references maintained by Saab communities for year/model interpretation.
Accept that you may not be able to obtain a comprehensive, factory-issued “build sheet PDF” on demand for every classic U.S. Saab, and you may be reconstructing originality via documentation + physical tags + period brochures.

Are “free build sheet” websites accurate for Saab?

Treat them as starting points. Some sites claim they can generate build sheets for Saab, but you should validate them against:

NHTSA VIN decode basics (make/year/plant logic where available)
Saab’s own VIN breakdown documents for your model/year
On-car labels when present (e.g., 9‑7X)

What about security-relevant data (keys/immobilizer) — is that part of “build data”?

It’s adjacent, and access is controlled. For example, Orio’s system describes a locksmith authentication process for keycodes that requires NASTF credentials and VIN entry. If someone offers to sell you sensitive security data with no verification, treat that as a red flag.

Practical advice and common misconceptions

Misconception: “If I have the VIN, I can always get the complete factory build sheet.”

Wrong for Saab in many cases. For some cars you’ll only get VIN-level decoding; for others you’ll reconstruct its configuration using parts/service systems; GM-based Saabs may give you more via the on-car SPID label.

Misconception: “A Carfax/AutoCheck-style report is a build sheet.”

It’s not. History reports focus on title events, mileage, accidents, and registrations; build sheets focus on factory configuration. (You can use both, but they answer different questions.)

What should I keep in my records once I’ve decoded everything?

For resale, restoration, and parts sanity:

Photo of VIN plate/labels on the car (not just paperwork)
Any on-car option label photo (9‑7X especially)
A saved PDF of the VIN decode mapping you used (Saab’s VIN bulletins for your model/year)
A single “as-built summary” you recorded, listing engine/trans, paint/trim, and verified option codes

Saab Build Sheet by VIN