The Short Answer: Scan Before the Vehicle Moves
A diagnostic scan reads every electronic control unit for trouble codes before a vehicle leaves its source market, when repairs are still cheap and responsibility is still clear. The scan records stored, pending and permanent codes, freeze-frame snapshots, and readiness monitor status, and for electrified vehicles it can carry high-voltage battery findings where the tooling supports them. Ten minutes of scanning converts invisible electronic history into a dated document that travels with the export file.
What a Diagnostic Scan Actually Reads
Since the late 1990s, passenger vehicles carry a standardized diagnostic connector, and every control unit behind it, engine, transmission, brakes, airbags, battery management, logs faults as standardized trouble codes. A scan tool lists current faults, pending faults that have been detected but not yet confirmed, and permanent codes that the vehicle itself clears only after it verifies the repair. Alongside the codes, most tools report freeze-frame data, the operating conditions at the moment a fault was set, which turns a bare code into a story of what the vehicle was doing when something went wrong.
Readiness monitors complete the picture. These are self-tests the vehicle runs on its emissions systems; a full set of completed monitors with no stored codes is the electronic equivalent of a clean bill of health, while monitors stuck incomplete usually mean a recent battery disconnect or a fault recently cleared.
Why the Scan Belongs Before Shipping, Not After Arrival
Once a vehicle is loaded, three things change. Repairs at the destination cost more and start slower, because parts, tooling and brand-specific software for Chinese vehicles are thinner outside China than inside it. Responsibility blurs, because a fault found weeks after handover invites disputes about whether it existed at purchase. And evidence disappears, because anyone along the chain can clear ordinary codes with a scanner in seconds, while a dated pre-shipment report fixes the baseline.
The scan also protects the buyer's own planning: a vehicle with an unresolved airbag or high-voltage fault can face registration or homologation friction in the destination market, and discovering that at the port is the most expensive possible moment. New vehicles benefit from the same discipline, because factory-fill faults, transport battery drain and module resets during accessory fitting all leave electronic traces that are cheaper to document at the compound than to dispute after delivery.
Reading the Report: Not All Codes Are Equal
A raw code list is meaningless without triage. The table below is the classification used in professional inspection scopes.
| Finding | Typical Meaning | Risk Level | Reasonable Action |
| No codes, all readiness monitors complete | Clean electronic history | Low | Archive the report; proceed |
| One historic code, not current | Past event, since resolved | Low | Ask what was repaired; keep the note |
| Pending misfire or fuel-system codes | Fault being watched, not yet confirmed | Medium | Re-scan after a test drive before release |
| Stored misfire or catalyst codes | Active drivetrain fault | High | Repair at source; re-scan to confirm |
| Airbag, ABS or brake-system codes | Safety system fault | High | Repair and documented clearance before loading |
| High-voltage or battery management codes | EV or hybrid battery fault | High | Brand-level diagnosis; verify state of health |
| Permanent code after a stated repair | Repair done, vehicle still self-verifying | Low to medium | Document the repair; monitor after arrival |
| All monitors incomplete | Codes recently cleared or battery disconnected | Medium | Ask why; drive cycles then re-scan |
The pattern matters as much as any single code. A clean report after a documented repair is normal practice; a report with every memory freshly cleared and no paperwork behind it is a question that deserves an answer before payment.
Scanning EVs, Hybrids and Used Vehicles
On battery electric and plug-in hybrid vehicles, the generic scan remains the entry point, but the decision-grade information sits in the battery management system: fault history, cell imbalance indications and state of health, read with brand-capable tools where the manufacturer supports it. For used vehicles the scan is non-negotiable regardless of powertrain, because the electronic file is the only witness of how the vehicle was treated before it met the buyer. A scan also cross-checks the odometer against module readings where accessible, adding a data point against clocking.
Writing the Scan Into an Export Workflow
Professional sourcing workflows treat the diagnostic scan as a document with a fixed place in the sequence. First, scan before purchase for used vehicles, or at handover for new ones. Second, record the full report, codes, freeze frames, monitor status, date, tool used. Third, agree repairs for anything in the high-risk rows and re-scan to confirm the result. Fourth, ship the report with the commercial documents so destination registration or resale can cite it. Fifth, scan again at arrival and compare against the baseline; identical results close the loop.
For buyers sourcing through AutoCN, a diagnostic scan with a written report is a line item that can be required in the inspection scope before the vehicle is released for shipping, alongside photo documentation and the standard export checks, so the electronic condition is established while the vehicle is still at source.
Frequently Asked Questions
Can a seller just delete the fault codes before a scan?
Ordinary stored codes can be cleared in seconds, which is why the report also records readiness monitors and permanent codes. Cleared memories leave monitors incomplete, and permanent codes survive clearing by design. A freshly wiped, incomplete set with no repair story is itself a finding worth questioning.
What is the difference between pending, stored and permanent codes?
Stored codes are confirmed active faults. Pending codes have been detected once and await confirmation, so they predict rather than report. Permanent codes are set by the vehicle itself and can be cleared only by the vehicle after it re-tests and verifies the repair, making them the strongest single signal in the file.
Should codes be cleared after a verified repair?
Clearing after a documented repair is normal workshop practice, and the re-scan then shows either a clean system or a returning fault. What matters is the paper trail: repair order, replaced parts, and the before-and-after scan reports, all dated. Clearing without paperwork removes information without adding any.
Does an EV need the same pre-export scan?
Yes, with an emphasis on the battery side. The generic scan still reads chassis and powertrain faults, but for battery electric vehicles the additional value is in battery management data, fault history and state of health where the tooling supports it, because battery condition dominates the vehicle's value and destination-market acceptance.
What if a fault appears only after arrival?
Compare the arrival scan against the pre-shipment baseline. A code already visible, even as pending, in the pre-shipment report points to a condition at source; a genuinely new code indicates a fault that developed in transit or after handover. The dated pair of reports is what makes that distinction possible.
Conclusion: Fix the Baseline While the Vehicle Is Still at Source
The pre-shipment diagnostic scan costs minutes and settles the question every importer eventually faces: was this fault there before the vehicle moved? Scanned before purchase or loading, with codes triaged, repairs documented and the report shipped with the file, electronics stop being a leap of faith and become a managed line item. AutoCN supports buyers in specifying these checks as part of sourcing and export preparation for Chinese vehicles, and related export guidance is available through 573auto.cn buyer guides.
For more information, you can contact us. jiasou666@gmail.com