Help CenterInventory

Inventory Tools

Use Inventory Tools

Use Inventory Tools for imports, failed-row review, exports, barcode work, and inventory maintenance workflows.

Before you start

  • Keep exact marketplace identifiers, card names, sets, collector numbers, conditions, finishes, quantities, and warehouse information when the source file provides them.
  • Keep a copy of the original file before importing.

What success looks like

  • Successful rows create or update inventory.
  • Failed rows show errors that can be fixed.
  • Exports and barcode tools produce files you can use outside MintLGS.

Quick start

The shortest path through this area.

  1. 1Open Inventory > Inventory Tools.
  2. 2Choose Import, History, Export, Audit, or Barcode Sheets.
  3. 3For imports, upload the file and map columns if prompted.
  4. 4Review preview rows and warnings before starting.
  5. 5Run the tool.
  6. 6Review the result, especially failed rows or warnings.
  7. 7Correct failed rows and reimport only the corrected data when possible.

Common tasks

Open only the task you need.

Import inventory from a CSVThe preview and backup stages protect the current inventory before rows are changed.
  1. 1Choose Import and select the job type: card inventory, price update, warehouse transfer, products, or price-review updates.
  2. 2Upload the file and let MintLGS detect its columns. Set the game and warehouse only when the file does not provide them.
  3. 3Review recognized rows, warnings, unknown cards, price changes, and the sample data. Do not continue while the preview is materially wrong.
  4. 4Start the import. You can leave the page; History records the job and its outcome.
  5. 5Open Import Details, review the summary and failed rows, and keep the backup until the result has been checked in inventory.
Resolve identifiers and unknown cards safelyExact external identifiers are safer than name-only matching, but different identifiers describe different levels of a card.
  1. 1Prefer a marketplace SKU when the file provides one because it can identify a specific condition or finish; a general product ID usually identifies the card printing but not the exact marketplace SKU.
  2. 2Keep card name, set, collector number, condition, finish, and language columns when available so MintLGS can cross-check the identifier.
  3. 3Review Recognized Rows Missing Catalog Matches, Warnings, and Rows That Will Fail before importing.
  4. 4Do not force an uncertain match. Correct the source row or import only the rows that were resolved confidently.
Undo a bad importRestore is for a recently completed import whose results were not what you expected.
  1. 1Stop staff from making related inventory edits while the restore is evaluated.
  2. 2Open History, choose the import, and compare its summary with the file you intended to use.
  3. 3Choose Restore from Backup and read the confirmation carefully.
  4. 4After the restore completes, check several affected cards or products and their warehouse quantities.
Complete a price-review CSVThe price-review export is an action sheet, not a general inventory price import.
  1. 1Open the Price Review import/export area and export the currently flagged rows.
  2. 2Enter a Custom Price or put yes in one action column for each row you intend to resolve; leave all action fields blank to leave a row unchanged.
  3. 3Upload the reviewed file and inspect the action preview and any errors.
  4. 4Import, then confirm updated, dismissed, skipped, and no-longer-flagged counts.
Audit inventory dataUse the audit to find missing or inconsistent store inventory information.
  1. 1Open Inventory Audit and run the available checks.
  2. 2Review each group by severity and fix customer-visible problems first, such as missing prices, images, or sale eligibility.
  3. 3Open the affected inventory area from the result when available.
  4. 4Run the audit again after corrections and confirm the issue count falls.
Print product barcode sheetsBarcode Sheets creates labels for products that staff need to scan.
  1. 1Open Barcode Sheets and search for the products.
  2. 2Select the correct product or variant and quantity of labels.
  3. 3Preview the sheet before printing.
  4. 4Print one test page and scan a label in POS before producing a large batch.

How this area works

Reference information for the choices on this page.

Import workflow
  • Let MintLGS detect a supported marketplace format, then review every automatic column mapping.
  • Review the analysis summary, recognized rows, missing catalog matches, warnings, failures, warehouse choice, quantity mode, and pricing behavior.
  • Use failed-row output to correct only rows that need work.
Common import fields
  • Marketplace SKU or product identifier when available, plus card name, set, and collector number for verification.
  • Condition, finish or printing, language, and game.
  • Quantity, quantity mode, and warehouse.
  • Product name, SKU, barcode or UPC, variant information, and price for non-card products.
Actions in Inventory Tools
  • Use Import to upload card inventory, price updates, warehouse transfers, products, or a pricing-review action file.
  • Use History to review import status, inspect row counts, open Import Details, download backups, and restore an eligible import.
  • Use the Pricing Before Import prompt to decide whether imported rows should use automatic pricing or prices from the CSV.
  • Use Import Details to review import configuration, row statistics, operational summary, failure details, backup information, and restore options.
  • Use Audit to run selected data-completeness checks for singles or products.
  • Use Barcode Sheets to search available products, select labels, and print barcode sheets or label-maker output.
  • Use Exports to download card inventory or product inventory with filters such as TCG, warehouse, product type, or search text.
  • Use Price Review import/export for the automated pricing review CSV workflow from Pricing.
  • Use Product Import review when UPC or product matching needs human confirmation before creating products or inventory.

Troubleshooting

Choose the symptom that matches what you see.

Many rows failed

Check identifier type, required column mappings, invalid quantities or conditions, and rows where the identifier conflicts with the card name, set, collector number, finish, or language.

Inventory imported to the wrong warehouse

Pause before importing more files. Review the import result and contact support if you need help correcting a large import.

Continue with a related guide

Manage TCG SinglesManage ProductsUse Pricing

Still stuck?

Open a support ticket. We’ll include this guide so you only need to explain what happened and where you got stuck.

Sign-in is required to protect store information.

Open support ticket