Panda Used CarsBAO 5EXPEDITION DESK
Route menu
Source

Bao 5 Purchase Schedule: Version, Systems and Included Work

A candidate schedule prevents a model-level promise from replacing the agreed vehicle file. Keep physical facts, accepted condition and commercial obligations distinct.

Representative sandstone Bao 5-style SUV illustration, not the inspected vehicle
Representative Bao 5-style illustration; not the offered VIN, original-market configuration, condition evidence or a comparison vehicle.

Identify one actual offered vehicle

Record VIN, production identity, original market, steering side, mileage evidence and condition category, with the supporting sources. Preserve the name used in the applicable documents instead of relabelling the candidate as a local DENZA offer. The current sourcing guide distinguishes a proposed candidate from reserved inventory. Mark confirmed, seller-stated and unresolved facts individually. A trim nickname or current brochure does not establish installed battery, charging or suspension identity. If a consequential record conflicts with the offer, retain the conflicting evidence until it is resolved rather than silently choosing whichever description supports the expected specification.

Specify installed systems and useful functions

List the pack and charging identity, applicable suspension and assistance equipment, keys and practical cabin features that influence the purchase. Distinguish fitment, demonstrated operation and legitimate regional service access. The assistance-package value review prevents unsupported activation being described as a working included function. A claimed later upgrade needs its own applicable evidence and scope. Keep the buyer’s necessary features separate from optional preferences, including the accepted camping or towing configuration where relevant. Do not certify every capability from a dashboard photograph or an off-road badge. The schedule should make each important equipment claim traceable to the actual candidate and agreed evidence.

Attach the condition and history that were accepted

Retain the dated examination, relevant history, disclosed intervention, modifications and any equipment not tested. The inspection checklist provides the broader physical scope, while the battery-repair purchase review separates intervention evidence from current acceptance. Do not replace the detailed file with a statement that the whole vehicle is fully certified. Record accepted ordinary wear and unresolved conditions explicitly. If further diagnosis is required before commitment, state the necessary evidence rather than hiding it behind a standard disclaimer. A signature on a schedule does not extend an inspector’s conclusions beyond the safe scope and conditions under which the examination occurred.

Describe work by operation and completion evidence

List seller preparation, diagnosed correction, included replacements and buyer-accepted arrival tasks separately. Identify responsible providers, actual scope, exclusions and the appropriate evidence or recheck required. The inspection-led negotiation review keeps an allowance from being mistaken for completed work. Where intervention affects pack, thermal, hydraulic or assistance systems, the resulting file should reflect suitable affected-system findings rather than only a fresh exterior photograph. Do not demand a workshop certify unrelated vehicle systems simply because it performed one operation. Each accepted task should have a understandable completion boundary, so handover records can show what changed and what remains the buyer’s responsibility.

Separate vehicle acceptance from route obligations

Keep dated price, included origin tasks, transport-related scope, documentary responsibilities and destination conditions attributable to the actual proposed agreement. The export-from-China review keeps origin processing separate from registration eligibility abroad. Appropriate qualified professionals should review applicable route and commercial requirements where needed; this equipment schedule is not a universal legal contract. Verify contracting entities and beneficiary details independently. Avoid sending unnecessary identity files through a model enquiry. Physical inspection, documentary progress, payment and booking concern different responsibilities, and completion of one should not be used to claim that every other part of the route has already been accepted.

Keep changes visible until handover

Version the candidate schedule alongside proposals, findings and completion records. A replacement VIN requires renewed identity, system, condition and destination review. If work or movement changes the accepted condition, retain an appropriate pre-shipment reinspection and describe affected changes instead of overwriting the earlier report. The keys and account handover guide helps keep included access legitimate and attributable. An enquiry submission does not establish a purchase contract or availability guarantee. The final handover version should state what the buyer knowingly accepts, which tasks remain conditional and who is responsible under the actual agreed scope without certifying facts nobody established.

Compare the acceptance conditions

Identify
Tie market and installed systems to one actual VIN.
Describe
Keep working functions, examination limits and included operations traceable.
Control changes
Review substitutions, interventions and movement before accepting an updated file.

Buyer evidence checklist

  • Preserve actual document names and original-market identity.
  • Separate fitment from demonstrated and regional operation.
  • Attach condition findings and retained limitations.
  • State work scope and required completion evidence.
  • Verify commercial and beneficiary details independently.

Questions before you buy

Does this replace professional contract review?

No. It organises candidate facts and proposed scope; applicable terms need appropriate review.

Can another Bao 5 inherit the same schedule?

No. A substituted VIN requires its own identity, installed-system, condition and eligibility file.