Do not let the first description decide the cause
"It arrived broken" describes an outcome, not necessarily the failure mechanism. The product may have an inherent defect, insufficient protection, impact damage, a missing component, incorrect setup or damage after delivery. The commercial remedy may need to happen quickly, but the operational diagnosis should remain evidence-led.
Preserve the case evidence
- Order and SKU reference in the private case record.
- Clear photos or video of the issue and a short description of what was attempted.
- Outer packaging, inner protection, seals, labels and visible impact points.
- Approved sample or specification, batch or supplier version, and packing instruction.
- Delivery timing and relevant carrier events without publishing the tracking identifier.
For higher-risk or regulated products, involve a qualified person and follow reporting obligations. This guide is an operational triage tool, not a safety or legal determination.
Branch 1: probable product defect
The packaging is largely intact, the reported failure matches a function or construction issue, and comparable units may show the same pattern. Quarantine related stock where appropriate, compare against the approved reference, and test a defined sample. ISO 2859 describes formal acceptance-sampling systems; the chosen plan, defect classes and acceptance rules should fit the product risk rather than being copied blindly.
Branch 2: probable packing failure
The product may be sound before packing, but movement, abrasion, compression or missing protection leaves it vulnerable. Recreate the packed configuration, check void space and contact points, and record whether the packing instruction was followed. The corrective action may be a new insert, stronger outer carton, separation between components or a packing audit.
Branch 3: probable transit damage
Crushing, puncture, water exposure or a concentrated impact may point to the distribution journey. Preserve packaging evidence for the carrier claim and ask whether the current package was designed for the handling environment. One damaged parcel does not prove every future parcel will fail, but repeated damage at the same point should change the package or route.
Branch 4: setup, compatibility or expectation issue
The product may work as designed but lack a clear instruction, use the wrong accessory, or differ from the listing expectation. Confirm the exact variant, included components and customer-facing information. The fix may be a listing correction, setup guide or compatibility gate rather than a factory change.
Separate remedy from corrective action
- Case remedy: refund, replacement, reshipment, part, repair path or further investigation.
- Containment: hold stock, stop a batch, add a temporary check or change packing immediately.
- Root-cause action: supplier, material, construction, QC, packaging or route change.
- Effectiveness check: confirm that later units no longer show the same failure pattern.
The practical takeaway
A useful defect record closes two loops: it treats the customer fairly and makes the next order less likely to fail in the same way.
Build a defect record that can produce a real fix
- Record the approved product version, arrival date and observable problem.
- Collect clear photos or video of the item, packaging and relevant function.
- Separate product defect, packing damage, transit damage, setup issue and wear after use.
- Choose the commercial remedy, then ask whether the supplier, QC brief or packing instruction must change.
Closing one refund is not the same as correcting a repeatable problem. The useful outcome is both a fair case decision and a clearer release rule for the next order.
Want a product checked before it ships?
Tell us what must be verified on WhatsApp (+86 178 4666 9989). We can build the product, packaging and quantity checks into the fulfilment process.
Request Quality Check on WhatsApp →