Establish what actually comes with the candidate
Inventory the supplied access items and demonstrate relevant normal functions safely. Do not assume every original package or version supplies the same arrangement. A photograph of similar objects cannot establish that each is operational for this vehicle.
The supplied-item record keeps count and functions connected to the candidate. New proposals still need matching equipment and delivery review; used offers need actual supply and any disclosed limitation. Retain missing or incomplete items before calling the proposition complete.
Obtain an appropriate replacement answer
Ask a suitable provider for legitimate supply, setup and verification scope for the actual configuration. A generic component listing does not establish compatibility or finished function. Necessary ownership authorisation should use the relevant process rather than ordinary message assumptions.
Keep component amount, provider work and required checks distinguishable. Avoid a universal key cost across every i60 application. Receiving-location support can change practicality, so obtain a specific answer. Do not collect passwords or verification codes through the initial sourcing enquiry.
Separate app and account access
The account transfer guide handles supported receiving-user setup separately. A seller's app operation cannot establish physical key count, previous-user handling or every fallback method. Retain applicable instructions and provider answers rather than assuming equivalence.
Do not arrange unofficial access changes or describe a guessed reset as a guaranteed remedy. If an essential supply or transfer question remains unconfirmed, keep it pending. A buyer may accept a narrower arrangement only when the limitation and useful supported functions are explicit.
Compare finished amounts and release conditions
Use the scope comparison guide to put supplied items and supported remedies beside the vehicle amount. A cheaper offer may leave access work unresolved. A component-only allowance should not be entered as a completed solution.
If a seller agrees to supply another item before movement, retain the task as pending until demonstrated. The remote evidence checklist helps close it through the appropriate record. Do not increase the retail inventory because the commercial discussion contains a future intention.
A one-item offer with a replacement promise
Suppose the candidate's supported inventory is incomplete against the buyer's requirement, while the seller promises completion. Ask for the actual identified remedy and verification responsibility before comparing the finished amount with another complete offer. Equal-looking objects or a working app do not answer that supply question.
At handover, reconcile items with each unit and supported functions through the relevant process. A substitute needs its own inventory, and a batch should not rely on one shared accessory claim. The dealer's final description must follow actual supply and completed work, keeping any customer-accepted limitation distinct from an unconfirmed future remedy.
Choose the next action
| Finding or requirement | Purchase response |
|---|---|
| Supply is incomplete | Record actual count and required functions, obtaining a supported remedy if the buyer requires completion. |
| Quote lists only a component | Clarify legitimate setup and verification for the identified system before budgeting finished work. |
| App use is offered as equivalence | Review account access and physical inventory separately through their applicable supported processes. |
Evidence to keep with the decision
- Inventory the actual supplied access items and relevant supported functions against the vehicle reference, noting missing or incomplete operation instead of assuming every original version has the same package or that similar objects are functional keys.
- Obtain a legitimate replacement answer for the identified system, including suitable supply, required setup and verification with the responsible provider rather than treating a generic component listing or a guessed reset as the complete remedy.
- Retain appropriate authorisation and necessary records through the relevant process, keeping passwords and codes out of ordinary sourcing enquiries instead of using unofficial access changes or another person's account to bridge an unresolved setup question.
- Keep physical inventory, supported app eligibility and receiving-user transfer independent, preserving applicable instructions and any fallback question rather than presenting one working demonstration as proof that all required access accompanies the accepted vehicle.
- Compare amount and supply at an aligned delivery stage, leaving a promised additional item pending until its actual functions and completion are established instead of increasing the retail count from a supplier's intention or component allowance.
- Reconcile supplied access and finished work individually at handover, requesting fresh inventory for substitutes and preserving explicit accepted limitations so a shared accessory assurance or equal model name cannot establish complete supply across a batch.
Questions buyers ask
Does app operation prove complete key supply?
No. Account eligibility, physical items and appropriate transfer are separate requirements.
Can a component amount represent completed replacement?
Not alone. Suitable supply, setup, support and verification need confirmation.
Model reference: GAC’s AION i60 presentation and AION’s manufacturer overview. Model information gives context; the offered vehicle needs its own specification and condition evidence.