VIN vs Rego Plate Lookup -- Which Is Better for Auto Parts?

When your software needs to identify a vehicle, there are two practical starting points: the VIN or the number plate. They are often treated as interchangeable, but they behave very differently -- especially in Australia, and especially for parts fitment. Here is how to choose.

What a VIN gives you

The VIN (Vehicle Identification Number) is a 17-character code assigned at manufacture. It is the vehicle's identity for life -- it never changes across owners, states, or re-registrations. Decoded fully, a VIN can pin down the exact build: plant, series, sometimes trim and drivetrain details.

The catches, in practice:

• Customers do not know their VIN. It lives at the bottom of the windscreen, on the door jamb, or in the paperwork. Asking a retail customer for it adds real friction to a checkout.
• 17 characters is a lot of typing. Transcription errors are common, and characters like I/1 and O/0 are banned from VINs precisely because people confuse them.
• Australian-market decoding is patchy. Generic VIN decoders are built around North American conventions; coverage and accuracy for Australian-delivered vehicles varies a lot between makes.

What a rego plate gives you

The plate is the identifier every driver knows by heart -- it is on the car in letters you can read from across the street. Combined with the state of registration, it resolves to the registered vehicle: make, model, model year range, body, and engine.

Its limits: the plate changes with re-registration or personalised plates, it identifies vehicles at the model-generation level rather than the individual build, and an unregistered vehicle has no active plate to look up.

The comparison that matters for parts

For auto parts fitment, the question is: which one gets you to the correct part with the least customer friction?

• Friction: plate wins decisively. Six-ish characters the customer knows, versus 17 they have to go find.
• Fitment precision: plates resolve to the model generation and engine -- e.g. "2003-2006 Toyota Corolla 1.8L petrol" -- which is the same granularity parts catalogues are indexed by. A full VIN decode is more precise than you usually need for fitment.
• Coverage in Australia: plate lookup works uniformly across all eight states and territories through an API like PlateAPI; Australian VIN decoding has no equivalent single reliable source.

That is why parts retailers overwhelmingly lead with plate lookup: the conversion cost of asking for a VIN is high, and the extra precision buys you nothing at the parts-catalogue level.

When the VIN is the right tool

VINs earn their keep in different jobs:

• Used car history checks. Australia's PPSR register -- finance owing, written-off status, stolen records -- is keyed by VIN, not plate.
• Compliance and recalls. Manufacturer recall lookups are VIN-based.
• Titles and transactions. Anything legal or financial follows the VIN because it survives re-registration.

In short: plate for identifying the car in front of you, VIN for investigating its history.

Using plate lookup in your application

A plate-based identification with PlateAPI is one request:

curl -s "https://api.plateapi.com.au/api/v1/lookup?plate=ABC123&state=VIC" \
  -H "X-API-Key: pk_live_YOUR_API_KEY"

The response identifies the vehicle at fitment granularity -- model year range, make, model, body, and engine -- with an alternatives array when one plate maps to several variants, so your customer confirms rather than guesses. No VIN required at any point.

You can see the exact data for a real plate on the live demo, read the API reference, or start on the free tier with 20 lookups a month. For the dropdown-based alternative when there is no plate available, see the vehicle database endpoint.