All guides

Published

US TikTok Claim Evidence Pack Template

A TikTok claim evidence pack template is a reusable file set that lets a US TikTok Seller Center reviewer reproduce your request: order ID, claim type, expected vs. actual USD amounts, supporting settlement rows, tracking or refund proof, the policy basis, and a short request statement. Build one pack per claim before you open a ticket.

TikTok Seller Center (US) and U-PIC reviews move faster when the reviewer does not have to reconstruct your math from scattered screenshots. An evidence pack is not a dump of every file you own—it is the minimum set that proves the unexplained difference for one order and one claim type.

Use this template after payout reconciliation has already isolated a candidate. Filing without a pack often leads to “insufficient evidence” replies even when the underlying discrepancy is real.

What do TikTok Seller Center reviewers typically need?

Reviewers need a complete story for a single claim, not a shop-wide narrative. Every pack should answer four questions in order:

  1. Which order and claim type is this?
  2. What amount do you expect, what posted, and what is unexplained?
  3. Which export rows or tracking events support that math?
  4. Which current US policy or program makes the request eligible?

If any answer is missing, the ticket usually stalls. Keep one claim per pack. Mixing a shipping fee discrepancy with a lost-in-transit reimbursement on the same order creates two different evidence requirements and two different filing channels.

Which exports belong in every evidence pack?

Prefer structured exports over screenshots whenever Seller Center allows a download. Exports are searchable, comparable across statements, and easier to attach without cropping errors. For how to audit those files before filing, see the settlement CSV audit guide.

ExportWhy it belongs in the pack
Order detail or order list rowConfirms order ID, SKUs, paid amount, and key dates
Settlement / finance transactions for the orderShows every debit, credit, fee, and later adjustment
Shipping or logistics recordSupports rate, package, or tracking disputes
Refund record (if relevant)Ties admin fees or refund reasons to the SKU
Prior ticket or claim historyPrevents duplicate filings and explains prior decisions

For each export, keep the original file name, export date, and the filter used (order ID, date range, shop). When you paste rows into a working sheet, retain a copy of the raw export so the reviewer can verify you did not alter amounts.

Which screenshots and tracking records should you save?

Screenshots fill gaps that exports omit—especially carrier portals, Seller Center UI states that do not export cleanly, and time-sensitive status pages.

Save:

  • the Seller Center order page showing fulfillment method and current status;
  • tracking history with carrier, tracking number, acceptance scan, and last event;
  • carrier POD or delivery photo when the claim is delivered-not-received;
  • damage photos when the claim is logistics damage;
  • the rate, measurement, or fee screen that supports a shipping dispute; and
  • the policy or help-center page you relied on, captured on the day you filed.

Name files with the order ID and role (ORDER123_tracking.png, ORDER123_settlement.csv). Ambiguous names waste review time and make handoffs between ops teammates unreliable.

How should you structure the claim evidence pack template?

Use the same folder layout for every claim so your team can assemble packs without reinventing the checklist, one subfolder per order and claim type:

  • 00_summary — request statement plus expected vs. actual amount;
  • 01_order_export — order detail or order list row;
  • 02_settlement_rows — settlement / finance transaction export;
  • 03_tracking_or_refund — tracking history or refund record;
  • 04_policy_reference — the policy or help-center page relied on; and
  • 05_extra_docs — photos, delivery proof, and prior ticket history.

Put the summary first. Reviewers and teammates should see the ask before opening attachments. The summary should include:

  • shop name and TikTok Shop ID if available;
  • order ID and claim type;
  • fulfillment method (TikTok Shipping, FBT, or Seller Shipping);
  • filing channel (Seller Center vs U-PIC vs carrier);
  • expected amount, actual amount, unexplained difference;
  • calculation in one short paragraph;
  • list of attached files; and
  • confirmation that you searched later settlements for an offset.

This mirrors the expected-versus-actual discipline used in the refund admin fee overcharge guide.

What fields change by claim type?

The core template stays fixed. Only the supporting evidence layer changes:

Claim typeExtra evidence to attach
Shipping fee discrepancyDeclared vs carrier-verified measurements, rate basis, buyer contribution, later shipping credits
Lost in transitTracking with last scan, waiting-period notes, refund/replacement outcome, value support
Delivered not received (DNR)Delivery confirmation, POD/photo if available, buyer non-receipt reason
Logistics damagedClear product damage photos, packaging condition if available
Refund admin feeSKU-level referral fee, refund date, 20% / $5-cap math, exception check
Return protectionReturn tracking, protection enrollment status for that order, return incident type

Do not reuse a lost-parcel photo set for a fee math dispute, and do not file a Seller Shipping carrier billing issue through TikTok merely because the order originated on TikTok Shop. Channel choice belongs in the summary before you attach files.

Which missing items delay or sink claims?

These omissions cause the most avoidable rejections and follow-up loops:

  • No order ID on the summary or file names.
  • Expected amount stated without the calculation.
  • Settlement rows from the wrong statement period.
  • Failure to check later settlements for a credit already posted.
  • Wrong fulfillment method / wrong filing channel.
  • Tracking without a carrier acceptance event on a lost-in-transit pack.
  • Damage claim filed without photos.
  • DNR claim filed without delivery proof.
  • Policy link missing or from a different market.
  • Multiple unrelated claim types stuffed into one ticket.
  • Request amount that exceeds the program cap without explanation.
  • Screenshots only—no export rows when exports were available.

Build the pack as soon as the anomaly appears, even if a waiting period has not expired. Tracking pages and UI states change; early captures preserve the evidence you may need later.

How do you write the claim request statement?

Keep the Seller Center message short enough to paste, and specific enough to stand alone:

Order [ID] ([claim type]). Expected [amount] based on [one-line calculation / policy basis]. Actual related settlements total [amount]. Unexplained difference: [amount]. Attachments include order export, settlement rows, [tracking/refund/photos], and the policy reference. Please review and credit the unsupported difference, or explain the calculation used.

Rules that keep wording usable:

  • lead with facts, not adjectives (“unsupported difference,” not “you overcharged us again”);
  • use USD amounts with two decimals;
  • name the claim type once;
  • point to attachments instead of pasting long tables into the ticket body; and
  • ask for review or explanation when eligibility is medium confidence, not only for an immediate credit.

Copy the final statement into the 00_summary file so the same wording is used if a teammate files the ticket later.

How does RecoverPayout generate evidence packs?

RecoverPayout runs deterministic reconciliation on US TikTok Shop order and settlement data, then builds a per-claim evidence pack with order ID, expected vs. actual amounts, tracking or refund fields when present, policy references, and required-doc hints (for example damage photos or delivery proof on low-confidence logistics claims).

You still file in TikTok Seller Center (US) or U-PIC yourself—RecoverPayout does not submit tickets on your behalf. The product surfaces candidates in a claims queue so you can review, copy claim wording, attach any seller-supplied documents, mark filed, and track recovery.

Browse all RecoverPayout guides or see how RecoverPayout detects and tracks reimbursements.

Sources and policy note

This guide addresses the US market. Confirm current US policy, fulfillment method, transaction date, and TikTok Seller Center (US) or U-PIC instructions before filing. Required documents, claim paths, and program labels can change.