List essential functions
Separate driving and cabin controls from connected conveniences such as remote access. Identify which functions affect acceptance. This avoids an undefined promise of full functionality. Record the required display language and phone-integration needs in the buying brief.
Request current demonstrations of relevant menus on the car and preserve its reference and visible software information. Another owner’s video or a different-market model is not proof. The specification guide keeps evidence connected to the offered configuration rather than the model name alone.
Identify regional dependencies
Ask whether a feature needs an account, subscription, mobile connection or region-specific service. Establish the permitted ownership-transfer process through the relevant provider. Demonstrating legitimate access should not require sharing a previous owner’s password or personal records.
If destination operation cannot be demonstrated, mark it unverified. A service working in China does not prove access on an overseas network. Separate offline controls from connected functions in the customer description. For an essential feature, obtain a supported route to use it or reconsider the candidate.
Plan keys and service access
List physical keys and separately agreed access devices. For used vehicles, ask how previous-owner access will be handled through supported processes. Record appropriate completion evidence without exposing personal data. A key count does not replace an account-transfer record.
Identify who will address software concerns and diagnostic work after delivery and what scope they have accepted. Do not promise updates, permanent connectivity or manufacturer support without applicable terms. Proposed unofficial modifications need separate assessment; they should not be hidden inside a routine vehicle offer.
Document what has been established
Give each required function a status: demonstrated, supported by applicable documentation or unverified. Include dependencies that affect acceptance. A changed vehicle or software state may require another review. This distinguishes general capability from the experience the receiving customer can expect.
Keep agreed access arrangements in the handover file. Retain individual records where a batch differs. The quotation should identify separately purchased support instead of implying every service is included. Dealers can then describe functions accurately and direct questions to the responsible party.
Example: a menu appears in a demonstration
A seller demonstrates an online function in the source market. The receiving dealer should record what was shown and ask which account, connection and regional conditions support it. Until destination operation is established, the demonstration supports only the observed context. The dealer can still describe verified offline functions separately. If the online feature is essential to the buyer, leave it as an acceptance condition. Do not turn a source-market demonstration into an unrestricted promise that every customer will have the same access.
Model reference: GAC’s AION i60 presentation and AION’s manufacturer overview. Model information gives context; the offered vehicle needs its own specification and condition evidence.