On this page
Start hereThis guide is a route into brand-specific research. It is not a universal character decoder or a promise that every linked database record has completed a fresh verification.
Three documented starting points
| Manufacturer example | What the source establishes | What it does not establish |
|---|---|---|
| Volkswagen | Its UK guidance describes where engine-code information can be found | That the same locations or one code length apply to every brand/generation |
| Toyota | The cited Prius Plug-in brochure uses M20A-FXS as an engine designation | A universal letter-by-letter decoder or a replacement compatibility rule |
| Ford | The cited manual has an application-specific engine-number location | That an engine serial number and a marketed family name are interchangeable |
Use the relevant Volkswagen guidance, Toyota specification or Ford manual example within its stated scope.
How to read a brand hub
Start with the exact designation you have and confirm whether the hub treats it as a family, variant or full record. Check the production context and sources, then follow the relevant record rather than assuming the first similar-looking code is a match.
Useful entry points include BMW, Mercedes-Benz, Audi, Volkswagen, Ford, Toyota, Jaguar, Land Rover, Peugeot and Renault. The manufacturer directory provides the wider set of brands.
The links are navigation aids, not endorsements of a replacement-engine application. A questionable source or mapping on a destination should be reported.
Keep a manufacturer-specific reading note
For each code you research, record:
- The exact designation and its source.
- Whether it names a family, a variant or an individual unit.
- The applicable generation, production period and market.
- Any manufacturer explanation of the format.
- What has been directly confirmed and what is only inferred.
Preserve suffixes until a relevant source establishes whether they can be omitted for your purpose. Do not apply another manufacturer's convention to explain an unfamiliar code.
Why a badge can be insufficient
A marketed badge can identify a model or broad technology without supplying all the information needed for a component or engine replacement. Even when the badge looks familiar, ask for the exact application evidence.
Read how to read an engine code for the transcription method. The identifier comparison explains why a VIN or registration lookup answers a different question from identifying the installed engine.
What if the brand uses several systems?
Treat the generation or document change as part of the task. A rule documented for one period should not be extended automatically to older engines, imports, related brands or a later redesign.
Shared engineering does not guarantee shared naming. Two brands can use related designs while their identifiers, records and application requirements remain different. See shared engine platforms.
Help improve a naming explanation
If a brand page gives an unsupported character meaning, send the statement and a relevant manufacturer source through Report a Problem. Do not create a new code by combining a valid family prefix with a guessed suffix. The existence of the identifier itself needs evidence, as explained in our verification guide.