Importing Inventory from a File
Already have your cards in another tool? Upload the export and Quick Ship matches every row to a valid card, prices it with your rules, and stages it for review — exactly as scanning does.
Supported Sources
Go to Inventory → Import and pick the tool your file came from. Columns are already mapped for the three named tools — you only map columns for a generic spreadsheet.
| Source | Match accuracy | Column mapping |
|---|---|---|
| ManaBox | Exact printing, including foil | Automatic |
| TCGplayer | Exact printing | Automatic |
| Card Uploader | Exact printing and condition | Automatic |
| Generic CSV | Depends on how much detail your file carries | You map it |
Files must be CSV, up to 20 MB. There's no row limit, and importing doesn't use any of your card scans.
Expected Columns
Export from your tool without renaming anything and these will already be present. Header matching ignores case and surrounding spaces.
| Field | ManaBox | TCGplayer | Card Uploader |
|---|---|---|---|
| Card name | Name | Product Name | Title |
| Quantity | Quantity | Total Quantity | Qty |
| Set | Set name | Set Name | Set |
| Collector number | Collector number | Number | Card Number |
| Condition | Condition | Condition | Condition |
| Foil / finish | Foil | Condition | Variant |
| Catalog id | Scryfall ID | TCGplayer ID | TCGplayer SKU |
Generic CSV: only two columns are required
How Conditions Are Translated
Quick Ship stores conditions as NM, LP, MP, HP and DMG. Whatever your file uses is normalized on import, and a blank condition becomes NM.
ManaBox uses the Cardmarket scale
| ManaBox / Cardmarket | Imports as |
|---|---|
| Mint | NM |
| Near Mint | LP |
| Excellent / Good | MP |
| Light Played / Played | HP |
| Poor | DMG |
Every other source uses the standard scale, where Mint and M collapse to NM. Finishes are normalized too — foil, traditional foil, etched, reverse holofoil, holo, 1st edition and similar are all recognized, and anything unrecognized becomes Non-Foil.
The Import, Step by Step
Pick your source and file
Choose the tool your export came from, then select the CSV. If you picked Generic CSV, you get a mapping step next.
Choose a location
Pick the storage location and, optionally, a starting SKU number. SKUs are minted from the location's composite code — a row in Box TM becomes something like TM-01-0001.
Review and set pricing rules
Pick the pricing rule set for this batch. Every matched row is priced against TCGplayer market price. Check the counts here before committing.
Commit
Rows become live inventory items. This is also where you can list the batch — see Listing to Marketplaces.
Why Your Import Count May Be Lower
An 800-row file can produce fewer than 800 staged cards. That's deliberate: a wrong match costs you more than a missing one, so rows we can't confidently match are left out rather than guessed at.
| Rows left out | How to fix it |
|---|---|
| The card name matches several printings and there's not enough information to pick one | Include a set and card number column — or better, export from one of the three named tools above |
| The card isn't in the catalog under that name or number | Check for typos and set-name differences between your tool and TCGplayer |
| Quantity is zero or blank, or the name cell is empty | Clean those rows out of the file before uploading |
Compare the two counts
How Importing Differs from Scanning
Staging, review, pricing, committing and listing all work the same way either route. Two things differ, and one of them matters a lot.
| Imported | Scanned | |
|---|---|---|
| A row of Qty 4 | One inventory item with quantity 4, one SKU | Four separate items, four SKUs — one per physical card |
| Photos | None | Your scans, kept as listing photos |
| Can list on eBay | No — eBay needs photos | Yes |
| Can list on ManaPool / TCGplayer | Yes | Yes |
If you sell on eBay, that last row is the reason to scan rather than import — a scanned card carries its own front and back photos into the listing.