SOH answers only part of the battery-capacity question in a used EV. Procurement teams have grounds to decide on deeper inspection only after cell consistency, temperature differences, fault history, fast-charging records, and repair records have been reconciled. Every conclusion must be limited to the same subject, version, and review date.
Divide Vehicle-Condition Clues into Three Evidence Levels
The first level consists of visible states such as cell-voltage differences; the second uses temperature, fast-charging, and other records for cross-checking; the third is professional measurement or disassembly. The first two may trigger escalation, but cannot be presented as third-level diagnosis.
| Observation | Original record | Reinspection method | Escalation condition |
|---|---|---|---|
| Cell-voltage difference | Location, measured value or status, unit, time, and photo of the same point | Recheck the cell-voltage difference after a version change | Close this field only |
| Temperature difference | Location, measured value or status, unit, time, and photo of the same point | Confirm that the temperature difference refers to the same vehicle or plan | Leave blank and assign a document owner |
| Fault history | Subject, original status, source date, and reviewer | Retain the original page or photo of the fault history | Return it to the originating role for review |
| Fast charging | Subject, original status, source date, and reviewer | Have the responsible reviewer check the date and scope of the fast-charging record | Keep pending |
| Repair records | File name, original page, version, date, issuer or confirming party | Use a second record to check consistency | Pause before the next review stage |
| Warranty conditions | File name, original page, version, date, issuer or confirming party | Link the warranty conditions to the responsible person's sign-off | Record the difference and reopen the decision |
SOH Is a Durability Indicator, Not a Cell-Consistency Conclusion
UNECE UN GTR No. 22 on in-vehicle battery durability establishes a framework for SOCE, SOCR, and in-vehicle battery health monitoring while leaving the manufacturer's calculation algorithm unspecified. It shows that a health indicator must be defined, read, and verified; it does not supply cell-voltage or temperature-difference limits, or a repair conclusion, for a particular VIN.
Procurement inspection should therefore treat SOH as one field rather than an overall verdict. Cell voltage, temperature, diagnostic codes, state of charge, and test conditions must come from the original diagnostic record for the same VIN. Acceptable values, rest conditions, and retest procedures must come from the OEM diagnostic information for the corresponding version. Without OEM limits, record the observed value and “retest required,” rather than “battery normal” or “replacement required.”
The Conclusion Level Rises with the Evidence
With one visible clue, state “reinspection required.” When several independent records agree, identify the risk direction. Form a technical conclusion only after obtaining a qualified inspection and the technical information for the corresponding version. If visible clues extend to the brakes, steering, load-bearing structure, or high-voltage system, records have been obscured by cleaning, or professional reinspection cannot be completed, route the vehicle to technical inspection and suspend the condition conclusion.
The Inspection Report Must State the Sampling Conditions
SOH, cell-voltage differences, and temperature differences can be read together only for the same VIN under similar state-of-charge and equivalent rest or load conditions. Require the report to retain the diagnostic tool, software version, sampling time, units, ambient and battery temperatures, diagnostic-code timestamps, and retest conditions. If these fields are absent, state only “retest required.” U.S. Department of Energy materials are used here only to explain that SOH and consistency are different observation dimensions; the vehicle-specific conclusion still depends on OEM information for that VIN and in-vehicle test records.
How to tie vehicle identity to the inspection timestamp
Regarding Brazil’s “In second-hand electric vehicle inspection reports, the most easily overlooked thing besides SOH is consistency”. First, put the vehicle, version or source batch, inspection date, mileage reading and record custodian in the same record. In this way, when later discussing the battery, appearance, certificate or maintenance status, it is possible to confirm which car each conclusion corresponds to, without mixing the results of the same car series, different years or different inspection dates. If the identity of the vehicle is still confirmed by file name, chat screenshot or verbal description, it should be marked as awaiting supporting evidence first and do not write it as verified.
The checklist should treat "what you see" and "what you can decide from it" separately. VIN, nameplate, registration documents, inspection reports, photos and maintenance records respectively record the source, record creation date, uploader and reviewer; when the report has missing pages, missing corners of photos, or readings and dates are incompatible, write the discrepancy field and designate the owner of the missing evidence. Set pause points for fields that affect payment, transportation, or customer commitments. A single piece of information cannot replace the entire chain of evidence.
Use the following record structure to keep the review fields, evidence sources, and release conditions traceable:
| Verification field | Recording requirement |
|---|---|
| Vehicle/lot identification | Record the current value, direct source, and applicable scope |
| Check date and mileage | Record the date, method, reading, and supporting evidence |
| Evidence documents and original sources | Record the document name, version, page, or original URL |
| Exception fields and scope of influence | Describe the discrepancy and the decisions it affects |
| Responsible person and cut-off point for supplementary documents | Assign an owner, deadline event, and reopening condition |
Use this table to keep the evidence and affected decisions traceable. The final decision must still be checked against the original record and the current vehicle or batch.
What to do about certification after a reporting gap surfaces
Gaps can be divided into three categories: formatting issues that only affect the description, missing data that affects a single field, and identity issues that cannot confirm the vehicle or the time of inspection. The first category allows revision prior to delivery; the second category requires supplementing original documents or re-inspecting; and the third category should suspend the affected procurement, release, quotation or delivery actions until the vehicle identity and conclusion scope are re-closed. Writing the reason for the suspension into a repeatable sentence makes it easier for the next person in charge to take over than stacking "to be confirmed" in the note.
After completing the evidence update, fill in the latest mileage, inspection date and reviewer into Brazil's "Second-hand electric vehicle inspection report, the most easily overlooked thing outside of SOH is consistency" record, and check the vehicle identification again before release.
FAQ
Can checking only the cell-voltage difference show whether the battery pack merits further inspection?
No. It closes only one field. Temperature differences, fault history, and fast-charging records must also be matched.
Can historical temperature-difference records replace the current batch's materials?
They can inform the follow-up checklist. The current batch must still reconfirm the subject, version, and date of the temperature record and the warranty conditions.
Which conflicts require escalation?
Escalate to technical inspection and suspend the condition conclusion when clues extend to the brakes, steering, load-bearing structure, or high-voltage system, records are obscured by cleaning, or professional reinspection cannot be completed.
One inspection report: sufficient to confirm vehicle status?
No. First check whether the vehicle identification, detection date, mileage and method in the report are consistent with the current object; the report can only support the fields it covers and cannot automatically expand to the entire vehicle or other time points. This question should be reviewed in conjunction with Brazil’s “In second-hand electric vehicle inspection reports, the most easily overlooked thing besides SOH is consistency” plus the matching original records.
Inspection date out of step with shipping or delivery: redo needed?
First determine whether any use, maintenance or transportation events that affect the conclusion occurred during the period. If state continuity cannot be proven, the affected fields should be reexamined and commitments that rely on the old conclusion should be suspended. This question should be reviewed in conjunction with Brazil’s “In second-hand electric vehicle inspection reports, the most easily overlooked thing besides SOH is consistency” and the corresponding original records.
Submit Battery-Health and Consistency Records for the Same VIN
Organize the cell-voltage differences, temperature differences, fault history, and warranty conditions for the same vehicle or batch, then submit redacted materials through the contact page. Starvia can review the handoff of Chinese-side materials. Brazilian approval, underwriting, repair authorization, and taxes remain subject to confirmation by the competent local parties.
This article covers the records and review steps required to decide whether a battery pack merits further inspection. Brazilian cases require final confirmation against the relevant contract, VIN records, official documents, and actual vehicle condition. No conclusion should be inferred for vehicle variants, destination markets or transaction terms not stated here.
This article explains a document-review method for the vehicle and transaction scenario described for Colombia. It does not determine local import eligibility, customs, tax, registration or technical outcomes, or guarantee a vehicle's price, availability, delivery or warranty. Each transaction depends on current official requirements, the contract, VIN-specific records, the vehicle's actual condition and confirmation by the competent local party. No conclusion should be inferred for vehicle variants, destination markets or transaction terms not stated here. Review date: 2026-09-28.