VIN Assembly Plant Codes: How Position 11 Works

Position 11 of a 17-character VIN is the assembly plant code. Manufacturers assign these characters to specific factories or manufacturing lines. Unlike model year codes, plant letters are not a single global alphabet—you must interpret them in the context of the brand and WMI.

DecodeAnyVin surfaces the plant character and, where rules allow, human-readable plant names. That is still factory identity data, not a record of accidents, titles, or mileage.

Where plant fits in the VIN

• Positions 1–3: WMI (manufacturer identity)
• Positions 4–9: descriptors + check digit
• Position 10: model year
• Position 11: plant
• Positions 12–17: sequential production number

Structure refresher: how to read a VIN.

Why plant codes are brand-specific

Toyota, Ford, and Volkswagen can each use the letter C for entirely different facilities. Publishing a universal “C means Ohio” table is misleading. Correct interpretation needs:

1. The WMI / manufacturer
2. Sometimes the model line (large makers reuse letters across divisions carefully, but documentation is still maker-scoped)
3. Manufacturer service information or a brand-aware decoder

Use brand tools: Toyota, Ford, Volkswagen, Honda.

Plant vs WMI country

WMI region and plant location usually align but not always in the way marketers imply. A U.S. WMI with a U.S. plant is straightforward. A European brand may assemble in Mexico, the U.S., or South Africa under different WMIs. Japanese brands operate major plants in North America with local WMIs.

Read both fields before accepting “JDM” or “German-built” claims. See WMI explained, Japanese vs North American VINs, and European VIN differences.

How plant codes help buyers

• Authenticity: Rare trims tied to one factory should show that plant character.
• Parts: Some catalogs differ by market/plant even within a model year.
• Reputation research: Enthusiasts sometimes track plant-specific build quirks—useful context, not destiny.
• Fraud checks: A seller claiming Kentucky-built while the VIN points elsewhere needs an explanation.

How plant codes do not help

Plant codes will not tell you:

• Whether that factory had a good or bad week when your unit was built
• Option packages beyond what descriptors encode
• Post-build crash or flood damage
• Whether the VIN plate is original

Limits overview: what a VIN cannot tell you.

Reading plant with year and serial

Plant + year + serial uniquely situate a vehicle in production. Two cars with the same descriptors but different plants are different units. When comparing “matching numbers” claims on enthusiast vehicles, plant and serial ranges matter alongside engine stamps—and engine stamps are not the VIN.

Practical verification steps

1. Decode the VIN on DecodeAnyVin.
2. Note position 11 and any resolved plant name.
3. Compare to window stickers, build sheets, or manufacturer “find my build” tools when available.
4. Be wary of aftermarket “heritage” plaques that are not factory documents.
5. If plant and story conflict, dig into cloning and paperwork checks (VIN cloning).

Commercial and incomplete vehicles

Cab-chassis and multi-stage vehicles can involve more than one manufacturer label. The road-going VIN’s plant code refers to the stage that assigned that VIN. Body builders may add separate plates—read them without mixing numbers into the 17-character VIN.

EVs and modern plants

EV factories still use position 11. Gigafactory-style branding in ads does not override the VIN. Confirm with a decode: electric vehicle VINs and brand pages such as Tesla VIN check.

How manufacturers publish plant maps

OEM service information, dealer technical portals, and sometimes owner “build sheet” tools map position 11 to factory names. Enthusiast wikis can help but go stale when plants retool or codes are reused after closures. Prefer primary documentation when money depends on the claim. DecodeAnyVin includes plant resolution where brand rules provide it—still treat obscure codes cautiously if the ruleset is generic.

Closed plants and reused letters

When a factory closes, makers may reassign letters years later. A historical decoder table can mislabel a modern vehicle if it is not year-aware. Always interpret plant codes with model year context. If a listing cites a legendary plant for prestige, confirm the code against year-correct references.

Quality narratives vs data

Internet lore sometimes ranks plants by “better build quality.” Individual vehicles vary more than forum averages suggest. Use plant data for authenticity and parts routing, not as a substitute for a compression test or paint-depth readings. A PPI beats plant mythology every time.

Documenting plant for resale

When you sell, including plant and WMI in your description—with a DecodeAnyVin link—reduces repetitive buyer questions. Photograph the door label manufacture date beside the VIN so buyers can see year vs build-month nuance without arguing in comments.

Export plants and port-installed options

Some vehicles leave the assembly plant incomplete relative to the final retail configuration. Port-installed accessories—spoilers, running boards, electronic kits—will not change position 11. Buyers sometimes think a plant code implies a certain accessory package; it does not. Use build sheets or window stickers for port options, and the VIN plant character only for the factory that assembled the core vehicle.

When two plants build the “same” model, compare TSBs and parts diagrams by VIN rather than assuming interchangeability across every fastener and harness clip.

Treat plant codes as manufacturer-defined factory IDs. Decode them in brand context, pair them with WMI, and use mismatches as questions—not as proof by themselves. Start with the free decoder whenever a listing boasts about where a vehicle was built.