A screen, camera or connected-car badge does not establish that every advertised function will operate overseas. For a China-market EV order, list the functions you depend on, ask for vehicle-specific evidence, and keep account and destination support requirements separate from the physical equipment.
Divide essential functions into clear questions
Start with what the car must do for daily use: keys, climate control, charging, basic driving displays and the interface you can use. Add navigation, remote control, connected apps and updates as distinct requirements. Ask which functions need an account, network connection or regional service.
This is an evidence checklist, not a claim that every China vehicle loses or retains the same features abroad. Market, production year, trim, software version and the offered support arrangement can differ. Record those details for the actual car.
| Function area | Evidence to request |
|---|---|
| Interface | Available languages and demonstration on the supplied version |
| Navigation | Maps, destination coverage and operation requirements |
| Mobile app | Supported account, region, device and remote functions |
| Connectivity | Network or subscription needs and support at destination |
| Updates | Supported update method, account needs and assistance |
| Driver assistance | Delivered functions, operating conditions and driver responsibility |
| Physical keys | Supplied keys, cards and essential access without a phone |
Check the interface on the exact supplied software
Request images or a demonstration of the current language menus, instrument display and important controls. Ask how a future update could affect the chosen settings and which party provides support. A brochure showing English marketing text does not prove the car’s interface language.
For a Stelato S9 or Luxeed R7 enquiry, use the factory equipment record to identify the physical cabin and assistance package, then ask separate questions about operation outside China.
Review account transfer without sharing credentials
Ask how ownership and necessary accounts will be set up through the manufacturer’s supported process. Identify the responsible party and what the buyer must complete. Never put personal passwords or one-time codes into a public enquiry or routine vehicle document.
Keep physical keys and required access cards in the handover record. Ask which basic functions remain available without a mobile app or network connection, and request a supported explanation for the supplied vehicle. The phone app should not be the only access plan you understand.
Verify navigation, apps and connectivity separately
List the countries and functions that matter to the buyer. Ask about map coverage, app region, mobile-network requirements, subscriptions and the support process. Seek a written answer for the actual destination rather than a general statement that the car is “international”.
If a function is unavailable or uncertain, record that clearly and decide whether the vehicle still meets the requirement. Avoid unsupported modifications or promises about future software. The quote should distinguish demonstrated capability, a supported arrangement and a remaining open question.
Treat driver assistance as a separate delivered feature
Confirm the assistance hardware and software version against the exact trim. Ask which functions are enabled for the supplied car and what the manufacturer’s operating conditions require. Driver assistance needs an attentive driver; hardware presence is not a promise of autonomous driving or destination availability.
Record the essential safety and basic driving controls separately from optional connected conveniences. When comparing two versions, distinguish a different sensor package from a claim about regional software operation.
Document the update and support arrangement
Ask who helps with supported updates, faults or account questions after delivery. Identify contact scope, language and any separately charged service. Review the offered warranty and software support wording with the vehicle quote rather than importing a domestic brochure promise.
At inspection and handover, record the software version, essential function checks, supplied keys and agreed support contacts. Use this record if the version changes or a function behaves differently after delivery. Keep it alongside the vehicle purchase and handover checklist.
Frequently asked questions
Does a global-looking screen prove overseas compatibility?
No. Ask about the exact supplied software, accounts, connectivity and destination operation of the functions you need.
Should I include passwords in an export enquiry?
No. Ask about the supported setup process and complete credential steps through the appropriate private manufacturer flow.
Can assistance hardware prove that a feature will work abroad?
It identifies equipment, not every enabled regional function. Confirm delivered software, operating conditions and driver responsibility.
What should be recorded before shipment?
Software version, demonstrated essential functions, available interface languages, supplied keys and the written support arrangement.
Related buying checks
To turn this comparison into an acceptance record, use the VIN-by-VIN inspection and handover plan. Keep the accepted specification, inspection findings, delivered accessories and handover evidence with the same allocated VIN.
Send a useful sourcing enquiry
Include your destination country and port, intended use, exact model and configuration, quantity, colour preferences and requested delivery scope. Identify any feature or service that is essential to your order. Send the requirements for an itemized vehicle export quotation →
References: Manufacturer trim and assistance hardware reference; Manufacturer cabin and configuration reference. Manufacturer configurations and carrier requirements should be checked for the exact order and booking.