Most dropshipping quality programmes are a single check at the wrong moment: the customer opens the box and becomes the inspector. By then the defect has already cost you the sale, the return shipping and often the review. Quality control works when it is placed at the points where a defect is still cheap to catch — before it ships, and ideally before it is even made. This playbook sets out those points.

Ключевые выводы
- QC is a set of inspection points, not one final check; the cheapest place to catch a defect is before production.
- Pre-shipment inspection catches what inbound receiving missed; the two are not interchangeable.
- An AQL sample is a statistical statement about a batch, not a guarantee about every unit.
- Defect documentation is what makes suppliers fix root causes; a photo without a category fixes nothing.
- QC data feeds directly into refund and chargeback reduction — the same defect drives both.
Where to Place Inspection Points
Three points cover most of the value, and each catches a different class of defect.
| Inspection point | Что она выявляет | Cost to catch here |
|---|---|---|
| Pre-production / sample approval | Specification and design defects | Lowest — before tooling or a print run |
| Входящая приёмка | Wrong quantity, wrong item, transit damage | Low — before the item is listed or shipped |
| Pre-shipment (outbound) | Wrong item picked, damage, missing components | Moderate — before the customer sees it |
| Post-delivery (returns analysis) | Systemic defects the earlier points missed | Highest — sale already lost |
The pre-production point is the one most sellers skip and the one with the best return. A specification signed off before the print run or the production batch prevents an entire batch of defects, which is why the sample and specification discipline in our packaging quality guide pays for itself many times over.
What an AQL Sample Actually Tells You
Sampling is how you inspect a batch without inspecting every unit, and understanding its limits prevents over-confidence.
| Concept | Что это значит | What it does not mean |
|---|---|---|
| Sample size | How many units are pulled for inspection | That the rest are identical |
| Acceptable quality limit | The defect rate the sample is designed to tolerate | That the batch is defect-free |
| Major vs minor defect | Defects that make the item unsellable vs cosmetic | That minor defects are free — they still drive returns |
| Accept / reject decision | A statistical call on the batch | A guarantee about any individual unit |
The practical implication: a passing sample means the batch is probably acceptable, not that it is perfect. For high-value or high-return categories, increase the sample or inspect every unit. The inbound inspection workflow that catches bad batches before they reach a customer is covered in нашем руководстве по предотгрузочной проверке.
Documenting Defects So They Actually Get Fixed
A photo sent to a supplier with “these are bad” gets a replacement and a repeat next month. A categorised defect record gets a root-cause fix.
| Field | Почему это важно |
|---|---|
| Defect category | Lets you see patterns across batches instead of one-offs |
| Batch / PO reference | Links the defect to a specific production run |
| Quantity affected | Distinguishes a systemic issue from isolated units |
| Photo with reference | Shows the defect against the specification, not just the damage |
| Specification clause | Makes the conversation about a requirement, not an opinion |
Track defect categories monthly. A supplier with a rising trend in one category has a process problem you can name; one with scattered isolated defects has a handling problem. Both are fixable, but only if the data distinguishes them.
From QC Data to Fewer Refunds
The link between QC and refunds is direct: most refund reasons are quality failures that reached the customer. Map your refund reasons to defect categories and the highest-cost refund reason usually points at a specific missing inspection point.
Two secondary effects matter as well. First, QC documentation is what supports a chargeback dispute — the evidence requirements are covered in нашем руководстве по профилактике чарджбеков. Second, QC findings feed supplier scorecards, which is how quality improves across orders rather than within one. The customer-facing side of the same problem is addressed in our customer service guide.
FAQ
Что такое контроль качества в дропшиппинге?
Набор контрольных точек на этапах закупок, входящего и исходящего потока, которые выявляют дефекты до того, как их обнаружит клиент. Это рабочий процесс, а не финальная проверка.
Когда мне нужно проверять товары для дропшиппинга?
Хотя бы на трех этапах: утверждение образца или предсерийной продукции, приемка входящей продукции и проверка перед отгрузкой. Каждый этап выявляет разные типы дефектов при разных затратах.
Что означает AQL при контроле качества продукции?
Acceptable quality limit — the defect rate a sample inspection is designed to tolerate. A passing sample is a statistical call on the batch, not a guarantee about every unit.
How do I get a supplier to fix a recurring defect?
Document it with a category, batch reference, quantity affected and the specification clause it violates. Categorised data shows a pattern; a photo alone gets you a replacement and a repeat.
Does quality control reduce refunds?
Yes, directly. Most refund reasons are quality failures that reached the customer. Mapping refund reasons to defect categories shows which inspection point is missing.
Should I inspect every unit?
For high-value or high-return categories, yes. For most categories, a properly sized sample with a defined AQL is the practical balance between cost and coverage.
How does QC help with chargebacks?
Inspection records and defect documentation are the evidence that supports a dispute. Without them you are asserting quality; with them you are demonstrating it.
Техническая подоплёка: контроль качества, acceptable quality limit и statistical process control explain the inspection framework referenced above.