Panda Used CarsBAO 5EXPEDITION DESK
Route menu
FIELD NOTE 19 / ENERGY

Separate Bao 5 Hardware from Regional Services

A function visible in China may rely on an account, SIM, map licence, cloud service, geofence or local regulation. Export buyers should test physical hardware and then classify each digital feature by its overseas dependency.

Representative sandstone Bao 5-style plug-in hybrid off-road SUV on a high-desert gravel route
Representative vehicle; apply every check to the selected VIN.

The decision on separate bao 5 hardware from regional services stays attached to one selected VIN. Record record the software baseline, test language and input and map account dependencies before comparing routes; keep check connectivity, qualify driver assistance and plan offline operation visible through quotation and handover.

01CHECKPOINT

Record the software baseline

Photograph system, navigation and assistance version screens and note the test date. Updates can change menus or behaviour, so a listing video is not permanent evidence.

Evidence threshold. For record the software baseline, Save version screens before and after preparation. Link record the software baseline to the VIN and source date. Name who checked record the software baseline, and retain enough detail for another reviewer to reproduce the result.

02CHECKPOINT

Test language and input

Check interface, voice, keyboard, units and warning-message language. Partial English support may not cover diagnostics, maps or owner guidance.

Failure condition. For test language and input, List which screens remain Chinese-only. If test language and input stays open, specify whether to reject, reprice or reinspect. Do not treat seller silence about test language and input as supporting evidence.

03CHECKPOINT

Map account dependencies

Identify functions requiring owner registration, China phone numbers, identity verification or subscriptions. Do not promise account transfer without a confirmed process.

Destination effect. Classify ownership transfer as confirmed or open. Ask the destination adviser whether map account dependencies changes customs or registration. Check charging, road use and service separately when map account dependencies affects them, then retain the dated response.

04CHECKPOINT

Check connectivity

Review SIM, Wi-Fi, Bluetooth, phone integration and hotspot behaviour. Network bands and embedded services may differ outside China.

Cost effect. Test local-phone functions separately from cloud services. Price check connectivity as its own inspection or preparation line. If check connectivity creates compliance risk, show the contingency clearly rather than burying it in a general discount.

05CHECKPOINT

Qualify driver assistance

Installed sensors do not guarantee every assisted-driving function abroad. Mapping, regulation, road design and software region can affect availability.

Custody check. Describe verified functions without implying autonomy. Reconfirm qualify driver assistance at each custody transfer. Seller, inspector, transporter and port records for qualify driver assistance should remain dated and tied to the same VIN.

06CHECKPOINT

Plan offline operation

Core vehicle use should not depend on an assumed overseas cloud connection. Prepare charging, navigation, keys, manuals and service options for limited connectivity.

Replacement rule. Give the buyer a fallback for each essential task. A substitute must repeat every check for plan offline operation. Similar colour, mileage or trim cannot transfer the previous VIN’s conclusion about plan offline operation to another vehicle.

DECISION LOG

Close the file without hiding open items.

Close “Separate Bao 5 Hardware from Regional Services” with the candidate VIN, source date and the evidence used for record the software baseline and test language and input. Name rejected alternatives and unresolved questions, then assign responsibility for qualify driver assistance and plan offline operation. A changed vehicle or destination reopens the affected checks.

  • Record the software baseline: confirmed / open / not applicable
  • Test language and input: confirmed / open / not applicable
  • Map account dependencies: confirmed / open / not applicable
  • Check connectivity: confirmed / open / not applicable
  • Qualify driver assistance: confirmed / open / not applicable
  • Plan offline operation: confirmed / open / not applicable

Three questions before commitment

What closes “Record the software baseline”?

Save version screens before and after preparation. For record the software baseline, attach a dated source and candidate identifier, then name who produced or verified the record. A listing label is not enough to close this checkpoint.

What closes “Test language and input”?

List which screens remain Chinese-only. Mark test language and input as confirmed only when the supporting record matches the VIN and route assumptions. Otherwise show the item as open in the quotation or inspection scope.

What closes “Map account dependencies”?

Classify ownership transfer as confirmed or open. If records about map account dependencies conflict, preserve both sources and ask the responsible party to resolve the difference before deposit, preparation or shipping instructions.