How to import your existing inventory
There are three import paths — from a connected marketplace, from a POS catalogue, or from a CSV file — and they are not interchangeable. Marketplace import is the one that gives SECND the listing IDs it needs in order to delist correctly later.
Last updated
Three import paths, three purposes
| Import from | Use when | What you get |
|---|---|---|
| A connected marketplace | You already have live listings somewhere | Inventory records linked to real listing IDs, so delisting works |
| A POS catalogue (Square, Shopify, Lightspeed) | Your shop floor stock lives in a register | Products with stock levels, kept in sync going forward |
| A CSV file | Your inventory is in a spreadsheet or another tool | Inventory records with no channel linkage until you publish |
The order to do it in
- 1
Connect and import your marketplaces
Highest-volume channel first, then the rest. Each import links existing listings to new inventory records.
- 2
Connect and import your POS
Your floor catalogue comes in with stock levels and stays synced.
- 3
Reconcile overlaps
An item that is both on your floor and on eBay should be one record. Review and merge before going further.
- 4
Import the remainder by CSV
Anything that exists in neither place — back-room stock, a spreadsheet — comes in last, once the linked records are settled.
Preparing a CSV
- One header row, one item per row, values not formulas.
- A unique SKU per row, or leave the column empty and let SECND generate them.
- Separate columns for price and cost — they are different numbers and merging them destroys margin reporting.
- A consistent date format for intake dates.
- A single, consistent consignor identifier if you take consignment.
- Image URLs if you have them hosted; otherwise attach photos after import.
Verify before you trust it
Every import should end with the same three checks: item count matches the source, total retail value matches, and twenty spot-checked items are correct across price, cost, status and consignor. Ten minutes here saves a month of confusing reports.
Frequently asked questions
Will importing create duplicate listings on the marketplace?
No. Import reads what is already live; it does not publish. Duplicates come from publishing a CSV-imported catalogue that describes items you already have listed, which is why import order matters.
Can I import in batches?
Yes, and for large catalogues you should. Batch by channel or by category so that reconciliation stays reviewable and a problem in one batch does not contaminate everything.
Does import bring my sales history?
Order history imports on the channels that expose it. Historical analytics from a different tool does not transfer, so if you need long-run history, keep the export.
What happens to items that fail to import?
They are reported with a reason rather than silently dropped. Fix the underlying field — usually a malformed price, a duplicate SKU or a bad date — and re-run just those rows.
Step-by-step product docs
This guide explains how it works. These show you exactly where to click.
Keep reading
Run it all on one system
Start free. Crosslisting, sale detection and automatic delisting are included, with no card required.