This file focuses on overseas software usability. Its approval points are screen language, phone integration, owner account, with destination and commercial checks kept visible.
Decide overseas software usability
Record interface languages, map region, voice language, Apple CarPlay or Android Auto support, Bluetooth, app pairing and OTA status on the actual vehicle. The 2026 Thai specification lists wireless phone integration, but this should not be assumed for earlier China PHEV trims.
Use the section outcome to decide whether screen language is confirmed or needs another document before the candidate advances.
Evidence for overseas software usability
Build a candidate record around Screen language and Phone integration; add dated media and documents for Owner account. Reject files assembled from different vehicles.
Save the supporting file under the candidate VIN and label how it establishes phone integration; do not rely on an unreferenced chat image.
Destination test for overseas software usability
Before choosing on overseas software usability, verify OTA region and Navigation maps in the destination, including any local registration or service limitation.
Record who will confirm ota region and by what date, because unresolved destination assumptions become expensive after loading.
Commercial control for overseas software usability
Value the car on functions that work locally. Do not pay a premium for remote climate, navigation or assisted-driving features unless access and legal usability are confirmed.
State the accepted result for ota region in the written approval record.
Apply overseas software usability to a candidate
Perform an offline-and-overseas usability test. Change the interface language, pair a local-format phone, verify calls and media, test smartphone projection, inspect map region, sign-out requirements and owner-account status, and observe which functions remain available without the original mobile application. Record the software version before accepting an update; an update can alter language, pairing or assisted-driving behaviour. Ask whether remote climate, digital key and charging scheduling depend on a Chinese or Thai phone number. The buyer should approve the vehicle based on durable local controls and confirmed integrations, treating unsupported cloud features as unavailable rather than promised future functionality.
Turn this field method into a dated worksheet and keep it with the candidate record so a later reviewer can reproduce the decision.
Approve or reject overseas software usability
Photograph the final software version and account state at handover. Give the buyer written notice of functions requiring an unavailable region, subscription or telephone number.
Retain the final outcome with the VIN file and reopen the review if the candidate, destination or commercial boundary changes.
Record the approval decision
Approve overseas software usability only when screen language, phone integration, owner account are supported by candidate-specific evidence and ota region, navigation maps, adas availability have an identified owner. Pause if the seller will not connect the VIN to the vehicle, documents or condition record, or if the destination answer depends only on another market's brochure. Record the precise missing test, quotation line or document. Resolve it before payment or reject the candidate; do not carry an undefined technical or commercial issue into shipping.
undefined
Buyer approval checklist
Use these fields as a candidate-specific decision record. Assign each unresolved item before approving payment or shipment.
- Screen language
- Phone integration
- Owner account
- OTA region
- Navigation maps
- ADAS availability
Primary references
Official Changan Thailand NEVO Q05 ↗Official NEVO Q05 specification sheet ↗Changan Q05 Software, Language and App Compatibility: buyer questions
Will the overseas mobile app work after export?
Do not assume it. Check account registration, phone-number rules, server region, prior-owner release and destination availability.
Are Apple CarPlay and Android Auto universal?
No. Verify the actual trim and software build; the 2026 Thai specification cannot prove an earlier China PHEV has them.
Should unavailable connected features affect price?
Yes. Value the car on functions that can be activated, supported and legally used in the destination.