For how to compare suppliers and validate a sample in the first place, start with how to compare, test and order from a Chinese supplier. This page is about what happens once the model is chosen and the quantity is a fleet.
Five things that only appear at scale
| Issue | Why it only shows up in volume |
|---|---|
| Batch consistency | A pilot uses one batch. A fleet uses several, built weeks apart, potentially with component substitutions. |
| Firmware drift | Later batches may ship with newer firmware that behaves differently from the version you validated. |
| Spares and RMA | At ten units a failure is an inconvenience. At a thousand it is a process that needs agreeing in advance. |
| Staged rollout | Fleets are fitted over months. The model has to still exist, and still behave the same, in month six. |
| Import documentation | Certification, declarations and product marking have to satisfy customs for the actual quantity and model shipped. |
The most expensive fleet sourcing mistake is not choosing the wrong device. It is validating one device and receiving a slightly different one three months later.
Freezing the specification
Once a sample has been validated, the specification should be written down and agreed rather than left as a shared assumption. In practice that means recording:
- The exact model and variant, including any hardware options.
- The firmware version validated, and what happens if the supplier wants to change it.
- The default configuration and reporting profile shipped on the units.
- The protocol and reporting endpoint the units are set to on arrival.
Without that, batch two arrives configured differently and the fitters discover it on a vehicle. The validation method itself is described in sample validation.
Spares, failures and RMA
Some proportion of any electronics batch fails. What matters is what has been agreed before it happens:
- Spare stock. Holding a small percentage locally is usually cheaper than air-freighting single replacements later.
- DOA handling. Units dead on arrival should be distinguishable from units that failed in service, with a route for each.
- Warranty start point. Ours runs 12 months from the shipment date shown on the commercial invoice — a date both sides can verify from the same document, which matters when units are fitted months after arrival.
- Diagnosis. Whether a suspected failure is hardware, installation or configuration is worth establishing before anything is shipped back.
Import and documentation
Certification marks are issued per model and variant. For a fleet quantity, confirm that the documents cover the specific model and the destination market, and that product marking matches what customs expects. Certification documents are available for selected models; where something cannot be evidenced, we say so rather than assuming catalogue-wide coverage.
Commercial terms at fleet scale
| Term | How we handle it |
|---|---|
| Minimum order | Custom orders from 100 units; samples and validation batches handled separately so testing never blocks a rollout. |
| Lead time | Confirmed by model, configuration and quantity — planned around staged rollouts rather than quoted as one number. |
| Warranty | 12-month limited warranty from the shipment date on the commercial invoice. |
| Platform | No lock-in. Units can be pre-configured to report to your endpoint where the model supports it. |
| Contract | No multi-year commitment or automatic renewal attached to buying hardware. |
The short version
At fleet scale, the supplier's job is consistency rather than price. Validate once, freeze the specification in writing, agree spares and RMA before the first batch, and confirm documentation against the actual model and market.
Frequently asked questions
What changes when sourcing for a whole fleet?
Batch consistency, firmware control, spares and RMA, staged rollout timing and import documentation. The device comparison itself does not change — everything after it does.
How do we stop later batches behaving differently?
Freeze the specification after validation: exact model and variant, firmware version, default configuration and reporting endpoint, all written down and agreed rather than assumed.
Should we hold spare units?
Usually yes. A small percentage held locally is cheaper and faster than shipping single replacements internationally each time a unit fails.
When does the warranty start on a fleet order?
Ours runs 12 months from the shipment date shown on the commercial invoice. Using an invoice date matters when units sit in stock before being fitted.
Can units arrive pre-configured?
Where the model supports it, units can ship already pointed at your endpoint with your reporting profile, which removes a step from every installation.
What documentation do we need to import?
Certification appropriate to the specific model and destination market, plus product marking that matches. Coverage is confirmed per model rather than claimed catalogue-wide.
What is the minimum order quantity?
Custom orders start from 100 units. Samples and small validation batches are handled separately.
How long is the lead time for a fleet quantity?
Confirmed by model, configuration and quantity. For staged rollouts it is planned wave by wave rather than quoted as a single figure.
Is a LEXUNYU platform subscription required?
No. LEXUNYU does not own or operate a tracking platform, and no LEXUNYU platform subscription is required. A customer's existing or third-party platform route must be checked per model for receiver support, field mapping and permissions.
What if a device turns out not to suit part of the fleet?
We would rather find that in validation than after a fleet quantity has shipped. Device categories should follow the fleet's power, installation, environment and required fields; identifying those differences early supports a staged validation plan.