ZocumentsOn this page
This dispute is about representation and what was actually delivered — not about whether a package scanned as delivered.
Useful records let a reviewer compare the listing or scope the customer saw, the item or work delivered, and any remedy you already offered.
Zocuments only organizes the facts and files you provide. It does not judge whether the listing was accurate.
Records that usually help
Usually helps
- Original listing or scope. The product page, invoice scope, photos, SKU details, or agreement the customer accepted before purchase.
- Delivered item or completed work proof. Delivery photos, a signed completion, inspection notes, or customer acceptance of the work as performed.
- Remedy offered. A return label, replacement, troubleshooting, or refund offer shows you addressed the complaint before the chargeback.
- Refund or return policy. Only the policy shown before purchase, and only the section that applies. Do not attach an entire terms document.
Usually does not help
- Tracking alone. Proof of delivery answers a non-receipt claim. It does not show that the delivered item matched the listing.
- Marketing claims added after the sale. A reviewer needs what the customer saw at checkout, not later copy.
Processor notes
File limits, deadlines, and outcomes come from your processor. These notes summarize public help articles; check the portal for the case in front of you.
How this looks in a packet
The packet should put the listing next to proof of what was delivered, then any remedy, so a reviewer can compare them without hunting.
-
A
Original listing or scope
the product page or signed scope from checkout.
Supports: Original listing or scope -
B
Delivered item or completed work proof
photos or a completion record.
Supports: Delivered item or completed work proof -
C
Remedy offered
the return, replacement, or refund offer you sent.
Supports: Remedy offered
