TCGplayer inventory CSV export and import, done right

Exporting your TCGplayer inventory to a CSV, editing it, and re-importing it is a real workflow. Sellers use it for bulk price changes, bulk quantity corrections, and moving inventory data between systems. TCGplayer's own documentation explains where the buttons are. It does not explain the two or three ways this process silently corrupts a listing, or what to check before you trust a re-import.

Sellers already hand-roll this themselves

The CSV round trip is common enough that sellers have built their own tools around it. richardneal/TCGPlayer-Pricing-Tool on GitHub is one example: a small script that automates the export-edit-reimport cycle for pricing. Its own README carries a plain disclaimer: the tool is provided as-is, and "there are no promises made" about it. The commit history is short, and the project hasn't seen active maintenance in some time.

That's the honest shape of a manual CSV workflow: a seller writes a script to solve today's problem, it works until TCGplayer's export format shifts or a listing has a value the script didn't anticipate, and it breaks quietly. A one-person tool with no promises attached is a reasonable stopgap. It's not something you want your live listings depending on indefinitely.

What the CSV actually needs to match

TCGplayer's bulk inventory CSV cares about a small set of fields, and getting any one of them wrong is enough to corrupt a listing on re-import. The fields that matter:

TCGplayer product ID or SKU. This is the row identifier. It's what tells TCGplayer which existing listing a row updates. Every row's ID has to match exactly, or point at nothing, or point at the wrong product.

Condition. TCGplayer expects an exact condition string: Near Mint, Lightly Played, Moderately Played, Heavily Played, Damaged, and the foil variants of each. A condition value that doesn't match one of those exactly, extra whitespace, a different capitalization, an abbreviation, doesn't map to the row you meant.

Printing (foil or non-foil), price, and quantity. These are the values you're usually there to change. They're only safe to change if the row above them, the product ID and condition, is correct.

The most common way a manual re-import breaks existing listings comes from the first two fields, not the last three. A missing or mismatched product ID doesn't fail loudly; it applies your new price and quantity to the wrong row, or to no row at all, while the listing you meant to update sits untouched. A condition value that doesn't match TCGplayer's exact set behaves the same way: the import doesn't reject the row, it just doesn't land where you expected.

The safe way to round-trip a file

Three habits catch most of the damage before it ships:

Export fresh, immediately before editing. Don't reuse yesterday's export. A sale, a manual price change, or a quantity update made anywhere between your last export and now means the file in front of you no longer reflects your live listings.

Never edit a stale CSV. If time passes between exporting and editing, treat the file as stale and export again. Re-importing a stale file re-applies old prices and old quantities on top of anything that changed in the meantime, including sales that already happened.

Reconcile row counts before you reimport. If your export had 12,400 rows and the edited file has 12,398 or 12,406, stop. Rows don't disappear or multiply on their own in a spreadsheet edit; a mismatched count means something got dropped or duplicated, and it's worth finding before the file goes back to TCGplayer.

This is the same round trip whether you're editing quantities or prices. Reimporting a repriced CSV back into TCGplayer follows this exact pattern, an export, an edit, and a re-import, with the same product-ID and condition risks. Get the inventory version right and you've already solved the pricing version.

The manual version is worth understanding even if you don't plan to run it forever, since it's what most sellers reach for first. Once the row-count checking gets old, Hoard's CSV inventory sync runs the same export-and-reimport pattern on a schedule, with product ID and condition matching handled automatically. For where this workflow fits against the rest of an inventory system, see the inventory management guide.

Sources: TCGplayer: How Do I Bulk Upload/Update My Inventory? · richardneal/TCGPlayer-Pricing-Tool