Sellers need an evidence pack before the dispute clock runs out

Start before the case exists

Most seller dispute losses are not "the buyer lied." They are "we could not produce what the portal asked for in time." Tracking screenshots in iMessage, a packing photo on someone's phone, and a PDF invoice with the wrong order id do not become a winning file under a 48-hour clock.

A dispute portal is not a place to invent your filing system. Build the pack while the order is still ordinary.

Checklist: capture at ship

Require these artifacts for categories that attract empty-box and INR claims (electronics, cosmetics, limited drops—name your own list):

1. Pack-bench photo — contents visible, order id in frame or in filename metadata your system stores.
2. Weight at label — system weight vs expected; flag outliers before carrier scan.
3. Carrier scan chain — accept that "delivered" alone is weak for empty-box; keep the scan history export path documented.
4. Seal / tamper note — if you use taped seals or serialized bags, record which seal id left the bench.
5. SKU unit scan — ties the dispute to what you claim you shipped (see packing integrity notes elsewhere).

If you cannot capture (1) at volume, pick the SKU families where claim rate hurts and start there. Perfect is not the bar; repeatable is.

Checklist: what the portal actually accepts. Every channel is picky. For each marketplace you sell on, document in one place:

• Accepted file types and max size
• Whether a tracking page URL is enough or they want a carrier PDF
• Whether buyer messages must be exported a certain way
• Whether policy distinguishes INR, empty box, and damaged
• The exact clock (business hours? seller timezone?)

Link that doc from the seller's case view. Do not make a first-time seller discover this in a help center maze while the timer runs.

Checklist: ownership and the clock

Name roles, not heroes:

• Assembler — pulls the pack from order storage (usually ops or a seller tools queue).
• Reviewer — confirms the files match the case reason before upload (can be the same person on a small team; still name the step).
• Uploader — the login that submits to the portal (personal seller logins that vanish when someone quits are a silent failure mode).
• Escalation — who decides to refund vs fight when evidence is thin.

Put the deadline on the case record as an actual timestamp your queue sorts by—not "soon" in Slack.

Checklist: after you win or lose

Whatever the outcome, write one line back onto the order: reason code, evidence used, result. That line trains the next pack and the next category policy. Without it, you will re-litigate the same empty-box pattern every quarter.

If you lose because a photo was blurry or a weight was missing, that is a process bug, not bad luck. Fix the capture step before you hire another person to write nicer appeal essays.

Multi-seller marketplaces should offer the pack as a downloadable checklist inside the seller hub, not only in a help article. The sellers who need it most are the ones who do not read help centers under stress.

For your own first-party store facing chargebacks, the same discipline applies with different portals (card networks, PayPal, Shop Pay disputes). The artifact list changes; the rule does not: capture at fulfill time, assemble under a clock, name the uploader.

Do not weaponize evidence packs against good-faith buyers. The goal is fewer indefensible losses and fewer slow-motion arguments—not a culture that fights every claim. When evidence is thin, refunding quickly is often cheaper than a heroic appeal.

Teach the pack once

New sellers lose disputes because nobody showed them the portal's picky upload rules during onboarding. Add a five-minute module: here is an empty-box case, here are the files that win, here is the button, here is the clock. Quiz them with a fake case before their first real one.

If you operate the marketplace, instrument how often cases close as "seller did not respond" versus "evidence insufficient." Those are different failures. The first is routing and notification; the second is capture quality. Fixing the wrong one wastes a quarter.

Keep legal review out of the critical path for routine INR templates, but give counsel a yearly pass on the evidence list so you are not asking sellers to upload something policy forbids.

When a 3PL ships on the seller's behalf, decide who captures the pack photo—the 3PL's bench or nobody. Contracts that are silent on evidence create cases that are unwinnable by design. Write the artifact requirement into the 3PL SOP and sample it monthly.

Buyers who reopen the same dispute after a partial refund need a linked case history in the seller view. Without it, each agent rebuilds the story and may upload contradictory files.

Store evidence with the same retention you need for tax and consumer law in your markets—not "until the phone fills up." Phones as systems of record fail audits and fail quits. Prefer order-linked object storage with access control over personal camera rolls, even when the photo originates on a phone.

If buyers can open cases in multiple channels (marketplace portal plus email plus chat), map each channel to the same evidence pack. Fragmented cases are how sellers upload twice and still miss the deadline once.

Sample five closed cases each month with a simple scorecard: artifacts present at open, uploaded before deadline, outcome. Share the scorecard with ops and seller success. Trends beat anecdotes when you ask leadership for pack-bench camera time.

Name one owner for the evidence-pack template the way you name an on-call. When portals change upload rules, that owner updates the checklist within a week—not after the next wave of losses.

Put this into practice

Open three closed disputes from last month. For each, list the files you wished you had at hour one. That wish list is version one of your evidence pack. Wire capture into ship confirm for one category this week.

We build marketplaces where sellers can defend a case without inventing a filing system under fire. If your portal clock keeps beating your photo roll—talk to us.

Related work: Paddle8.