Verify A06 Software Updates and Supported Features

Capture the starting configuration

Record VIN, production period, market, installed hardware and accessible software-version information. Retain clear images of the relevant menus without exposing private accounts or credentials. Use the model and trim identity record when a translated sales description differs from the actual configuration. Ask whether the head unit or any relevant module has been replaced, because a build record alone may not describe the current installation. Keep the starting condition with the proposed work so the buyer knows what will change. A seller saying the car has the latest system does not identify its version or prove eligibility for a particular function.

Establish a legitimate update route

Ask the manufacturer or a competent authorised service route to confirm the update's applicability to the exact vehicle and hardware. Obtain the source, purpose, prerequisite conditions and support scope. The official NEVO page and Changan technology demonstrations provide product context; they are not an update instruction for every export candidate. Do not download unknown firmware, share account passwords or use another model's package as a shortcut. If no supported route is confirmed, keep the proposed change outside the agreed equipment specification. A plan that depends on an unavailable or uncertain update is not equivalent to a function already demonstrated on the selected car.

Describe the required outcome precisely

List the buyer's actual needs: interface language, navigation, phone connection, controls, warning information or another identified function. Distinguish a bug correction from added equipment or a paid service. A software version cannot prove that the physical sensors or communications hardware needed for a feature are installed. Use the driver-assistance sensor assessment for related hardware or repair questions. Do not value a feature solely because it appears in a promotional video. Ask whether the proposed update changes the required function on this configuration, and retain any condition or limitation in the sourcing proposal.

Keep service accounts and regions separate

Verify whether the seller can remove existing associations and what the buyer must do through the official ownership process. Use the keys and app-account handover guide rather than treating a firmware installation as account transfer. Check destination service eligibility separately from the local demonstration. A local connection, translated interface or successful app login does not establish overseas map coverage, subscription, remote access or communications support. Record unavailable functions clearly. Never describe account bypass, identity substitution or credential sharing as a legitimate update pathway or a harmless way to make an imported car usable.

Document work and completion without unsafe instructions

Qualified personnel should follow the applicable process and conditions. The buyer's evidence pack should record the responsible party, date, starting and resulting versions, stated purpose and any warnings or incomplete actions. This guide does not prescribe power-supply, high-voltage or module-programming procedures. Do not interrupt or improvise an update as a demonstration. Ask what checks the responsible workshop performs afterward and whether the result is reproducible. An invoice saying software work was completed does not by itself prove that the requested functions are present, that all relevant modules are healthy or that destination services will remain accessible.

Retest the relevant real-world functions

After documented completion, repeat the buyer's supported function tests and record differences from the baseline. Preserve any new warnings, connection problems or unavailable menus rather than reporting only a changed version number. Charging-related work should connect to the charging-session evidence where applicable, and road behaviour should stay within a qualified inspection plan. Do not conduct hazardous driver-assistance demonstrations to prove a feature. If a promised change has not achieved its outcome, retain the failure or limitation as a hold point. A later repair or substituted vehicle requires a new relevant baseline and test.

Agree a clear handover boundary

The accepted proposal should identify demonstrated functions, unresolved service eligibility and who is responsible for any further work. For example, a seller may offer an update to improve a local interface while overseas remote services remain unconfirmed; those are separate outcomes and must not be bundled into a promise of full international functionality. Ask about legitimate destination workshop support through the hardware and parts support inquiry. Keep original records and the actual supported process available to the receiving workshop. The purchase decision should rest on documented capability and an acceptable support route, not confidence that an unknown future update will solve everything.

Buyer checklist

• Starting hardware and versions recorded
• Update source and applicability confirmed
• Requested functions precisely named
• Account and region eligibility separate
• Completion record retained
• Relevant functions retested

Buyer questions