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.
Pick a source once and the journey remembers it, so the next run is a re-fetch rather than a re-upload.
Upload a CSV and get on with it. Your original filename is kept, so a month later you still know which export it was.
Give us the URL your supplier or ERP publishes to — with credentials where needed — or have it drop files in your SFTP folder with us. Each run collects the current version.
Point at an API that returns your products and we'll read it like any other feed — no middleware to write.
Connect Shopify, Amazon, eBay or Etsy and import from there directly — no export step in the middle.
Moving from another tool? See how to bring your listings with you.
Not everything starts as a feed. The + Add products menu on the Products screen covers the rest.
Type in the title, photos, price, stock and channels, and add its variants in the same panel. AI then picks each channel's category.
Start from one you already sell. Photos, description, price and channels are copied; you give it a new SKU. A channel it is already listed on reuses that category, so it is not paid for twice.
Copy up to 200 rows from Excel or Google Sheets and paste them in. Each row is checked before import, and a SKU you already have is skipped.
Upload up to 10 photos and AI drafts the product from them — one AI credit per product. You check every field it wrote before you save.
A spreadsheet (CSV or XLSX), a supplier feed by URL or SFTP — once, hourly or daily — or a connected marketplace, all from one place, with a preview before you start.
An import can also update products you already have with the same SKU. You choose what changes: title, description, photos, price or stock.
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.
The file with one row per product. That's what a listing will be built from, and what the other files attach to.
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.
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.
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.
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.
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.
Build skip rules on any column — equals, contains, greater or less than — and combine them with "all must match" or "any of these".
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.
Filters belong to the import, not to one upload, so tomorrow's fetch is cleaned exactly the same way without you re-doing anything.
Formats, scale, scheduling and what happens when a feed changes under you.
No questions in this category.
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.
Shopify
5 active
Etsy
3 active