Count the access items supplied
Request an itemised list of keys and other agreed access devices tied to the vehicle. Demonstrate the applicable normal functions with the actual items supplied. A brochure may describe an original package while a used car no longer includes every item. A new-stock label also leaves the delivery contents to be confirmed.
Connect missing or replacement items with the commercial offer. Ask the appropriate provider to describe proposed replacement work and its completion evidence. The buying record should tell the receiving dealer what arrives and what has been checked, without requiring assumptions based on a single key photograph.
Specify which app functions matter
Ask which connected or app functions the particular car supports and which are required by the customer. Identify the provider and relevant market arrangement. A promotional app description or a visible menu cannot establish activation rights, the receiving user’s eligibility or operation with every overseas network.
The ownership support review separates those dependencies from cabin software. For stock that will be resold, identify both the importer’s preparation stage and the final customer’s setup. A temporary demonstration arrangement should not silently become the promised permanent service route. Keep the intended recipient and accepted outcome explicit.
Confirm the prior-user release process
For a used candidate, obtain the permitted provider process for removing or changing relevant associations. Ask for evidence of completed steps rather than accepting instructions as proof that release already occurred. Do not use a previous owner’s password as the new buyer’s long-term access arrangement.
Removing saved cabin information can address privacy without resolving provider-side ownership records. The software version check concerns a separate task and cannot certify account transfer. If legitimate receiving-user control remains unresolved, record it as an acceptance issue before describing the vehicle as ready for the customer.
Demonstrate the receiving arrangement
Where supported, let the appropriate receiving user enter their own authentication information and test the agreed permitted functions. Keep private credentials out of shared screenshots. Record the vehicle, date and relevant service context so the result remains understandable to the dealer preparing the final handover.
Source-market success does not establish destination availability. Ask which network, registration or subscription conditions still apply overseas. A cabin phone connection is also different from remote vehicle access. Keep each essential task visible rather than reporting that the app works when only a sign-in screen or seller-controlled demonstration was observed.
Handle new and used evidence appropriately
For new stock, clarify first-user setup and whether an existing preparation association must be changed. For a used car, add previous-user release and disclosed key replacement history. These are different evidence routes to the same receiving-user requirement, and neither can be resolved by the model year alone.
Use the condition buying guide alongside this access record. If a service step is deferred until arrival, identify the responsible provider and the condition that must be met. A vague promise to sort the app later gives the receiving dealer little basis for answering a customer who requires the function immediately.
Retain a private and useful handover record
Preserve supplied items, completed legitimate provider steps, demonstrated functions and remaining limitations. Leave account passwords and recovery information controlled by the appropriate user. A general vehicle report should not become a repository for personal access material. Include the agreed support contact and the date of the result.
The final handover guide ties this evidence to the delivered unit. Keep separate records when access items or setup stages differ across an order. A substituted car requires its own review; one successful demonstration cannot certify every ROX 01 carrying the same version description.
BRING TO YOUR ENQUIRY
Three useful starting points.
- Supplied key list and demonstrations
- Legitimate prior-user release and receiving-user process
- Supported functions and unverified destination dependencies