product import & export — on autopilot
Product Import & Export.
Supplier feeds in, marketplace listings out, and your store always right in the middle – prices, stock, images and descriptions moving between systems on a schedule instead of through a spreadsheet at 11pm. Built on the platforms you already sell through.
01 · the problem
Your catalogue is a spreadsheet someone re-types.
The supplier sends a CSV. Someone opens it, fixes the headings, strips the lines that don't apply, resizes the images, pastes it into the store, and does it again next month – by which time the prices have changed and three lines are out of stock. Multiply by every supplier and every marketplace, and the catalogue is a full-time job that's always slightly wrong.
What changes
- Supplier feeds pulled and cleaned automatically – CSV, XML, an API, or the spreadsheet they email you
- Prices and stock updated on a schedule, not when someone remembers
- One product record feeding your store and every marketplace
- Every change logged, so you know what moved and when
fig. 01 · the catalogue · illustrative
bay 01 · powered
02 · how it works
Feed in. Store right. Listings out.
We map each supplier's format to your product model once – headings, units, categories, image rules, the margin you want on top – and the automation applies it every time the feed changes. Your store becomes the single source of truth, and the marketplaces are fed from it: Amazon, eBay, Google Shopping, whichever you sell on.
Under the hood
- Supplier imports: CSV, XML, API, email attachments, FTP
- Cleaning and mapping: SKUs, categories, units, variants
- Pricing rules: margins, rounding, currency
- Image fetching, resizing and naming
- Marketplace exports and feed files, kept valid
- Every run logged; a failure alerts a person
fig. 02 · the pipeline · illustrative
bay 02 · powered
03 · what you get
A catalogue that's right every morning.
Stock that matches what the supplier actually has, prices that follow the cost, listings that stop being flagged by the marketplace – and the person who used to do it doing something that needs a person. It compounds: every supplier and channel you add reuses the mapping that already exists.
In the box
- Imports built for each supplier, on a schedule
- Your store connected as the single source of truth
- Marketplace exports and shopping feed files
- A dashboard of runs, changes and errors
- Mapping changes as suppliers change their files, included
fig. 03 · updates per month · illustrative
bay 03 · powered
04 · the offer
One setup per source. One flat monthly. No contract.
Setup is per supplier and per channel: we map it once, run it beside a manual pass, and switch it on. The monthly covers scheduling, monitoring, fixes and the mapping changes suppliers force on you. We give you the figure on the call, once we know how many sources and channels you have.
- 01
Setup
Each supplier feed and each marketplace mapped, tested beside the manual version, then switched on.
- 02
Monthly
Scheduled runs, monitoring, alerts, fixes and mapping tweaks. One flat figure.
- 03
Term
Month to month. The mappings and the connections stay yours, documented.
05 · questions people ask before they say yes
Which platforms does it work with?
Shopify and WooCommerce as the store; Amazon, eBay, Google Shopping and most marketplaces on the way out. On the way in, anything a supplier can send – CSV, XML, an API, an FTP folder or a spreadsheet attached to an email. If it has structure, we can map it.
What about a supplier who keeps changing their file?
It happens constantly. The run fails safely, we get the alert, we adjust the mapping and re-run – that's what the monthly is for. Nothing half-imported ever reaches your store.
Can it set prices?
Yes, from rules you own: cost plus margin, rounding to .99, per-category exceptions, currency conversion. Change the rule and the next run applies it everywhere.
What about images and descriptions?
Images are fetched, resized and named to your store's standards. Descriptions can be passed through, templated, or – where a supplier gives you nothing – drafted by AI from the specification for you to approve.
Will it overwrite things I've edited by hand?
Not unless you want it to. Every field is owned by one side: supplier-owned fields like stock and cost update automatically; store-owned fields like your titles and your copy are left alone.
How long does the first supplier take?
One to two weeks for the first, including a run beside your manual process. The second is quicker, because the store side already exists.
Can I stop?
Yes, monthly. The mappings, the connections and the documentation stay yours.
next step
Fifteen minutes to see whether your catalogue is worth automating. If it isn't, we'll say so and you've lost a coffee break.