Data Import & Linking

Your data,
whatever shape it's in.

Nobody's product data is one tidy file. It's an export plus an image list plus a stock sheet, with three columns you'd rather nobody saw. Bring all of it in, join it up, and throw away the rows you don't want listed.

  • CSV upload, a URL we fetch, FTP, or a JSON/API endpoint
  • Or pull straight from a connected Shopify, Amazon, eBay or Etsy account
  • Join several files on a shared key — including attribute-per-row exports
  • Filter out junk rows and see the effect before you commit
3 files linked · 12,904 rows Ready
Base file products.csv — keyed on SKU
Linked images.csv, attributes.csv (name/value)
Filtered out ~1,180 rows: no image, price 0
Re-fetches and re-runs on your schedule

Where your data can come from

Pick a source once and the journey remembers it, so the next run is a re-fetch rather than a re-upload.

A file you have

Upload a CSV and get on with it. Your original filename is kept, so a month later you still know which export it was.

A URL or FTP path

Give us the location your supplier or ERP publishes to — with credentials where needed — and each run collects the current version.

A JSON endpoint

Point at an API that returns your products and we'll read it like any other feed — no middleware to write.

A store you already run

Connect Shopify, Amazon, eBay or Etsy and import from there directly — no export step in the middle.

Files that only make sense together

Most catalogue exports are relational whether they admit it or not. Rather than making you flatten them in Excel first, nominate one file as the base and link the others to it.

1

Choose a base

The file with one row per product. That's what a listing will be built from, and what the other files attach to.

2

Link on a key

Say which column in the base matches which column in the other file — usually SKU or a product id. Add as many linked files as you need.

3

Check the preview

A sample of joined rows is shown before you go further, so a mismatched key is something you catch in seconds rather than after a full run.

Attribute-per-row exports, handled

The awkward format where each row is one SKU, one attribute name and one value — common in ERP dumps — is pivoted into real columns for you. Tell us which column holds the name and which holds the value; that's it.

Column mapping with a head start

Your columns rarely share names with marketplace fields. The mapping step proposes matches for you to confirm or change, and marks which target fields are genuinely required rather than nice to have.

Don't list the rows you never meant to

Discontinued lines, placeholder SKUs, zero-price rows, anything without an image — every real export has them, and they're the ones that generate support tickets.

Rules, not scripting

Build skip rules on any column — equals, contains, greater or less than — and combine them with "all must match" or "any of these".

Quick Scan

An instant estimate of how many rows your filters would drop, updated as you type — so you can tell a useful filter from one that would empty your catalogue.

Applied on every run

Filters belong to the import, not to one upload, so tomorrow's fetch is cleaned exactly the same way without you re-doing anything.

FAQ · Updated weekly

Frequently Asked Questions

Formats, scale, scheduling and what happens when a feed changes under you.

Still wondering?

Our team replies within a few hours, Mon–Fri.

01 Do my columns have to be named anything in particular?
No. You map your columns to marketplace fields in the wizard, and the mapping step suggests matches to start from. Required fields are marked as required and optional ones as optional, so you know what actually has to be filled before you can continue.
02 How big a file can I import?
Catalogue scale. The wizard works from a sample of your file so every step stays instant, and the full file is only processed when the import actually runs — in chunks, in the background, with progress you can watch.
03 Can imports run automatically?
Yes. An import is a job with a schedule: it re-fetches your URL or FTP source, re-applies your mapping, links and filters, and processes what's changed. Uploaded files are the one exception — there's nothing to re-fetch, so those runs are manual.
04 What happens if I change a step I already completed?
The steps after it are cleared rather than left holding stale decisions. Change your source file and your old column mapping doesn't quietly survive against columns that no longer exist — you're walked back through the affected steps.
05 Is it safe to give you a URL from my own network?
We only fetch from public internet addresses. A feed URL that resolves to a private or internal address is refused rather than followed — on the first fetch and on every scheduled one after it — so a supplier link can't be used to reach somewhere it shouldn't.
06 Does importing create listings straight away?
No. Import brings your data in and stages it. Turning that into listings is the AI listing builder step, which you review and publish yourself — or, if you only want to move prices and stock on products that already exist, the lighter sync job.

No questions in this category.

4 of 6 questions
All systems normal · 99.98% uptime

Your single
command center
for every marketplace.

Connect Amazon, eBay, Shopify and Etsy in minutes. Centralize inventory, automate listings, and let AI handle the busywork — so you can focus on selling more.

No hidden fees Cancel anytime Setup in 4 minutes
Syncing your channels
Inventory In sync
22 variants
across your platforms
Amazon Amazon 8 active
eBay eBay 6 active
Shopify Shopify 5 active
Etsy Etsy 3 active
AI Pricing +12% margin
Orders today 147 · 2 channels