When a used vehicle intended for Egypt has conflicting battery state-of-health test methods, a supplier's brief explanation can easily distort the purchasing decision. The priority is to restore a verifiable evidence chain and record confirmed facts, reasonable explanations, and outstanding items separately.
Preserve the condition in which the discrepancy was found before assessing the supplier's explanation. Record the VIN, battery identity, metric definition, device model, software version, vehicle condition, and test time. Any later submission can then be compared with the original state instead of being mistaken for the initial evidence.
Confirm That Both Reports Measure the Same Metric
The required evidence includes complete test reports, device screenshots, diagnostic sessions, instrument-cluster status, charging or discharging context, fault codes, and the tester's notes. Every item must identify the vehicle, creation time, and provider. Where an attachment cannot be tied to an identifiable subject, even if its name is similar, it stays pending and is kept out of the confirmed record.
Use a fixed inspection sequence. Transcribe each metric name and unit, then verify whether the vehicle was resting, charging, or being driven before the test. Explain results from different methods separately rather than ranking them directly. Inspectors should record observations and test conditions; the appropriate technical role should determine causes so that an observation is not prematurely labeled as an accident or repair conclusion.
Record the Equipment, Software, and Vehicle State Together
If evidence about the test-method discrepancy conflicts, compare originals, dates, and vehicle identifiers first, then ask the issuer one question that can be answered in writing. The buyer should retain prior versions and reasons for each change so that reviewers in Egypt can see how the conclusion was reached.
Completeness is not established by the number of files. Every conclusion needs a traceable source, and the same fact should remain consistent in the contract, acceptance record, and customer disclosure. Translations should preserve the original document names and their relationships.
Separate Method Differences From Battery Abnormalities
Pause the transaction if a report cannot be tied to the vehicle, the metric is undefined, or repeat tests under matching conditions still show a substantial unexplained difference. A pause does not mean the vehicle has necessarily failed. It means the evidence is insufficient for further payment, shipment, or customer disclosure until the agreed supplementation or retest is complete.
At re-review, the parties should agree on one method for retesting and should not price the vehicle from a single result before that retest is finished. The EV inspection lead consolidates the findings, the contract specialist checks responsibilities and deadlines, and the purchasing approver signs only conclusions that list the applicable VINs.
The same metric label may reflect different calculations in different tools. Reviewers can prepare a method-comparison page showing the device label, report field, data source, and testing party's explanation side by side. This prevents translation from reducing different concepts to one identical term. If the tester supplies an algorithmic conclusion without raw values, state the limits of independent review and supplement it with vehicle status, fault codes, and other inspection evidence. The pricing meeting should first decide which result follows the agreed method rather than choosing the highest or lowest number as a shortcut.
Battery Health Comparability Decision Table
| What to check | When you can proceed | When you must pause | Who is responsible |
|---|---|---|---|
| VIN | Records identify this vehicle and show when they were created | Subject or date cannot be identified | Document intake coordinator |
| Original evidence | Complete test report is corroborated by other records | Only a retelling is available or the source cannot be retrieved | EV inspection lead |
| On-site review | Test conditions, process, and results are all recorded | Report cannot be tied to the vehicle, metric is undefined, or comparable retests still differ materially without explanation | Vehicle inspection technician |
| Commercial decision | Both parties agree on one retest method, and no single result controls pricing before completion | Responsibility, cost, or retest milestone remains unwritten | Purchasing approver |
This table applies only to the current order. When additional evidence arrives, the EV inspection lead reviews what changed and records the basis for lifting the pause. Other roles continue using the previous status until a new conclusion is approved.
Put the Retest Plan Into the Contract and Delivery File
Check Egypt's current filing and market requirements through an official source. Government pages explain administrative procedures, while transaction documents, physical inspection, and professional opinions establish this vehicle's technical and historical condition. Neither replaces the other. Start with the Egyptian Customs ACI service, and rely on the information available on the processing date if the page changes.
After the vehicle reaches Egypt, recheck the evidence points covered by this review using the same angles, identifiers, and conditions recorded before shipment. If the condition changes, create a separate arrival record that distinguishes the original gap, transport effects, and destination handling.
When briefing the customer, list confirmed facts, unresolved items, and scheduled actions separately. A report number is meaningful only when its method and conditions are clear; it cannot become an unverified range or service-life promise. Buyers may also consult the charging-standard FAQ for imported EVs to organize the vehicle-identification fields needed here. That page does not replace the vehicle's own records or test results.
Any customer document citing a battery-health result should include the test date, method name, and limitations. If a later retest uses new software or equipment, create a new version so that differences remain traceable.
The procurement file should state the comparison method selected for this order and the reason for choosing it. If the supplier later submits a report generated by another algorithm, place it in an appendix and have the inspection lead determine whether it changes the transaction recommendation. It must not silently replace the original basis.
FAQ
If two SOH results differ, should we accept the newer one?
A newer date does not make a method more suitable. Compare metric definitions, equipment, software, pre-test vehicle condition, and battery identity. If conditions cannot be aligned, retain both results and state the scope of each.
Is a photo of the device screen enough?
The photo can establish what was displayed at that moment, but a complete report, VIN or battery identity, test time, and operating conditions are also required. An image that cannot be linked to the vehicle is not a sound pricing basis.
Can we wait and conduct one standardized retest after arrival?
An arrival retest can be arranged, but the contract should first state the pre-shipment condition, test method, treatment of differences, and cost responsibility. Questions that could change the purchase price are better resolved before payment.
Can the SOH result be converted directly into real-world range?
No. Vehicle specification, operating environment, driving, and charging conditions also affect actual performance. Preserve the test method in customer disclosures and do not present one metric as a road-performance promise.
On questions about battery SOH tests that use different methods for an Egypt order, send the model, quantity, and current document status through WhatsApp or contact Starvia. This next step clarifies the fields still requiring review; it does not constitute vehicle release.
Produced by Starvia Automotive as general operational guidance for used-vehicle procurement in Egypt. It is not a promise regarding eligibility, law, tax, insurance, or vehicle performance. Apply the destination authority's current requirements together with the transaction documents, model information, and actual vehicle condition. Information reviewed on 2026-09-10.