Identify the installed system first
Request the vehicle reference, source market, production information and visible head-unit details. Ask whether the unit is original or has been replaced or modified. A similar-looking Dashing screen may belong to a different market configuration. Keep the original designation with the seller’s explanation before deciding which update or language work is appropriate.
The version naming guide distinguishes earlier and later China releases from global Dashing descriptions. A product photograph can illustrate the design without establishing the software installed on the candidate. If the provider cannot identify the unit, ask what information is missing rather than treating a familiar model name as sufficient application evidence.
Define what the customer wants changed
Specify the tasks that determine acceptance: ordinary vehicle controls in the required language, a particular phone connection or resolution of a recorded complaint. These are separate outcomes. A changed software number cannot prove them all, and a translated phone app should not be described as conversion of every vehicle menu.
Use the software and connected-function overview to distinguish local controls from services dependent on accounts, subscriptions or networks. A source-market function needs destination context when overseas operation matters. Keep each unconfirmed task visible rather than accepting international software as a broad promise whose actual scope the buyer cannot assess.
Obtain a supported work proposal
Ask the responsible provider to confirm the method for the identified unit, what it changes and what limitations apply. Keep any additional hardware or unofficial modification disclosed separately. The buyer should understand whether the proposal concerns an applicable update, configuration work or an added aftermarket arrangement, along with the party offering support.
Do not select firmware from an unverified download or another vehicle to meet an enquiry deadline. This guide asks for purchasing evidence rather than giving installation procedures. If the required result is unsupported, compare another candidate or revise the accepted requirement before proceeding. An undefined future update is weak evidence for a function the customer must have at delivery.
Retain a before-and-after record
Preserve the relevant starting information and complaint, the date of work and the provider’s completion summary. Record the visible final system details where available. Keep account credentials and unrelated personal content out of the shared file. A polished final-screen photograph does not explain which unit was changed or whether an earlier problem was resolved.
If a reset is included, identify which settings or associations need re-establishing. The key and account checklist addresses legitimate user access separately. Deleting saved preferences can be useful preparation without proving every prior association has been released. The software work and the receiving-user arrangement each need their own interpretable completion result.
Repeat essential cabin and phone checks
Demonstrate the required normal tasks on the finished car, including ordinary restart or reconnect steps where relevant. Identify the phone and accessory arrangement and preserve any failure or limitation. Evidence obtained before a change should not automatically be treated as proof of the final installation. The buyer needs one coherent delivered setup rather than successful demonstrations taken from different cars.
The CarPlay and Android Auto review separates calls, audio and projected functions. Also repeat any relevant parking display checks where the work could affect them. A working phone interface cannot certify the required camera views, and a working view does not establish every language or account service.
Describe the delivered result precisely
List verified functions, dependencies, supplied items and the support route with the actual vehicle reference. For new stock, retain the record with pre-delivery preparation. For used stock, also preserve available replacement or modification history. If the seller substitutes another unit, repeat the relevant identification and operating checks rather than carrying over the original car’s result.
Keep untested overseas services explicit in the handover description. A useful dealer promise names the task that was established and the arrangement needed to reproduce it. It should not grow into unrestricted compatibility with every phone, language or future software revision simply because the screen now looks familiar to the receiving customer.