Define the customer's actual access need
Ask whether the buyer needs phone-based unlocking, another specified function or simply convenient everyday access. Identify the phone model and operating environment without requesting account passwords or verification codes. The term digital key can describe different implementations. Retain the manufacturer's wording for the actual configuration instead of assuming another market's system works the same way.
Use the connected-function guide to separate installed equipment from provider and region-dependent services. A screen menu can show a feature without confirming the customer's eligibility. Keep the purchase brief practical: specify the function, expected destination use and evidence required, while allowing a physical-key-only alternative if the customer expressly accepts it.
Establish compatible equipment and process
Request the applicable instructions and provider confirmation for the offered specification and intended user arrangement. Compatibility may involve more than a phone brand, so do not treat a broad Android or iPhone description as sufficient. Avoid transferring instructions from a foreign-market product page to an unidentified China-market head unit or access system.
Any demonstration should use an authorised account and an appropriate ordinary sequence. Record what was shown and which conditions remain untested. A seller's successful demonstration under their own account does not automatically establish the receiving owner's access after transfer. Keep setup, transfer and destination-use questions independent until the responsible provider confirms the applicable process.
Protect access during ownership transfer
Ask how previous users, shared permissions and personal data will be handled through the supported transfer procedure. Do not retain the seller's account as a workaround or arrange access through an unverified intermediary. The buyer should know who is responsible for completing each step and what evidence will be retained without exposing sensitive credentials.
For used cars, prior account status needs its own review. For new proposals, confirm how the actual customer would be enrolled rather than assuming an unregistered car has no setup questions. The handover checklist keeps access arrangements alongside supplied items and records. If the process cannot be confirmed, the feature remains unresolved; it should not be presented as a completed benefit in the dealer's offer.
Keep physical keys and fallback separate
Count the actual physical keys and demonstrate their normal supported functions. Do not describe a phone demonstration as proof that all keys are supplied or that the buyer can recover from a failed setup. Ask the appropriate provider about any missing key, supported replacement and resulting verification. A generic blank key price does not represent a completed remedy.
The supplied-item inventory provides a place to retain keys alongside other agreed accessories. Confirm the relevant emergency-access instructions for the actual car rather than inventing a universal fallback. No buyer should need to share passwords in the initial enquiry. Agree a suitable process later when a transaction genuinely requires additional access information.
If the physical inventory contains only one key, the one-key replacement review defines the separate supported remedy and its completed purchase scope.
Decide how much value remains after uncertainty
A customer who expressly wants supported phone access may reject an unresolved transfer process even if the car is otherwise attractive. Another may accept the vehicle on a physical-key-only basis, provided the digital function is not advertised as confirmed. Compare that proposition with a supported alternative before paying a technology premium.
Write the accepted access arrangement into the final record: keys supplied, demonstrated functions, provider confirmation and remaining limitations. If a substitute candidate has a different system, repeat the review. Matching screens or trim labels do not establish matching access support. The decision should preserve secure, understandable ownership access rather than depend on an unconfirmed convenience promise.
A practical shortlist example
Consider a buyer who sees the seller unlock the car with a phone and assumes the feature will work after export. Retain the demonstration, but request the supported receiving-user setup and transfer answer before adding that benefit to the accepted specification. The seller's account, phone and location may not represent the customer's eventual arrangement.
If the customer is happy with physical keys alone, state that basis explicitly and remove any unconfirmed phone-access promise. If phone access is mandatory, seek a candidate and process whose support can be established. In both cases, record supplied physical keys separately. This keeps a convenience preference from becoming an unclear ownership-access dependency or a reason to share sensitive credentials through an ordinary sourcing conversation.
Compare the decision
| Finding or requirement | Useful next decision |
|---|---|
| Seller can demonstrate phone access | Record that observation but separately confirm the receiving user's eligibility and supported transfer procedure. |
| Physical key supply is incomplete | Obtain a supported replacement scope and retain the unresolved item before acceptance. |
| Destination eligibility is unknown | Leave the digital feature unconfirmed or compare an explicitly accepted physical-key-only alternative. |
Buyer questions
Does a digital-key menu prove my phone will work?
No. Vehicle configuration, phone eligibility, provider conditions and the transfer process require their own confirmation.
Should I provide login codes with the enquiry?
No. Initial buying requirements should not contain passwords or verification codes. Use only an appropriate authorised setup process.
