# Electronics QC checkpoints: what to test before shipment
Most electronics quality failures are invisible. A cracked solder joint, a wrong firmware version, a battery that dies after forty charge cycles: none of these show up in a photo of the finished goods. That is why electronics QC checkpoints matter more than in almost any other category. You are not checking how the product looks. You are checking whether it works, whether it keeps working, and whether the units in the box match the sample you approved.
This guide lists the electronics QC checkpoints to run before a shipment leaves China: the functional tests, the reliability tests, the firmware and labeling checks, and the sampling logic that ties them together. It covers the final inspection stage in detail and shows where during-production checks fit. If you take one idea from this guide, make it this: a defined test plan, agreed before production, beats the most thorough inspector working from vague instructions. The electronics QC checkpoints below are that plan, written out.
Electronics QC checkpoints start with the plan, not the inspection
An inspection is only as good as its instructions. Before production begins, write a QC plan that names every checkpoint, the method, the sample size, and the pass criteria. Put it in the purchase order or a separate QC agreement. A factory that knows the tests in advance builds to them. A factory that meets the inspector for the first time on inspection day negotiates them.
The plan has two halves. AQL sampling governs the visual and dimensional checks: how many units get pulled from the shipment and how many defects are allowed at each severity level. The functional test plan governs what those sampled units actually do: power on, run the functions, and survive the reliability checks. AQL alone is not enough for electronics, because most electronic failures are functional, not cosmetic. The electronics QC checkpoints that catch real problems are the functional ones.
Define defect severity in the plan. Critical defects make the product unsafe or non-functional. Major defects impair function or salability. Minor defects are cosmetic and do not affect use. The plan should state the AQL levels for each and, just as important, which functional failures count as critical regardless of count. One unit that fails to power on is not a statistic. It is a reason to stop the inspection and investigate. Writing these rules down is what turns generic electronics QC checkpoints into a plan your inspector can actually enforce.
Assign responsibility too. Who performs the inspection: your own staff, a third-party inspector, or the factory's QC team with your oversight? Who pays for re-inspection if the shipment fails? Ambiguity here causes more disputes than defective products do. The best electronics QC checkpoints in the world do not help if nobody is clearly responsible for running them.
Function testing: make every sampled unit prove itself
Function testing is the core of electronics QC. Every unit in the sample gets powered on and run through its functions, and the results are recorded against the approved sample. This sounds obvious. It is skipped more often than buyers expect, especially when the inspector is under time pressure and the product "looks fine."
Build the function list from your specification. Every button, every mode, every port, every wireless function gets exercised. For a Bluetooth speaker: pairing, audio playback, volume and track controls, charging, and LED indicators. For a smart device: app pairing, each sensor reading, firmware version display. The test procedure should be written step by step so any trained inspector can execute it identically. Vague instructions like "test functions" produce vague results.
Test with the actual accessories and the actual power sources the customer will use. A device that works on the factory's bench supply but fails on its own charger has a real defect. Charge and discharge at least once where the product has a battery. Check that the device enumerates correctly when plugged into a computer, if that is part of its function. Real-world conditions are what separate serious electronics QC checkpoints from lab exercises.
Record failures precisely. "Three units failed Bluetooth pairing" is actionable. "Some Bluetooth issues" is not. The failure log is what lets the factory find the root cause, and it is what justifies rejecting the shipment if the failure rate exceeds the plan. Among all electronics QC checkpoints, function testing catches the largest share of real defects, because it is the only checkpoint that treats the product as the customer will. Give it the biggest share of inspection time accordingly.
Burn-in, drop, vibration, and cycle life: reliability checkpoints
Function testing proves the product works today. Reliability checkpoints ask whether it still works after real use. These tests take time, which is why they are often cut, and cutting them is how products with 5% field failure rates ship with clean inspection reports.
Burn-in means running the product under power for a defined period, often hours, to catch early-life failures. Components that are going to fail tend to fail early, and a burn-in period on the production line or in the lab pulls those failures out before the customer finds them. Define the duration and conditions in the QC plan. A token ten-minute power-on is not a burn-in.
Drop and vibration testing simulates shipping and handling. The packaged product gets dropped from defined heights onto defined surfaces and vibrated on a shaker table, then inspected and function-tested again. This catches weak solder joints, loose connectors, and packaging that does not protect the product. If your product ships by sea and then by truck, it will be dropped. Test for it.
Button and cycle-life checks cover the mechanical interfaces: buttons pressed thousands of times, hinges opened and closed, ports plugged and unplugged. These are defined by cycle counts in the plan, not by feel. A button that works on inspection day and fails after a month of normal use is a warranty claim waiting to happen, and cycle testing is the checkpoint that finds it.
None of these tests needs a laboratory for every production run. The factory should have the equipment for routine reliability checks, and the inspection can witness or sample them. What matters is that the checkpoints exist in the plan and produce records, not that they happen in a white coat. When buyers compare electronics QC checkpoints across suppliers, the presence of real reliability equipment on the floor is one of the clearest quality signals.
Firmware, labeling, and accessory completeness
Three checkpoints that are cheap to run and expensive to miss.
Firmware version checks confirm that every unit ships with the approved firmware. Flash the wrong version, or let the factory ship whatever was loaded last, and you get inconsistent behavior across the shipment that no functional test on a small sample will fully characterize. The QC plan should name the exact firmware version, and the inspector should verify it on sampled units, ideally through the product's own version display or a connected app. Keep a record of which firmware shipped with which production batch. When a field issue appears six months later, that record is how you scope it.
Labeling checks cover the marks the product must carry: model number, ratings, certification marks, serial numbers, and battery warnings where applicable. Verify the labels against the approved artwork and against the certification documents. A label with the wrong model number undermines the certificate that names the right one. Check that serial numbers are unique and sequential as specified; duplicated serials suggest mixed production batches.
Accessory completeness closes the loop. Open the retail package exactly as a customer would and confirm every listed item is present: the device, charger, cable, manual, and any extras. Count them against the packing list. Missing accessories are among the most common inspection failures and the easiest to prevent, because the check takes minutes. The electronics QC checkpoints that buyers skip are usually the boring ones, and accessory completeness is the classic example. Put it on the checklist anyway.
AQL plus functional test plans: the sampling logic
You cannot test every unit in a 10,000-piece shipment. Sampling logic is how a few hundred tested units give you confidence in the rest. Get this wrong and the inspection is theater.
AQL, acceptable quality limit, defines the sampling plan for visual and dimensional checks. The inspector pulls a statistically defined sample from the finished, packed goods and counts defects by severity. Standard tables set the sample size from the lot size and the inspection level. Most electronics buyers use general inspection level II as the default and set AQL 2.5 for major defects and 4.0 for minor defects as a starting point, tightening where the product demands it. The key discipline: the sample must be drawn randomly from finished cartons across the shipment, not handed over by the factory.
The functional test plan runs on the sample or a defined subset of it. Decide in advance what percentage of sampled units gets full function testing. For high-value or high-risk products, that percentage should be high. For simple products, a smaller subset may be defensible. Write the number down. "Test some units" is how inspections end with three tested units and a signed report.
Handle failures by the plan, not by negotiation. If defects exceed the AQL limits, or if any critical functional failure appears, the inspection fails and the shipment does not move until the root cause is found and the lot is reworked or resorted. Re-inspection follows, and the plan should state who pays for it. This sounds harsh. It is the only version that works, because a failed inspection with no consequences teaches the factory that the checkpoints are suggestions.
During-production checks catch what final inspection cannot
Final inspection gets the attention, but during-production checks catch a different class of problems: the ones baked in before the product is finished. A wrong reel of components loaded on day two, a soldering profile drifting out of spec, a firmware flash step skipped on one line. By final inspection these are finished goods with defects inside them, and sampling may or may not find them.
An inspector on the line during production verifies that the right components are being placed against the BOM, that in-process testing is running and its results are recorded, and that the process matches what was agreed. This is also where counterfeit-component defenses live: checking that components come from the expected sources and match the approved parts. The cheapest time to catch a wrong component is while the reel is still on the machine.
Schedule the during-production visit for the first days of the run, when setup errors appear, and consider a second visit mid-run for long productions. The cost is a fraction of a failed final inspection, because finding the problem early means reworking hundreds of units instead of rejecting thousands. Buyers who run only final inspections are inspecting the factory's output. Buyers who add during-production checks are inspecting the factory's process. For electronics, the process is where the quality lives, and process checks belong in every serious set of electronics QC checkpoints.
Conclusion
Electronics QC checkpoints form a system: a written plan before production, function testing on the sample, reliability checks for burn-in and mechanical life, firmware and labeling verification, accessory completeness, and sampling logic that combines AQL with functional test plans. Add during-production checks for the problems final inspection cannot see. None of this requires exotic equipment or unusual expertise. It requires writing the plan down, agreeing it with the factory, and enforcing it when the results say no. The shipments that pass these electronics QC checkpoints are the ones that stay sold.
Frequently asked questions
### What are the most important electronics QC checkpoints?
Function testing on every sampled unit, firmware version verification, and burn-in for early-life failures. Visual AQL checks matter, but most electronic failures are functional, so the functional electronics QC checkpoints carry the most weight. If inspection time is limited, spend it there.
### How many units should be function-tested?
It depends on the product's value and risk. Define the percentage in the QC plan before production. High-risk products deserve a high percentage of the AQL sample; simple low-value products can use a smaller subset. The number should be written down, not decided on inspection day.
### What is the difference between AQL and functional testing?
AQL is a statistical sampling method for counting visual and dimensional defects. Functional testing powers the product on and exercises its features. Electronics need both, because AQL alone misses the failures customers actually experience. A complete electronics QC checkpoints plan always pairs the two.
### Should I inspect during production or only at the end?
Both. During-production checks catch process problems like wrong components while they can still be fixed cheaply. Final inspection verifies the finished shipment. For electronics, skipping the during-production visit leaves the highest-cost defects unguarded, which is why the full set of electronics QC checkpoints spans the whole production timeline, not just the last day.
### Who should perform the inspection?
Your own QC staff, an independent third-party inspector, or a sourcing partner with QC capability. The factory's own QC team can support the inspection but should not be the only party signing off, since they report to the factory.
### What happens when an inspection fails?
The shipment does not move until the root cause is found and the lot is reworked, resorted, or remade. Then a re-inspection happens under the same plan. Put the re-inspection cost and responsibility in writing before production starts, or the failure becomes a negotiation instead of a procedure.