Free lesson · 11 minute read · Reseller Growth Systems

Refunds, Replacements, and Wrong-Item Disputes

Use a structured evidence and resolution process instead of improvising under pressure.

Your goal

Build a refund-case workflow from intake through resolution and inventory update.

When to use

Use whenever a buyer or supplier reports a defect, wrong specification, missing item, lock, or damage.

Why this matters

Returns become expensive when evidence, item identity, supplier responsibility, and payment status are unclear.

The lesson

Start every case by identifying the exact transaction and physical unit. Capture the complaint in factual terms. What is wrong? When did it appear? What evidence exists? Compare that with pre-sale photos, testing notes, serial, listing, receipt, and buyer communication. Classify the issue: verified pre-existing defect, wrong item/specification, shipping damage, misunderstanding, buyer-caused change, lock/MDM, counterfeit, missing item, or unresolved claim. Then determine the appropriate resolution under applicable law, platform rules, payment-provider requirements, and your stated policy. Options may include troubleshooting, return for inspection, full refund, partial resolution, replacement, repair, supplier escalation, or denial when evidence supports it. Keep the financial and inventory states separate. 'Refund approved' does not necessarily mean money has been received from a supplier. 'Buyer refund issued' does not necessarily mean the item has physically returned and can be restocked. Wrong-spec cases deserve precise evidence. Show what was ordered versus what was received using invoice/listing, serial, system information, and photos. Neutral documentation is stronger than anger. Close the case with a process lesson. If one supplier repeatedly sends wrong storage, change the supplier score and verification requirement.

Worked example

You order a 512GB iPad and receive 128GB. Preserve the listing/invoice, order number, shipping label, serial, and Settings screenshot showing 128GB. State the discrepancy plainly and request a specific remedy. Do not argue about motives; prove the mismatch.

Practical checklist

  • Exact transaction/unit
  • Complaint/evidence
  • Classification
  • Applicable rules
  • Resolution
  • Return status
  • Refund payment status
  • Inventory outcome
  • Supplier impact
  • Process lesson

Common mistakes

  • Refunding before identifying the unit
  • Treating approved refund as received cash
  • Restocking before item returns
  • Arguing emotionally instead of documenting discrepancy

Key takeaways

  • Returns are a workflow, not one status
  • Evidence improves resolution
  • Every case should create a process lesson
Put this into practice

Draw a refund decision tree for defect, wrong spec, shipping damage, buyer-caused damage, and unresolved cases.

Before you finish

You can track a refund from complaint to money movement to inventory outcome separately.
Next lesson

Progress is saved on this device; no account required.