A supplier can say that every unit was tested, yet the buyer may still have no clear answer to a practical question: What function was checked, under what conditions, using which fixture, and what happened when a unit failed? A final test becomes meaningful only when it is tied to a defined product requirement and a record that supports the release decision.
A China supplier end-of-line testing process gives the factory a final functional-test instruction before completed goods are packed or released. It identifies the product configuration, test input, fixture, sequence, pass and fail criteria, sample or unit scope, result record, failure hold, retest rule, and authorized release owner.
This is general commercial quality guidance. It does not define electrical safety, radio, battery, medical-device, software-validation, product-safety, or other regulated testing requirements. Buyers should use qualified engineering, laboratory, regulatory, and legal support when a test decision has technical or compliance consequences.
“Tested” is a claim. A controlled test instruction explains what the claim means.
Define the function that matters to the buyer
Start with the product behavior the factory must verify. “Works normally” is not a usable instruction. Describe the function in terms of what the operator must set up, what action to perform, what response to observe, and what result counts as passing. The required detail depends on the product.
| Product type | Example functional question |
|---|---|
| Mechanical assembly | Does the mechanism move through its intended range without binding or unexpected interference? |
| Electronic product | Does the defined input produce the required display, output, or response? |
| Pump, valve, or dispenser | Does the unit operate under the stated setup without visible leakage or failure to actuate? |
| Battery-powered item | Does it power on, perform the designated action, and respond to the specified charge or input condition? |
| Furniture or hardware | Does the assembly open, close, lock, or attach as specified? |
| Packaging feature | Does the closure, seal, dispenser, or tear function operate as intended? |
Do not try to turn a final functional check into every possible product test. The buyer should identify the release-critical functions that a factory can check consistently at the end of the line. Other requirements may belong at incoming material, in-process, laboratory, engineering, or third-party testing stages.
Write a factory-ready test instruction
The test instruction should be short enough for an operator to use but complete enough that another person can reproduce the test. Connect it to the current drawing, bill of materials, software version where applicable, and product configuration. If a product has several variants, state which parts of the instruction differ.
| Test-instruction field | Why it matters |
|---|---|
| Product ID and revision | Prevents testing the wrong model or outdated configuration |
| Function to verify | States the exact behavior or output under review |
| Test setup | Defines power, accessories, media, load, position, or other starting condition |
| Fixture or equipment | Identifies the controlled tool, jig, device, or tester used |
| Test sequence | Shows actions in the order the operator must perform them |
| Pass criterion | Defines observable result, reading, position, or response required |
| Fail criterion | Defines what must be held, rejected, or escalated |
| Record requirement | States unit, lot, operator, date, equipment, and outcome fields |
| Rework and retest rule | Controls what happens after a failed test |
Use a photo, diagram, or short video reference when setup is difficult to explain. A simple image of fixture orientation can stop an otherwise competent operator from applying the test to the wrong face, connector, or assembled position.
Control the test conditions and fixtures
Functional results can change when the factory uses a different cable, input, load, fixture, software setting, power source, or physical orientation. Define the conditions that matter to the decision and ask the supplier to identify the test equipment or fixture used for critical tests.
| Test condition | Buyer control question |
|---|---|
| Product configuration | Is the correct model, component revision, firmware, or accessory installed? |
| Input or power | Is the defined power, load, pressure, signal, or operating condition used? |
| Fixture | Does the unit sit, connect, or align in the specified test position? |
| Test equipment | Is the tester or instrument identified and under the factory’s control process? |
| Environmental condition | Does temperature, humidity, or cleanliness matter to the product function? |
| Operator action | Is there a documented sequence that avoids subjective variation? |
| Result display | Does the operator know where to read the pass, fail, or measured output? |
An end-of-line fixture does not need to be complex to be controlled. For a low-risk mechanical check, it may be a simple go/no-go setup. For a higher-risk product, it may include a programmed tester. The buyer’s requirement should match the function and the consequence of a bad release decision.
Define pass, fail, and inconclusive outcomes
Operators need a clear action for every outcome. A pass criterion should be observable. A fail criterion should trigger containment. An inconclusive result should not be converted into a pass because the line needs to keep moving.
| Outcome | Factory action |
|---|---|
| Pass | Mark or record the defined result and move the unit to the next authorized stage |
| Fail | Identify and segregate the unit or defined lot, then record the failure condition |
| Inconclusive | Stop release of the affected unit, verify setup, and repeat only under a defined rule |
| Tester malfunction | Hold affected output since the last known-good equipment check and notify the responsible owner |
| Reworked unit | Follow a written rework instruction and repeat the required test before release |
| Repeated failure | Expand containment and trigger a cause or process review before normal release resumes |
The factory should not use “operator judgment” as a pass criterion unless the buyer has defined a visual standard or other controlled basis. For a measured output, state the acceptable range and units. For a function, state the required response and any time or sequence condition that is relevant.
Decide whether to test every unit or a defined sample
Some functions should be checked on every unit. Others may be checked by lot or sample according to a buyer-defined inspection plan. The right choice depends on the product, test time, potential failure mode, process capability, contractual requirement, and risk. The buyer should state the planned scope rather than allowing the factory to assume it.
| Test scope | When it may be appropriate |
|---|---|
| 100 percent unit test | A release-critical function can be checked quickly and a failed unit must not ship |
| First-off test | Verifies setup when a line begins or changes over |
| Periodic in-process test | Confirms a process remains in control between first and final checks |
| Lot sample | Supports a defined inspection plan for lower-risk characteristics |
| Final packed sample | Checks function after final assembly or packaging effects |
| Independent witness sample | Gives buyer or third party evidence for a critical or disputed item |
Do not claim that 100 percent testing guarantees zero defects. A test only checks what the method can detect under the stated conditions. It is still valuable when it is correctly designed, controlled, and linked to the shipment scope.
Capture test records that support traceability
A final test record should let the buyer see what was tested and whether the result belongs to the product or lot being released. Keep it proportionate. A simple product may need only lot, date, quantity, result, operator, and exception. A complex product may need unit serial number, fixture ID, readings, software version, and retest history.
| Record field | Why retain it |
|---|---|
| Product, SKU, or configuration | Connects test to the correct item |
| Lot, work order, or serial number | Defines the output covered by the record |
| Date and time | Places the test in the production sequence |
| Operator or station | Supports factual investigation and training review |
| Fixture or tester ID | Identifies the equipment used |
| Test result | Records pass, fail, inconclusive, or retest outcome |
| Measurement or evidence | Captures reading, image, log, or reference where needed |
| Disposition | Shows accepted, held, reworked, or rejected status |
For medical devices, 21 CFR 820.80 describes acceptance activities as inspections, tests, or other verification activities, and describes final acceptance procedures, control of finished product until release, data review, authorized release, and records of activity, date, result, signature, and equipment where appropriate.1 Those are device-specific regulatory requirements. The buyer can still apply the general discipline of defined test, retained result, and controlled release to an ordinary commercial product.
Hold and investigate failures before packing
A failed end-of-line test can signal more than an isolated unit problem. It can reveal an assembly, component, tooling, software, or process problem that affects other output. Ask the supplier to identify the failure, stop the affected unit from entering packing, assess the production scope, and report the immediate containment action.
| Failure response step | Buyer expectation |
|---|---|
| Identify the unit or lot | Prevents a failure from disappearing into normal stock |
| Segregate affected goods | Keeps suspect output separate from accepted goods |
| Record the failure | Preserves symptom, time, test station, and product information |
| Review scope | Determines whether adjacent units, shifts, or lots may share the issue |
| Correct or rework | Uses an authorized instruction rather than an improvised repair |
| Retest | Repeats the required functional check after the defined action |
| Escalate repeat failures | Triggers a process, material, or engineering review where needed |
Do not allow a factory to erase failed test results after a rework pass. Keep the initial failure, action taken, and final retest outcome. That history helps the buyer determine whether an isolated issue became a recurring process signal.
Link testing to packing and shipment release
The buyer should define when test completion is checked. For some products, a completed test record is a condition before the unit is packed. For others, the record supports a lot-level final release. The factory needs to know how it should identify goods that are tested, untested, held, or awaiting review.
| Release status | Factory control |
|---|---|
| Untested | Keep separate from final-packed or releasable goods |
| Passed | Link to test record and authorized packing flow |
| Failed | Quarantine or segregate pending disposition |
| Reworked | Identify for required retest before normal flow |
| Awaiting review | Prevent loading or shipment release until authorized decision |
| Released lot | Connect final release to defined test-record scope |
A buyer can verify the system during production by asking for a sample record, viewing the fixture or station, checking the physical status labels, and comparing finished goods with the documented lot or serial range. A third-party inspection may confirm the evidence but does not replace a factory’s day-to-day test control.
Frequently asked questions
What is end-of-line testing with a China supplier?
It is a defined final test or verification performed on completed products before packing or release. The buyer should specify the function, setup, pass criterion, scope, record, and failure action rather than accepting a generic claim that units were tested.
Should every unit receive a functional test?
It depends on product risk, test feasibility, contractual requirements, and the function being checked. The buyer should define whether the test applies to every unit, first output, periodic samples, lots, or an independent witness sample.
What should happen if a final functional test fails?
The supplier should identify and hold the unit or affected scope, record the failure, assess whether other output may be affected, use an authorized correction or rework instruction, and retest before release.
Can a pre-shipment inspection replace factory end-of-line testing?
No. A pre-shipment inspection is a separate, time-limited check. A controlled factory test can occur on every unit or at defined production stages and creates records that a final inspection can review.
Make final testing a release control
A China supplier end-of-line testing process turns “tested” into a defined production control. It links the intended function, setup, fixture, acceptance criteria, results, failure containment, retest, and final release scope so the buyer can understand what occurred before goods were packed or shipped.
Before the next functional product order, add a short end-of-line test instruction and record format to the factory package. Supplier Ally can help buyers coordinate test requirements, supplier work instructions, factory evidence, targeted inspections, and controlled shipment release across China sourcing projects.
EN 
ES 