Define a Q05 purchase by VIN, BEV or PHEV identity, original market, included equipment, inspection acceptance and handover scope.
Verify parties and the complete vehicle identity
Record the contracting entity independently from a marketplace listing contact, then reconcile VIN, production, original market, steering and BEV or PHEV designation. The model identity file prevents an ambiguous Q05 name from concealing a different system. Keep applicable specification documents attached to the accepted schedule. A substitute vehicle requires explicit review, not a general promise of the same model. Clarify whether the offer is existing identified stock or a conditional sourcing arrangement. The record should make it possible to compare the eventual handover with a definite car rather than rely on a conversation that used abbreviated names and representative photographs.
Describe included equipment and confirmed functions
List actual battery and factory-equipment identity, keys, charging hardware, manuals and removable items included in the amount. The charger-bundle review separates equipment from installation claims. Name any aftermarket additions and excluded accessories. Essential language, phone, app or assistance functions need their own supported evidence through the software file. Do not write promised future updates as currently installed equipment. Photographs help but may not identify small components or services that do not transfer. Clarify exceptions and untested functions so the agreement does not silently award confirmed value to every feature the advertisement mentioned.
Define inspection and preparation acceptance
Identify the assessor, agreed scope, access and evidence required before commercial acceptance. The whole-vehicle inspection file sets the technical starting brief; the agreement must state how findings and defined preparation are handled. New cars need delivery-condition checks, while used cars add actual history and system condition. Keep seller representations separate from observations, diagnosis and remaining limitations. Do not require an inspection to guarantee no future fault. Where work is agreed, name the intended supported result, responsible party and reassessment evidence rather than using an open-ended promise to make everything good before delivery.
Keep delivery and document responsibilities explicit
State the named delivery basis, movement assumptions, inspection and preparation inclusions, document responsibilities and relevant exclusions. Use the FOB-versus-CIF review to expose the scope behind trade-term shorthand. Carrier acceptance depends on the actual energy system and prepared configuration, not a generic SUV quotation. Destination taxes, compliance and registration require qualified local confirmation. Do not present a port-delivered price as a road-ready local total. Have appropriate professionals review risk, insurance and the enforceable wording where these affect the transaction. A useful schedule names what evidence and responsibility follows the vehicle at each stage.
Verify payment instructions independently
Confirm beneficiary details against the contracting arrangement through an independently established route, especially when instructions change. Do not send passwords, payment-card data or unnecessary identity files through an initial enquiry form. A clear equipment schedule is not proof that an account is legitimate. Record payment stages and the evidence required using appropriate advice. Preserve authorised changes in a coherent transaction record rather than relying on messages with unclear authority. If the VIN or work scope changes, reconcile acceptance and price before the next stage. An enquiry submission or availability discussion does not itself reserve a car or constitute the buyer’s signed purchase agreement.
Reconcile final handover with the accepted schedule
Use the pre-shipment reinspection to compare identity, equipment, agreed preparation, keys and condition after storage and movement. Record discrepancies and follow the actual agreed resolution process before release where possible. Save the final evidence for the arrival review. A neat schedule can reduce ambiguity but does not guarantee enforceability or compensation in every jurisdiction. Keep professional advice and the actual agreement separate from this general purchasing method. The objective is one clearly identified vehicle with understandable responsibilities, not a broad model-name promise that can change silently between shortlist, payment and shipment.
Buyer approval checklist
Use these fields as a candidate-specific decision record. Assign each unresolved item before approving payment or shipment.
- Verified parties and full VIN-specific identity
- Confirmed equipment and exclusions
- Inspection and preparation acceptance process
- Named delivery and document responsibilities
- Independent payment verification and final handover record
Primary references
ICC international sale-contract framework ↗Changan Q05 Purchase Contract: Generation and Equipment: buyer questions
Is Q05 automatic with a year enough for the agreement?
No. Name BEV or PHEV, original market, steering, actual configuration and included equipment so substitution or ambiguous specification is visible.
Does this guide guarantee a remedy for mismatched equipment?
No. Remedies depend on the signed agreement and applicable law. Obtain appropriate professional advice for the actual parties and jurisdiction.

