Fleet and dealer procurement from China
Programme buying is a different exercise from buying a single unit. Repeatability, specification consistency, replenishment rhythm and after-sales planning matter more than the price of any individual vehicle. This page covers how dealers, fleets and project buyers should structure that.
- The specification set that will be repeated, not the individual unit.
- Replenishment rhythm and the shipping cadence that supports it.
- How much variety the programme can absorb before operations break down.
- Service, parts and warranty expectations in the destination market.
- Payment terms that scale with volume rather than per-order deposits.
The three shapes of volume demand
Dealer stock, operational fleets and project tenders each have different constraints. The sourcing plan should follow the constraint, not the unit count.
Dealer stock programmes
Fast-moving models replenished on a rhythm, chosen for turnover speed rather than specification depth.
Open dealer stock unitsFleet and taxi supply
Consistent specification, durable service profile and predictable maintenance cost across the fleet.
Open taxi and ride-hailing picksTender and project supply
Delivery to a fixed specification and date, where slippage is a contractual problem rather than a commercial nuisance.
Open fleet project supplyBulk order units
Larger consolidated orders where the loading plan and documentation discipline decide success.
Open bulk order unitsRepeat replenishment
A cadence of smaller shipments that keeps stock turning without locking up capital.
Open source on demandService and parts planning
Deciding the parts path before the first delivery, since it governs resale confidence later.
Review verified suppliersWhat to define before the first order
- The repeat specification, written so it can be quoted consistently.
- The replenishment rhythm and the shipping method that supports it.
- The acceptable substitution rules when a model is unavailable.
- The inspection regime applied across the whole programme.
- The payment structure at programme volume.
What breaks programmes in practice
- Specifications that drift between shipments, which complicates local registration.
- Too many models in one programme, which multiplies parts and training requirements.
- Replenishment rhythm that ignores sailing frequency.
- Inspection that is tightened only after a problem appears.
- Documentation prepared per shipment without a consistent template.
Programme mistakes that show up later
Optimising each shipment separately
A programme wins on consistency across shipments. Chasing the cheapest unit each time destroys specification stability.
Ignoring the parts path
Fleet buyers judge vehicles by downtime. Without a credible parts plan, resale and renewal both suffer.
Under-planning the documentation
At volume, inconsistent document sets across shipments create registration problems that are expensive to unwind.
Fleet and dealer procurement questions
Structure the programme before scaling
Send the target specification, volume range and destination. We will tell you what can be repeated consistently and what cannot.