The short answer
This note does not quote an industry average, because a reliable one does not exist: sources define defects differently, count at different points, and mix models of very different complexity. A basic single-channel 1080P unit and a 4K front-and-rear GPS set with WiFi do not have comparable risk. Instead of a number, a buyer gets more from understanding the drivers: the design, the components, the line discipline, the testing, the packing and the shipping. Most of those can be influenced before the order is placed, through the specification, sample approval, inspection brief and written terms. The desk helps set them up on each program.
What drives defects
| Driver | How it creates defects | What the buyer controls |
|---|---|---|
| Model complexity | More channels and radios mean more points of failure | Choose only the options the market needs |
| Component choice | Marginal parts, substitute parts, unnamed sensors | Name sensor, chipset and memory in the specification |
| SMT and assembly | Solder defects, misplaced parts, tilted lenses | Ask about AOI, focus checks, rework policy |
| Testing depth | Weak tests let faults escape | Agree functional and burn-in scope in writing |
| Firmware | Crashes, card errors, version mix | Freeze features, approve a version, check the string |
| Packing | Missing items, wrong manual, crushed boxes | Packing list, drop test, inspection of packaging |
| Shipping and storage | Heat, moisture, rough handling | Carton spec, route choice, storage advice |
| Usage conditions | Cards, heat, power supply in cars | Bundle suitable cards, give clear instructions |
Why averages mislead
A number quoted by a factory or a forum might count only returns inside a short window, or only units that fail inspection, or only defects the factory admits to. It may also refer to a different product class. Defects also come in different severity: a scratch and a unit that never boots are not equal. And the rate for a first batch is rarely the rate for the tenth, since learning and tooling changes alter results. That is why the better question is how a factory finds, records and removes defects rather than what its rate is. A factory that tracks defects by type and station has data to improve with; one that quotes a flat figure without records probably does not.
What a buyer controls, step by step
- Specification. Write the sensor, chipset, power buffer, lens and housing material into the program, not just the resolution. See reading a spec sheet.
- Golden sample. Approve a sample, seal a pair, and keep one. See the sample checklist.
- Change control. Require approval for any change of component, supplier, lens or firmware.
- Test scope. Agree what is tested on every unit and what on a sample, including burn-in.
- Inspection brief. Choose the AQL plan, defect classes and the inspector; see quality inspection.
- Packing and shipping. Carton specification and route suited to the goods.
- Terms for defects. Written rules for replacement, credit or return, including how claims are evidenced.
What a buyer cannot fully control
Some risk remains with the supply chain. Component shortages can force substitutions. Heat in the field can age units faster than expected. Cards chosen by end users may not match what the factory tested. Installation errors cause battery drain complaints that are not product defects; see will a dash cam drain the car battery. A realistic plan treats part of the risk as a cost of doing business and prepares for it with spare stock, clear instructions and an after-sales process, covered in warranty and returns for resellers and after-sales support.
How to track defects once you sell
Keep a simple log from the first shipment: date of purchase, batch or carton number, firmware version, symptom, and whether the card was the bundled one. After a few dozen cases, patterns appear. If failures cluster by batch, the cause is probably production. If they cluster by card type or vehicle, the cause is probably use. If they cluster by firmware version, the fix is a firmware change. This record also gives the factory something specific to work on, which speeds up a fix. Without a record, discussions turn into opinion. Share the log with the desk, which can pass the information to the factory and follow the correction through.
Defect definitions come first
Before any rate can be discussed, both sides need the same defect vocabulary. Write it into the program: what counts as a critical, major or minor defect for this model, with examples. Without it, a factory can answer "the rate is low" and be correct under its own definition while the buyer counts refund requests under a wider one. Returns are not the same as defects either: a unit returned because the buyer's customer could not route a cable is a return, not a factory defect, and mixing the two corrupts the record. Sorting inbound cases into factory defects, usage issues, shipping damage and card problems takes discipline but produces numbers that mean something. That sorted record is also what gives the buyer standing in a cost discussion with the factory, because it separates what the factory should absorb from what the buyer's market or instructions caused.
A worked pattern, illustrative
To show how the levers combine, take an illustrative case, not a real one. A buyer orders a 4K front-and-rear model for a hot market. The specification names the sensor and chipset, the golden sample is sealed, and the program sheet sets burn-in on every unit plus a temperature sample with a sharpness check afterward. The first shipment passes inspection, but month two brings reports of soft rear footage. Because the batch and firmware version were logged, the desk can trace the units to one production lot, and the factory finds the rear lens focus drifted after the heat test was skipped on a subbatch. The corrective action is written, the next lot is checked at that exact point, and the field reports stop. Nothing in that story is exotic; every step is one of the levers listed above, used in order. The same case without records would have ended in a dispute about whose fault soft video is.
How to discuss defects with a factory
Describe the symptom, give the batch and version, attach clips or photos, and ask for a root cause and a corrective action in writing. Avoid asking for an assurance of zero defects; no factory can give it, and a request of that kind usually produces vague answers. Ask instead for what was found, what was changed and how the change will be verified on the next lot. Then check the next inspection report for that specific point. That cycle is what lowers rates in practice.
The desk applies this approach on the quality control page and in the production process it coordinates. To set up a program with explicit defect terms, send your brief through the quote form.