Inventory visible software
Record system version, languages, navigation provider, app-binding state, account region, mobile-key support and installed feature menus. Use dated screenshots linked to the VIN.
VERIFY / FIELD NOTE 10

CONNECTED DECISIONS
Connect software behaviour with the physical assistance-sensor and calibration record.
Record system version, languages, navigation provider, app-binding state, account region, mobile-key support and installed feature menus. Use dated screenshots linked to the VIN.
A camera, modem or NFC reader can remain installed while the associated service is unavailable. Ask what requires a Chinese number, identity, subscription, data service or manufacturer account. Reconcile all supplied keys and supported account access.
Capture current software and fault state before purchase. Do not install unofficial packages or reset accounts before the buyer understands recovery, warranty and cybersecurity consequences.
Verify sensors, calibration evidence, warning history and visible functions. Treat assistance as supervised technology; road, mapping and regulatory differences can limit operation in the destination.
Ensure essential driving, climate, charging and safety functions work without an overseas data connection. Record which conveniences may be lost and whether local service can diagnose the installed modules.
HANDOVER FILE
BUYER SCENARIO
Test the car after disconnecting the seller phone and any temporary hotspot. Confirm which driving, charging, climate and safety functions remain available. Record account binding, language, maps and current software before a reset. If an overseas app or OTA cannot be proven, value the vehicle on its dependable offline baseline rather than on a connected-service promise.
Stress the result by assuming “Preserve update history” reveals a conflict, “Qualify driver assistance” is delayed, or “Plan an offline baseline” changes before custody. Rework the cost, timing and stop condition using sensor and calibration report, official OTA record where available, offline-function test. A different VIN, propulsion route or installed configuration starts a new candidate record. The conclusion for Tai 7 Software, App and Region Compatibility must explain how dated system screenshots and account and region status support or limit the selected route.
CLOSE THE FILE
For Tai 7 Software, App and Region Compatibility, reconcile dated system screenshots, account and region status, sensor and calibration report, official OTA record where available, offline-function test. Mark each item verified, seller-stated, estimated or unresolved, and put a responsible person and expiry date beside the open work. Keep commercial rows separate so a change in one assumption does not silently rewrite the whole conclusion.
Immediately before payment or handover, repeat “Inventory visible software” and confirm that the candidate still matches the reviewed record. Preserve the VIN, odometer, visible condition, keys, documents and relevant energy state. If the vehicle or a material specification changes, close this file and begin a new one.
OFFICIAL REFERENCE BOUNDARY
Fangchengbao may revise equipment, software and specifications. Match official information to the production record and actual installed hardware. Review the official Fangchengbao Tai 7 reference, then verify the candidate and destination independently.