Overselling costs you something you can’t buy back. Point us at the file or the store that knows your real numbers and choose how often to check it. Every channel gets the same stock level and the same price.
Set it up once. After that, every run fetches your source again, so you never re-upload.
Upload a file, give us a URL to fetch each time (with credentials if it needs them), or use a file in your SFTP folder with us. Shopify stores connect over OAuth instead of a file.
SKU is required, because that is how we find your product. Price and quantity are the fields you want moved. Map either or both.
Pick how often the job runs. You set it per job, and the job re-fetches your source each time.
This is deliberately the simplest journey in the product. It doesn’t create listings, doesn’t touch your content and doesn’t need AI.
Map only the column you want moved. The other one is left alone.
A common setup: quantity on a fast schedule from the warehouse export, and price left to a Smart Pricing rule. The two don’t fight each other.
How Smart Pricing worksBecause listing content is never touched, a frequent schedule carries no risk to your titles or images.
Creating or enriching listings is the job of the AI listing builder.
Files, URLs and SFTP run on the schedule you pick. For Shopify sellers there is a faster path: your store tells us, rather than us asking your store.
We fetch your source on the cadence you set and send what changed. For the overwhelming majority of catalogues, 15 minutes is fast enough.
Best when your real numbers live in a file or a warehouse export.
Switch it on when you connect Shopify. Every price or inventory change in the store is pushed out to your marketplaces as it happens. No polling interval to wait for.
Best when your Shopify store holds your real numbers.
Sync is only half of it. The Products screen is where you find out whether the numbers landed.
Find a SKU, see its price and stock per marketplace, and jump straight to the listing.
Open the marketplace’s response for a SKU: the accepted, the warned and the rejected.
Add or correct a SKU directly when the source file isn’t the thing that’s wrong.
Sync failures raise an alert with a retry button, instead of going quietly missing.
| Channel | Price | Qty | Status |
|---|---|---|---|
| PRT-A4-OAK | |||
| Amazon UK | £24.00 | 3 | Accepted |
| eBay UK | £24.00 | 3 | Accepted |
| PRT-A4-WAL | |||
| Amazon UK | £24.00 | 5 | Accepted |
| eBay UK | £24.00 | 5 | Rejected |
When a source goes missing or a row doesn’t match, the sync stops short. It never guesses.
If your file is missing or the URL is down, the run fails rather than treating it as “everything is out of stock”. A file that arrives empty, or with every quantity at 0 after a run that had stock, is held. You get an alert, and your last good numbers stay until the next good file.
A row is tied to a product by its SKU. Rows whose SKU isn’t in your catalogue yet are simply not matched.
Updates are grouped and sent through each marketplace’s own bulk feed. A bulk change in your warehouse becomes a handful of calls, not thousands.
What gets synced, how it’s matched, and what happens when a source goes missing.
Connect Amazon, eBay, Shopify and Etsy in one place.
