Most chargebacks trace back to a small set of factory defects that were visible weeks before shipment. This second part of the series shows how a during-production inspection turns those early signals into corrections while cartons are still open. The method is straightforward: match each return code to the workstation that creates it, check that station mid-run, and fix the drift before packing. Acceptance sampling provides the math for how many pieces to pull, and factory acceptance logic supplies the pass-or-hold discipline that keeps shaky lots out of the container.
Key takeaways
- Each major return code maps to one workstation, and DPI checks that station while output can still be reworked, with sample sizes grounded in the statistical logic of acceptance sampling[1].
- Catching drift while 20 to 50 percent of the order is finished leaves enough unfinished units to justify a machine reset or operator retraining, at far lower cost than opening sealed cartons.
- A DPI report functions like a factory acceptance test held mid-run, with defined criteria, recorded evidence, and a clear pass, rework, or hold decision[2].
- Dated photos, measurement sheets, and defect counts from mid-production document that goods matched the approved standard, which strengthens the seller's position in chargeback disputes.
- Findings only pay off when they feed the next purchase order as tighter tolerances, clearer packing instructions, and explicit criteria for the next inspection.
Chargebacks and returns rarely arrive as surprises to anyone who has watched the production line. The wrong shade, the short inseam, the missing accessory, and the dead-on-arrival unit each leave traces weeks before the goods ship. Buyers who only inspect sealed cartons meet these problems at their most expensive moment, when every fix means opening boxes and renegotiating sailing dates.
A during-production inspection moves the checkpoint upstream, into the weeks when output is still flowing and corrections are cheap. An inspector on the floor can pull pieces straight off the line, compare them against the approved reference, and flag drift while the responsible workstation is still running. That timing advantage is the entire economic case for DPI in return prevention.
This article is the second part of a series on reducing chargebacks with mid-production checks. It maps five frequent return reasons to their factory origins, describes what inspectors actually verify while the line runs, and sets out a report-to-action workflow. Sampling logic follows acceptance sampling principles, and the pass-or-hold discipline borrows from factory acceptance testing.
Start from the return code, not the defect list
Chargeback reports rarely speak the language of the factory. They say wrong size, arrived damaged, color not as pictured, missing parts, or stopped working after a week. Each phrase points to a workstation: cutting tables, sewing lines, dye lots, packing benches, or function test benches. The buyer's job is to translate the complaint backward along the line until the responsible station comes into view. That translation is the real planning document for a during-production inspection, because it tells the inspector exactly where to stand and what to measure.
Timing decides whether that knowledge pays. When the first finished cartons show drifting measurements, many importers ask UTS to place an inspector on the line while machines are still running, because a mid-run correction costs a fraction of post-packing rework. Sealed cartons must be opened, pieces re-sorted, and shipping dates renegotiated. Open production, by contrast, can be steered with a machine reset, a retrained operator, or a segregated material batch.
This article builds the bridge between complaint codes and line checkpoints. It maps five frequent return reasons to their factory origins, shows what inspectors verify while output still flows, and lays out a workflow that turns findings into fewer refunds. The statistical backbone comes from acceptance sampling theory, and the decision discipline borrows from factory acceptance testing.
Mapping five common return codes to line checkpoints
| Return code buyers file | Workstation that creates it | DPI checkpoint | Fix before packing |
|---|---|---|---|
| Wrong size or fit | Cutting and sewing | Measure early pieces of each size against the spec sheet[1] | Recut or regrade before bundling |
| Loose threads and open seams | Stitching line | Pull samples hourly and tug-test seams | Reset tension and re-sew the affected bundle |
| Color or shade mismatch | Fabric batch changeover | Compare running output with the approved swatch under daylight | Segregate the off-shade batch |
| Missing parts or accessories | Assembly and packing table | Count parts per set against the bill of materials[2] | Complete the sets before cartons are sealed |
| Dead on arrival or weak function | Function test bench | Power-test samples from each hour of output | Quarantine the faulty lot for repair |
Keep this mapping inside the inspection instruction sheet so the inspector checks causes rather than symptoms, and every finding arrives with a workstation attached.
What inspectors actually verify mid-run
A mid-run visit has a different rhythm from a final check. Instead of judging sealed cartons, the inspector samples pieces straight off the line, compares them with the approved reference, and records whether the process is stable or drifting. Two verification blocks carry most of the weight.
Measurements and workmanship
The inspector starts where returns start: dimensions and seams. Pieces are pulled at intervals across sizes and colors, measured against the specification sheet, and checked for stitching density, seam strength, and finishing defects. Because only part of the order exists, the sample is spread across the output available so far, which follows the same representative-sampling idea that acceptance sampling theory describes[1].
Workmanship checks run alongside measurement. The inspector looks at edge finishing, thread ends, print alignment, and surface flaws under normal light, recording each defect with a photo and a location on the line. When one workstation produces most of the findings, the supervisor can usually trace it to a single operator, machine setting, or material batch within the hour.
Function and completeness
For assembled or powered goods, the inspector operates samples exactly as a buyer would: switching, charging, fitting parts together, and fastening closures. Failures are logged with the time of production so the faulty period can be isolated. This mid-run function screen mirrors the acceptance-test habit of proving that the product does what its specification claims before it moves to the next stage[2].
Completeness closes the visit: counting parts per set, verifying labels and barcodes, and confirming that gift boxes, manuals, and accessories match the order. Missing-part returns look trivial until they arrive by the thousand, and a mid-run count catches the shortage while the missing components can still be produced or purchased in time.
Turning a DPI report into fewer chargebacks
- Code every finding by return riskTag each defect with the return code it would have become, so the factory sees refunds rather than abstract quality points. A seam failure tagged as a certain return concentrates attention far better than a generic workmanship note.
- Contain the suspect output the same dayMark the cartons produced during the faulty period and stop them from moving to packing. Containment takes an hour on the floor and saves weeks of arguing about mixed lots later.
- Agree the correction with the line supervisorWalk the line supervisor to the failing station, agree the concrete correction, and write it into the report with a name and a deadline. Vague promises to pay attention evaporate once the inspector leaves.
- Re-verify before the lot moves to packingHave the inspector or a trusted follow-up check re-measure fresh output from the corrected station before those cartons are sealed. Unverified corrections have a habit of drifting back within days.
- Feed the pattern into the next purchase orderConvert the pattern into purchase-order language: tighter tolerance on the drifting dimension, an explicit shade-approval step, or a mandatory function test per hour. The next inspection then starts from a stronger baseline.
One rule keeps the whole exercise honest: never let a doubtful lot ship on promises. If the DPI report says hold, the lot stays until rework is verified, because every waived defect becomes a return carrying the buyer's name. Discipline at this gate is what converts inspection fees into fewer refunds.
Sources
- Wikipedia: Acceptance sampling —— Overview of acceptance sampling including AQL concepts used in product inspection.
- Wikipedia: Factory acceptance test —— Overview of factory acceptance testing performed before shipment or installation.
Frequently asked questions
How is DPI different from final inspection when the goal is fewer returns?
Final inspection judges sealed cartons, so its only options are ship or rework the whole lot. DPI happens while machines run, so the inspector can point at the workstation causing the problem and have it corrected on the spot. For chargeback prevention that difference is decisive, because most returns come from process drift that a final sample either misses or finds too late.
What share of the order should be finished before booking DPI?
A common window is 20 to 50 percent completion, with at least some finished pieces and most materials still in process. Earlier than that, the sample reflects pilot runs rather than steady production. Later than that, too much output is already packed and corrections turn into expensive rework.
Can DPI evidence help dispute a chargeback?
Dated photos, measurement sheets, and defect counts taken mid-run show the goods matched the approved standard at a documented point in production. Marketplaces still decide cases on their own rules, but organized production evidence consistently strengthens the seller's position compared with having no records at all.
Should every SKU get a DPI, or only risky ones?
Risky first orders, complex assemblies, and products with a history of size or function complaints deserve it most. Stable repeat orders with clean inspection history can sometimes rely on final inspection alone. A practical rule is to require DPI for every new supplier and relax it only after two clean production cycles.