Why TCGplayer sellers oversell (and how to stop it)

Start with the exact listing: game, set or printing, language, finish, and condition. Two copies with the same name are not interchangeable if the buyer ordered a particular version. Then compare the listed count with sellable physical stock and orders already committed against it.

How a shared last copy can sell twice

Illustrative example: one physical copy is listed on two independent marketplaces. A buyer purchases it on the first marketplace. Until the second marketplace receives and applies the quantity change, its listing may still accept an order. Faster polling can shorten that interval; it cannot make two independent checkouts share an atomic reservation.

If your tools cannot reserve that last copy across channels, consider listing it on only one channel or allocating separate physical quantities to each. Verify what happens after a sale in each direction before treating an integration as protection against overselling.

A completed sync is not the same as a verified count

1. Match the exact listing. Check the identifier and variant rather than joining records by card name alone.
2. Account for orders since the last snapshot. A fresh export can become stale while you edit it. Include pending commitments before deciding what remains available.
3. Check returns and Staged Inventory. A refund does not prove a sellable copy came back. Read the cancellation and refund reconciliation checklist.
4. Verify the physical exception. Check the recorded slot, recent moves, and returns area. If the copy is misfiled, correct its location rather than treating it as gone.
5. Read back the changed listing. Confirm the intended marketplace accepted the quantity and that the live count matches the reviewed adjustment.

What Hoard helps you investigate

Hoard's inventory workspace brings TCGplayer listing data and seller controls into one workflow. Its inventory trust checks help prioritize records that need review. Those signals do not inspect the shelf or establish that every external marketplace has applied a stock change.

Do not treat a Hoard store connection as a guarantee of instant quantity synchronization across eBay, Shopify, and a physical register. Confirm the supported integration and its writeback behavior for each channel you actually use. For a suspected mismatch within your TCGplayer records, start with the ghost inventory audit worksheet.

Keep manual corrections small and current

For a CSV quantity correction, use a fresh export and review the signed quantity adjustment before moving it live. Reconcile intervening sales instead of blindly reapplying an old physical count. Keep the original export, the reason for the adjustment, and the verified result together.

Common questions

Why does TCGplayer say I oversold a card?

The available listing count exceeded the copies you could supply. Check the exact variant, physical stock, pending orders, returns, and any other channel sharing the same copies.

Does a faster sync guarantee no oversells?

No. Faster updates reduce the interval during which a count can be stale, but independent checkouts can still accept orders before an update reaches them. Verify reservation behavior or allocate stock separately.

Does connecting Hoard prevent overselling on every marketplace?

Do not assume that. Hoard helps you inspect TCGplayer inventory and investigate discrepancies. Verify support and writeback behavior for each external channel; a store connection does not establish instant shared reservations.

Does exporting and re-importing a CSV stop overselling?

A CSV correction can repair a verified count, but sales after the export can make that snapshot stale. Review pending changes and read back the live listing after publishing.

Source: TCG Sync: TCG Inventory Management Guide