CHECK 01
Identify the hardware behind the screen
Request the vehicle reference, production information and visible head-unit details. Ask whether the unit is original, replaced or modified. Similar model names can describe different market equipment, and a screen photograph may not show what hardware or software is installed. Keep the original designation and the seller’s explanation together before asking which updates apply.
The GS3 and EMZOOM naming guide establishes market and production context. An overseas brochure should not be used to select software for a China-market unit without an applicable confirmation. If identifying information is incomplete, request clarification through the responsible provider. A familiar display layout is not sufficient evidence that a software package belongs to the particular car.
CHECK 02
Define the function you need from the change
State the actual task: a required menu language, stable phone connection, ordinary media operation or resolution of a documented complaint. These are separate outcomes. A seller can show that the software number changed without establishing that any of those requirements now works. Keep the desired result visible instead of accepting updated as a complete feature description.
The software and regional-function overview separates offline controls from services dependent on accounts or networks. If an online function is essential, identify the support and destination context as well as the installed version. An update should not be described as a universal route to overseas connectivity merely because it improves one source-market demonstration.
CHECK 03
Ask for a supported procedure and provider
Have the relevant provider confirm whether an update is available and appropriate for the identified unit. Ask who performs it, which tasks it covers and what limitations they disclose. Do not choose a file from another vehicle or an unverified download link to satisfy a sales deadline. The buyer needs an applicable, traceable process rather than instructions copied from an unrelated screen.
If a seller proposes unofficial software or additional hardware, request a separate explanation and assess it as an added modification. Identify continuing support, applicable terms and any effects the provider says require review. Keep it out of the ordinary factory-equipment description. A paid modification may be offered, but the buyer should understand what has been changed and who accepts responsibility for the proposed arrangement.
CHECK 04
Record the before-and-after state
Preserve the starting version information, identified complaint and date of the work. Add the provider’s completion record and the visible state afterwards. Keep sensitive account screens out of shared inspection material. A video showing only the final home screen cannot explain which vehicle was changed or whether an earlier warning was actually resolved.
Where preparation includes a reset, ask which settings or account arrangements need re-establishing. Do not assume a factory-looking screen establishes ownership transfer or deletion of every prior user association. Use the key and account handover checklist for those separate requirements. The software work and the legitimate receiving-user setup should each have a clear result.
CHECK 05
Repeat the buyer’s essential demonstrations
After the supported change, test the agreed normal tasks on the actual car. Include a routine restart and a phone reconnect where relevant, using the intended device arrangement. Record the software, accessories and conditions. A successful demonstration before an update should not automatically be retained as evidence of the final setup without checking whether the change affects it.
The CarPlay and Android connection review specifies the phone task independently of the update. Charging a phone, playing Bluetooth audio and displaying projected navigation are different demonstrations. Keep the verified outcomes precise, and mark anything unavailable or untested. A favourable result for one device should not become a promise for every phone or future software revision.
CHECK 06
Keep the delivered setup in the offer
Put the installed-unit identity, completed change and verified requirements beside the final vehicle reference. Identify any accessory travelling separately and the responsible support contact. For new stock, retain this with pre-delivery preparation; for used stock, preserve disclosed replacement or modification history as well. A substitute car needs its own review even if it carries the same trim name.
The delivery preparation checklist helps connect the final setup with the car released to the buyer. If an essential outcome remains unsupported, choose another candidate or make the limitation explicit before acceptance. The dealer can then describe what the delivered GS3 actually does without turning an unspecified update into a guarantee of every language, app or online service.
Make the next request specific.
Send the condition, accepted years and version, destination and quantity. Include the items that must be confirmed before you accept a candidate. A sourcing enquiry begins the discussion; availability and purchase terms require an actual offer.
Discuss a suitable GS3 →