Record the access items that travel with the car
Request a precise physical-key count and identify any other agreed access device. Demonstrate the applicable items on the actual vehicle through normal operation. A brochure package or another owner’s photograph does not show which items remain with a used candidate. Put missing or separately sourced items into the offer before deciding what the price covers.
The handover checklist keeps those items connected to the vehicle reference. For multiple cars, use individual lists when contents differ. An identical colour or trim description should not conceal a different key count. If replacement work is proposed, ask the appropriate provider to define its scope and the record supplied on completion.
Establish which account functions are actually offered
Ask which remote or account-dependent features exist on the particular GS4 and which the buyer needs. Do not assume all production periods and markets have the same arrangement. A menu or app demonstration can show a current context while leaving ownership and regional support unresolved. Name the required task instead of accepting full app access as a complete description.
The software and connected-service review identifies those dependencies. Keep ordinary physical access separate from optional digital convenience. Where a function needs provider registration, ask what evidence and legitimate user participation are required. The buying record should make clear whether the receiving dealer, final customer or another permitted user completes each stage.
Use supported prior-user release processes
For a used candidate, ask how previous associations or permissions are handled through the relevant provider. Record the process and its completed result separately. A reset of saved addresses, media or display preferences may be useful preparation without completing every service-side ownership change. Ask for evidence of the actual transfer task rather than treating an empty screen as sufficient confirmation.
Do not use a previous user’s password or a borrowed identity as an unexplained workaround. Let the account holder manage credentials privately and retain only necessary confirmation references. If the process cannot be completed for an essential requirement, leave it as an acceptance issue and assess alternatives before the vehicle is handed over.
Demonstrate the permitted receiving-user arrangement
Where supported access is available, test the agreed functions with the receiving user’s intended device and account. Preserve the vehicle, date, relevant software and network context while keeping sensitive screens out of the shared inspection record. A login should be followed by the specific tasks the buyer requires; it does not automatically establish every advertised function.
A source-market demonstration does not prove availability at the destination. Keep that limitation explicit if destination operation cannot be assessed beforehand. The phone-projection guide addresses another independent task. Working calls or map projection in the cabin should not be recorded as proof that a remote vehicle service has transferred or will remain available overseas.
The two-driver household review identifies the keys or account arrangement actually supplied for the household’s daily method.
Apply appropriate new and used preparation
For new stock, ask how first-user activation will be arranged and whether a preparation association already exists. For a used car, add prior-user release and disclosed key replacement history. The condition label cannot settle those answers. The final requirement can remain the same while the supporting evidence differs between the two buying routes.
Use the new and used criteria to connect these tasks with the agreed release point. If a missing item or account step is included in preparation, identify who completes it and what establishes completion. A promise to resolve access after arrival needs a defined outcome and responsibility to have useful meaning in a dealer offer.
Give the recipient a clear completion record
Retain the vehicle reference, delivered key count, demonstrated results, permitted provider steps and remaining limitations. Include the agreed support contact. Keep passwords and recovery information under the appropriate user’s control rather than embedding them in a shared vehicle report. The receiving dealer should be able to understand the handover without exposing another owner’s private data.
Repeat relevant checks if a substitute unit appears or the software and access arrangement changes during preparation. Preserve one result per vehicle when a batch differs. A concise completion record lets the buyer distinguish supplied physical access, established user control and services still dependent on provider or destination conditions, without turning the seller’s current login into an unlimited future-support promise.
NEXT / YOUR BUYING REQUEST
Make the requirement specific.
Send the accepted years, condition, destination and quantity. Identify the powertrain and features that must be confirmed before you select a candidate.
Discuss your GS4 requirement ↗