TCGplayer keeps each refund on its order. That works for one buyer message, but not for understanding a month of refunds. A seller refund tracker brings the orders together without losing who started the refund, what it cost, or which cards need inventory reconciliation before any restock.
The Seller Portal is the source of truth. Open Orders, find the order, and you can see the refund there. TCGplayer records whether it was full or partial, who initiated it, and why—cancellation, missing package, condition issue, inventory issue, and so on.
That answers “what happened to order 123?” It does not quickly answer “how many inventory-issue refunds did we have this quarter?” or “which returned cards need a count before they return to stock?” Once order volume gets high, the problem is less about finding a refund and more about not losing the pattern. Use the cancellation and refund reconciliation checklist for the stock decision on a specific order.
TCGplayer can record a refund initiated by its customer-service team. A seller who watches messages but rarely reviews old orders may not notice the business effect right away. The refund is still in the Seller Portal; it was overlooked, not hidden.
That distinction matters. Hoard is not uncovering a secret ledger. It runs a dedicated refund pass, brings seller-, buyer-, and TCGplayer-origin refunds into one Returns view, and keeps each one tied to the original order and buyer. You can still open TCGplayer when you need the official record.
A refund changes net sales. It may also create inventory work, but those are not the same event. TCGplayer's refund screen asks whether inventory should be adjusted and how many copies should return. If Live quantity is zero, the copy can go to Staged instead.
So a clean refund review asks two plain questions:
Monthly refund dollars alone cannot answer the second one.
Pick the last 30 days. Split full refunds from partial ones, then group by origin and reason. Seller cancellations belong in a different pile from buyer condition complaints. TCGplayer-origin decisions deserve a look at the original order and messages.
After that, look for repetition: the same buyer, game, set, condition, shipping method, or employee handoff. One refund is an incident. Five with the same shape are a process problem.
Finish with the cards. Every refunded product should have an answer you can say out loud: “back in Live,” “waiting in Staged,” “buyer kept it,” “lost in the mail,” or “returned damaged.” If the answer is “I think it came back,” it belongs on the count list.
Use this on the next review: download the refund and restock reconciliation worksheet (CSV). It keeps the money decision, Live/Staged quantity, physical status, owner, and next action on one row.
Hoard collects refund records on its sync schedule and lets you filter them with their order, buyer, product-line, and available item detail. It can surface repeat-refunder patterns and build a restock pull sheet. It cannot reverse a refund, settle a dispute, or decide whether a returned card is sellable.
It is also not real-time. A refund made after the last successful sync will not appear until the next one. When a live customer issue is in front of you, use TCGplayer. When you're trying to understand the store, use the combined view.
For the stock side of the job, keep the cancellation and refund reconciliation checklist nearby. For the monthly numbers around the same orders, use TCGplayer sales analytics.
The Seller Portal is the source of truth — open Orders, find the order, and the refund is recorded there, including whether it was full or partial, who initiated it, and the reason. That view answers what happened on one order; it doesn't roll up a pattern across a month on its own.
Not automatically. TCGplayer asks whether inventory should be adjusted and how many copies should return, and when Live quantity is at zero, a returned copy can land in Staged instead of Live and sit there until someone moves it.
Usually not hidden at all. TCGplayer can record a refund its own customer-service team initiated, and a seller who doesn't review old orders regularly can miss the business effect. It's still in the Seller Portal; it was overlooked, not concealed.
A monthly 30-minute pass works for most stores: split full refunds from partial ones, group by origin and reason, then look for repetition — the same buyer, game, set, condition, or shipping method. One refund is an incident; five with the same shape are a process problem.
The Seller Portal is the source of truth — open Orders, find the order, and the refund is recorded there, including whether it was full or partial, who initiated it, and the reason. That view answers what happened on one order; it doesn't roll up a pattern across a month on its own.
Not automatically. TCGplayer asks whether inventory should be adjusted and how many copies should return, and when Live quantity is at zero, a returned copy can land in Staged instead of Live and sit there until someone moves it.
Usually not hidden at all. TCGplayer can record a refund its own customer-service team initiated, and a seller who doesn't review old orders regularly can miss the business effect. It's still in the Seller Portal; it was overlooked, not concealed.
A monthly 30-minute pass works for most stores: split full refunds from partial ones, group by origin and reason, then look for repetition — the same buyer, game, set, condition, or shipping method. One refund is an incident; five with the same shape are a process problem.
See the refund beside its order, buyer, and restock work while somebody still remembers what happened.
Get started freeSource, last checked Aug 22, 2026: TCGplayer: How do I process refunds?. Hoard shows the TCGplayer data available at the last successful sync; use the Seller Portal as the source of truth for a live refund or dispute.