Salvage VIN Lookup

When the compliance plate is gone

Salvage vehicles arrive damaged. Sometimes the damage is exactly where the identifiers are. A front-end collision can take the compliance plate with it. Fire damage can make a VIN unreadable. A vehicle bought at auction from photographs can turn up with less information attached than the listing suggested.

Our API accepts a VIN, a chassis number, or a rego plate, and returns the same verified record whichever you have. If one identifier is unreadable, you work with another rather than guessing from the badge on the boot.

Why write-off category changes the buying decision

The WOVR classification is not an administrative detail for a salvage operator. It decides what the vehicle is for.

A statutory write-off can never legally return to the road. Its entire value is in components and materials, and it should be priced and processed on that basis.

A repairable write-off can be repaired, inspected and re-registered. That changes the calculation completely. The same vehicle might be worth more intact to a repairer than dismantled in your yard.

Getting that wrong in either direction costs money. Dismantling a vehicle that had repair value burns the margin. Paying repair-project prices for a statutory write-off leaves you holding a parts car you overpaid for.

Checking the category before the hammer falls, rather than after the transporter arrives, is a two-second lookup.

Screening what comes into the yard

Salvage yards are a known destination for stolen vehicles, and a known source of identities for rebirthing. A yard that unknowingly processes a stolen vehicle can lose the vehicle, lose the labour already spent on it, and end up part of an investigation.
 
A stolen check at intake, run automatically as part of the booking-in process rather than manually when something feels wrong, closes that exposure. Combine it with a PPSR check and you also catch vehicles carrying a registered security interest, where the secured party has a claim that survives your purchase.

Where this fits in a recycling operation
 

• At auction and acquisition. Run a lookup before bidding. Confirm what the vehicle actually is, what category of write-off it carries, and whether it is clean. Auction listings are built from limited information and are not always right.

• At intake. Populate your yard management system from the lookup instead of keying in details from a damaged plate. Fewer keystrokes, fewer transcription errors, and a consistent record from day one.

• At cataloguing. Variant-accurate identification is what makes interchange data reliable. A part catalogued against the wrong variant will be sold against the wrong variant.

• At listing. Online recycled parts buyers are buying sight unseen from a description. Accurate make, model, series, variant, engine and build date in the listing is the difference between a sale that sticks and a return that eats the margin and the freight.

• At compliance. Keep timestamped, auditable records of what every vehicle was, sourced from the official register, against your dismantling and reporting obligations.

Returns are an identification problem

A wrong part coming back costs you the freight both ways, the restocking, the handling, and a buyer who now has a reason to try someone else. Across a national customer base, freight alone makes returns disproportionately expensive.
 
Most wrong parts are not picking errors. They are identification errors made weeks earlier, at intake, when a vehicle was catalogued as something slightly different from what it actually was.
 
Fixing it at the point of identification fixes it everywhere downstream.

Built to fit how you already work

Lookups run by VIN, chassis number or rego plate. Batch processing handles bulk intake and back-catalogue cleanup without anyone keying in identifiers one at a time.

The API integrates into yard management systems, inventory platforms and online parts marketplaces. If your workflow needs a specific field set or a custom response format, that is a conversation rather than a refusal.

Free test environment, so your developers can build against it before anything is signed.

Where the data comes from

Vehicle identity, registration, written-off and stolen data is sourced from NEVDIS, the National Exchange of Vehicle and Driver Information System managed by Austroads on behalf of Australia’s state and territory road authorities. InfoAgent is an authorised NEVDIS broker.

Every dataset comes from an authorised channel. You will know exactly where your data comes from.