A defective batch is a commercial event with a technical cause, and the outcome depends less on the argument than on the evidence. Programmes that keep batch records resolve claims in days; programmes that do not resolve them through negotiation.

This article covers the evidence set, the failure-analysis options and how to decide between rework, replacement and credit.

What evidence does a defective batch claim need?

Records plus a sample set.

A claim needs the batch code and inspection report, a documented defect description with the failure rate, a sample set of failed units and the conditions under which they failed.

The claim’s strength comes from traceability: the batch code links the units to a production record, which shows what was tested and what the results were. Without that link, the discussion moves to who is responsible rather than what happened.

The sample set matters because failure analysis cannot be performed on a description. A small number of failed units, retained unmodified, is more valuable than a large number that were opened or repaired before dispatch.

Building a defect sample set with traceability

The practical procedure is to record the failure rate, keep the failed units with their packaging, and note the conditions: the supply voltage, the load, the ambient temperature and how long the unit had been in use.

Failure analysis: who performs it and how

Failure analysis is a joint exercise: the supplier has the test equipment and the production record, and the buyer has the field conditions. A useful analysis answers three questions: what failed, whether the cause is a single unit or a batch, and whether the design, a component or the process is responsible.

Where the answer is a component lot, the analysis moves to incoming inspection. Where it is a process step, it moves to the line record. Where it is a design margin, the answer affects the whole programme rather than one batch.

Rework, replacement or credit

The three remedies fit different situations. Rework is appropriate when the defect is correctable without affecting the product’s verified state. Replacement suits a defect that affects a subset of units. Credit is the practical answer when the cost of recovery exceeds the value of the goods, provided the safety question is settled.

Where the defect touches safety or compliance, the discussion is not primarily commercial: the affected units must be identified, and the destination market’s requirements determine whether notification is necessary.

Field failure versus incoming inspection failure

The distinction changes the remedy. A defect found at incoming inspection offers options: sort, rework, replace or return. A defect found in the field has already incurred customer impact, and the cost of recovery includes returns, replacements and, potentially, reputation.

That asymmetry is the reason inspection plans and claim policies should be written together, since the cost of a field failure justifies tighter sampling at the factory.

Handling a safety-related defect

A safety-related defect requires a defined sequence: stop shipment, identify affected batches by code, assess the population in the market, and decide on the appropriate response under the destination market’s rules. That response may include notification, recall or a field action.

Documentation discipline is what makes this possible. Where batch codes are recorded on shipments and returns, the affected population can be identified precisely; where they are not, everything has to be treated as suspect.

Preventing the repeat batch

A claim that ends with a credit but no corrective action will be followed by a second claim. The corrective action should name the change – a component, a process step, a test addition – and the verification that will demonstrate it worked.

The verification is usually a follow-up batch with a documented comparison against the previous one, which is why the batch record format matters. WECENT’s quality control process produces per-batch inspection reports and supports failure analysis on returned units; programme documentation and analysis reports are available under NDA through the OEM/ODM programme, with the platform range listed in the product catalogue. Market documentation for the affected units follows the destination’s rules (Regulation (EU) 2019/1782, 47 CFR Part 15 and, where batteries are involved, US EPA: used lithium-ion batteries).

Programmes in this area are decided by documentation as much as by hardware. The practical discipline is to keep one file per model containing the specification, the test and inspection records and the market documents, and to review it whenever the bill of materials or the production site changes. WECENT produces per-batch inspection records at its quality control gates and provides model-level specifications and certification planning through its OEM/ODM programme, with the platform range listed in the product catalogue.

For batch claims and failure analysis, the same file answers most questions that arise during qualification, audit or listing review: which standard applies, which model was tested, and which batch the shipped units came from. Reference documents for the relevant requirements are published by the standards and regulatory bodies, including the official text and the related requirement, with the equivalent market rule and https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15 applying where the product is sold into those markets.

Two further habits keep the file usable over time. The first is to record the review date and the reviewer against each document, so that an outdated report is visible rather than assumed current. The second is to keep the commercial documents – quotation, agreed specification and packaging artwork – in the same folder as the technical evidence, because a question about a shipped unit usually requires both.

A further point concerns the production reality behind the paperwork. Claims that survive scrutiny are the ones a factory can reproduce batch after batch, which means the specification, the test method and the acceptance criteria have to travel together with the order. Where they do not, the same product can be built to two different understandings of the same document.

Finally, buyers should decide in advance what evidence they will need if a question arises later, and request it at the sampling stage rather than after the shipment. Requesting records retrospectively is possible, but it is slower and it removes the opportunity to correct a specification before tooling. WECENT supports programmes with model-level specifications and per-batch inspection records produced at its quality control gates, available under NDA through its OEM/ODM programme, with the platform range listed in its product catalogue catalogue.