Before launch, decide how your team will identify a reported missing or damaged component and what response it can actually offer. Plan by exact SKU, component version and evidence.
Map each SKU to its component record
Store the approved contents list, package image, production revision and contact route. These separate City and Farm references do not prove interchangeable accessories. Request a component diagram and written supplier confirmation.
100PCS City Construction Magnetic Blocks Set
MBP-010 · City set reference for SKU-specific records.
View product100PCS Farm Life Magnetic Blocks Set
MBP-011 · Farm set reference; do not assume interchangeability.
View productSeparate the problem from the remedy
Ask for order reference, SKU, box version and clear photos. Check pack-out and receiving records before assigning a cause. Escalate any safety concern through your seller safety process.
Define what support can promise
Document whether the supplier offers individual pieces, a replacement set or another agreed resolution for the exact SKU and market. Confirm cost, availability and shipping in writing.
- Identify SKU and revision
- Record the component and evidence
- Compare with approved contents
- Confirm owner and resolution
- Track repeat reports by SKU
SKU [ ] · component [ ] · version [ ] · evidence [ ] · remedy [ ] · cost/availability [ ] · owner [ ].
Use the missing-pieces guide, then send model IDs before publishing replacement wording.
FAQ
Can I promise replacement pieces for every set?
Only after supplier confirmation for the exact SKU.
Can City and Farm pieces be shared?
Do not assume interchangeability from photos or title counts.