Returns & Replacements
Part of POD returns and replacements
Tracking repeat defects by supplier and product
Log POD complaints by exact product and supplier, compare affected and delivered orders, and investigate recurring faults.
Link every reported POD problem to the exact product, variant, artwork version and production route. Then compare confirmed affected orders with delivered orders in a comparable group. Complaint counts alone cannot show whether a problem is becoming more common.
Keep a usable case record
Give every report a case ID tied to the store and supplier orders. Log the supplier, print provider where known, product code, variant, decoration method, artwork version, delivery date and reported issue. File the evidence, customer outcome, supplier claim outcome and closing date with the case.
Record a specific reason: damaged blank, wrong item, shifted print, unreadable text or inaccurate listing tells you more than “quality issue”. Mark an incomplete investigation as unconfirmed. If the finding changes, keep the original report and note the revised classification.
A trend sheet usually needs order references and product facts, not a buyer’s full personalisation text. Keep the necessary proof in the controlled order record.
Compare like with like
Choose a defined period and group: one poster format from one supplier, or one shirt blank with its print method and artwork version.
Count distinct delivered orders in that group, then those with a confirmed instance of the defect. Two photos of one misprint are still one affected order. If several units within an order can be affected, keep an item-level measure separately.
Observed affected-order share = confirmed affected orders ÷ delivered orders in the same group and period.
This describes reports in the store’s records, not the supplier’s full production defect rate. Some customers will not report a problem, and recent orders may not have had time to generate reports. Show the counts with any percentage, and compare periods with similar time for complaints to arrive.
Pattern / Investigation to start
- Same design produces similar complaints across suppliers
- Check the file, placement instruction and listing.
- Similar reports cluster on one supplier or product
- Review the exact configuration and linked cases with the supplier.
- Reports begin after a blank or artwork change
- Compare the affected and earlier versions.
- Reports cluster on a size or colour
- Check variant mapping, measurements and the relevant preview.
Treat these patterns as questions, not proven causes. Label an unknown production route as unknown rather than inferring it from a catalogue location.
Steps to Investigate Repeat Defect Patterns
- Define group and periodone product variant, supplier, artwork version
- Count distinct delivered orders in that group
- Count confirmed affected orders (not per item)
- Calculate observed affected-order shareaffected ÷ delivered
- Compare across similar time periods; flag trends
Act on the finding
Set an internal review trigger before interpreting a trend, such as several independent reports of the same issue. No single threshold fits every catalogue. Assess a serious safety concern immediately rather than waiting for repeated complaints.
Give the supplier representative case IDs, photos, dates and the shared product configuration. Where the supplier’s process requires it, report individual issues through that process; a pattern summary does not replace an individual claim. Keep resolving each customer complaint under the applicable rules.
After a change, start a new comparison period tied to the revised file, product or provider. Keep the earlier group visible and compare its delivered-order count. Fewer complaints caused merely by fewer sales do not establish better quality.
