CHAPTER 1

Name what genuinely must match

Ask whether the requirement concerns a specific function, model period, appearance or customer assignment. These are separate fields. The period identity review prevents registration and production differences being hidden inside a uniform stock label.

Colour flexibility does not authorise changed systems or history automatically. Retain common essentials and permitted variation explicitly. A dealer should understand how each candidate serves the brief before the order total is presented as the accepted proposition.

CHAPTER 2

Describe useful differences per unit

The dated specification comparison keeps familiar trim names in context. An older and newer car may meet common essentials through different supported arrangements, or differ on a mandatory function. Establish that rather than relying on one model-family equipment list.

Assign each accepted unit its own retail description and reference. A premium example's photographs should not illustrate the whole group's supplied equipment. A lower amount can reflect an accepted difference, but not an unidentified feature or a condition gap hidden beneath a blended total.

CHAPTER 3

Repeat evidence rather than conclusions

The individual findings framework applies appropriate scope to each used car, with new-status and delivery checks for new proposals. One positive report cannot establish the order. Matching trims may still differ through later work or condition.

Keep open tasks and inaccessible areas per unit. Avoid all-ready language unless the actual records support the stated scope. The receiving dealer needs to distinguish established configuration, completed work and unconfirmed items without reconstructing a shared message history.

CHAPTER 4

Keep amounts and substitution visible

Use the scope reconciliation guide for currency, transfer stage, supplied items and individual preparation. A batch average can conceal one material unresolved task. Shared services should identify their scope rather than being allocated ambiguously.

The remote file review carries final references and readiness forward. Substitutes need actual records and visible approval where essentials change. Equal colour or amount cannot establish an equivalent period, function or condition proposition.

CHAPTER 5

A common function across differing periods

Suppose the dealer accepts several model periods but requires one supported phone and passenger arrangement on each. Record that requirement per car. A matching badge does not establish the function, and a different colour need not be rejected when expressly permitted.

Before movement, reconcile final units and pending release conditions. Do not carry another car's inspection or package media onto a substitute. Retain the accepted differences so stock variety remains understandable and an apparent uniform order cannot conceal meaningful specification or individual-condition variation.

Choose the next action

Finding or requirementPurchase response
Consistency has a specific purposeSeparate common mandatory functions from permitted cosmetic or period differences.
One example represents the groupObtain unit-level configuration and appropriate findings before repeating a shared claim.
Substitute changes an essentialReview fresh evidence and record explicit acceptance before including it in the final count.

Evidence to keep with the decision

  1. Write common essential requirements and permitted differences before asking for multiple L6 candidates. Keep the accepted production periods explicit rather than assuming a shared model or translated trim name establishes interchangeable equipment; distinguish a useful mixed-period order from an uncontrolled collection of unlike propositions.
  2. Retain a per-unit identity and original configuration record, linking each car to its individual quotation and media. A convincing first example cannot approve the remaining batch, and a generic representative photograph should not substitute for the evidence needed to establish the actual equipment of each offered unit.
  3. Keep new-or-used status, disclosed history and assessment scope separate for every candidate. A consistent order total does not demonstrate consistent condition; record supported findings and gaps rather than allowing one complete inspection or reassuring seller statement to cover cars that have not been assessed equivalently.
  4. Identify any function or supplied item that differs and the customer assignment affected by that difference. Do not bury variation in a batch description, and do not assume optional equipment is unimportant because another buyer accepted it; preserve the receiving customer's actual minimum specification and accepted alternatives.
  5. Align amount, preparation and handover stage per unit while retaining the order-level scope. A batch saving may include different deliverables or incomplete work, so distinguish confirmed inclusion from pending preparation rather than crediting every quoted car with an identical ready-to-handover condition and supplied equipment set.
  6. Record accepted deviations and substitutions with the relevant customer approval before replacing a unit. The order's broad period flexibility does not remove individual acceptance; any new candidate must enter the same identity, configuration, condition and commercial review rather than inheriting approval from the discarded car.

Questions buyers ask

Does matching trim prove matching equipment?

No. Period, build, later work and condition require individual verification.

Can an average amount describe the whole order?

Not fully. Keep per-unit work and accepted differences visible.

Dated model references: 2024 Li L6 launch, 2025 update, and July 2026 new L6 announcement. Confirm the specification and condition of the individual offered vehicle.

BRING THE REQUIREMENT INTO YOUR BRIEF

Discuss a suitable Li L6 offer.

Share destination, quantity, new-or-used preference and the requirements that determine acceptance. Include a year or version preference where it matters; actual availability and purchase terms need separate confirmation.

Prepare your sourcing request ↗