“Still under warranty” and “the battery is in good health” are separate determinations for a used EV. The former depends on VIN-applicable terms and commencement rules; the latter depends on a clearly defined SOH measurement method. This article answers only the current question and does not expand the method into a market-wide conclusion.
Enable the next reviewer to reproduce the same battery-risk and warranty decision
The verification table separately records the warranty provider, VIN coverage, commencement date, mileage cap, transfer conditions, exclusions, SOH tool and software version, and measurement date.
| Condition indicator | Location, value, or photo | Cross-check | Pause condition |
|---|---|---|---|
| VIN-applicable terms | File name, version, page, signatory or confirming party, and applicable subject | Use a second source or later retest to check whether the VIN-applicable terms are consistent | Retain the range and trigger a review |
| Current mileage | Location, measurement or observed condition, unit, time, and matching-location photo | Use a second source or later retest to check whether current mileage is consistent | Retain the range and trigger a review |
| First registration | File name, version, page, signatory or confirming party, and applicable subject | Use a second source or later retest to check whether first registration is consistent | Retain the range and trigger a review |
| Service records | Subject, measurement basis, source date, and responsible person | Use a second source or later retest to check whether service records are consistent | Retain the range and trigger a review |
| SOH method | Subject, measurement basis, source date, and responsible person | Use a second source or later retest to check whether the SOH method is consistent | Retain the range and trigger a review |
| Exclusions | Subject, measurement basis, source date, and responsible person | Use a second source or later retest to check whether exclusions are consistent | Retain the range and trigger a review |
Connecting public methods with current-batch battery and warranty records
One external fact comes from the Uruguay guidance on warranty repair receipts, which confirms that a comprehensible service receipt should be retained after a warranty repair. It does not establish that a fault falls within warranty coverage.
Another boundary comes from the AFDC electric vehicle maintenance guide, which helps organize the scope of EV maintenance checks. It does not replace the OEM manual or battery diagnostics.
When a public page and a current-batch document have different scopes, retain an explanation of the difference rather than using a broader general conclusion to override a specific restriction.
What the reviewer and business owner confirm separately
Do not confirm remaining warranty or SOH when the seller can provide only the first registration date or an instrument-cluster screenshot. Status should be stated only as confirmed, pending, or paused, avoiding an ambiguous “in progress.”
Pairing vehicle identity with inspection time
Regarding Uruguay's "How to verify the remaining warranty of a second-hand electric vehicle, you can't just look at the first registration date". 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 separate "what you see" and "what you can decide based on it." 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.
Adding evidence once gaps in reporting appear
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 may still be changed before 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 the Uruguay record, and check the vehicle identification again before release.
FAQ
Who confirms the VIN-applicable terms in the table?
The responsible role must also confirm current mileage and first registration. One verified field cannot replace the complete set of decision inputs.
Can hypothetical examples be used directly for quotations or procurement when confirming battery risk and remaining warranty?
The inspection sequence can be reused; amounts, thresholds, model applicability, and approval status cannot.
What triggers a reassessment of battery risk and remaining warranty?
Do not confirm remaining warranty or SOH when the seller can provide only the first registration date or an instrument-cluster screenshot.
Is a lone inspection report enough to establish 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.
If the inspection date does not match the shipping or delivery date, does it need to be redone?
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.
Materials for requesting an organized battery-risk and warranty decision draft
Submit the VIN-applicable terms, current mileage, first registration, service records, SOH method, and exclusions through the contact page. Identify the responsible party separately for Chinese-side materials, export documents, and destination confirmation so they do not substitute for one another.
This article explains a document-review method for the vehicle and transaction scenario described for Uruguay. 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.