Two-way sync
Products, prices, stock and orders move between the shop and each marketplace, not in one direction only.
E-commerce
Multichannel inventory management without the spreadsheets
Products, prices, stock and orders kept in step between your store and the marketplaces you sell on.
Stock kept in step · Prices and orders too · Only marketplaces you can reach
Two channels, one pile of stock
A spreadsheet between the shop and the marketplaces is where orders and stock drift apart.
You sell on your own store and on marketplaces. Prices change. A size sells out on one channel and is still offered on another. Orders arrive in different inboxes. Someone copies rows across at the end of the day, and that is the integration.
We connect the store and the marketplaces you sell on, both ways: products, prices, stock and orders. The risk we are reducing is overselling. We confirm API access on the call. If a marketplace doesn't offer it, we'll tell you before we scope it.
The zero-stock rule is written in the brief.
What we build
The fields that drift, kept in step, plus listings that can go out in more than one language.
Overselling
A sale on one channel updates the stock the others can sell, so the same unit is not promised twice.
Marketplace APIs
We use the APIs those marketplaces give you. Access is checked before the scope is fixed.
Listing copy
Listing text can be drafted and translated, English and French first, then checked before it is published.
Categories
Your categories are mapped to each marketplace's categories, so a product does not land in the wrong aisle.
In use
A sale on one channel changes what the others can still sell.
A jacket sells on the marketplace. The shop's stock drops by one before the next visitor adds the same size. The order shows up with the shop's other orders, not in a file someone has to paste in.
How it works
We name the marketplaces first, then the fields that must stay in step.
Call
Which marketplaces, and whether you can reach their APIs.
Brief
Products, prices, stock, orders, and the overselling rule.
Build
The sync, the category map and the listing checks.
Launch
One channel first, then the rest.
Handover
Code, docs and access are yours. We stay on call for 30 days.
What you get, and what we need
You get one picture of stock and orders. We need access and a person who knows the catalogue.
What you get
- Products, prices, stock and orders kept in step.
- A written rule for when stock hits zero.
- Category mapping per marketplace.
- Listing copy in English and French, checked before it goes out.
What we need from you
- The marketplaces you already sell on.
- API access, confirmed before we start.
- Who owns a listing when the text is wrong.
- The catalogue fields that must not drift.
Projects we've worked on
Trade · Stock
Stock and credit ledger
Stock and what is owed sit on one desk.
What's in stock and who owes what, on one desk.
Live shopping
Live shopping app
Viewers check out without leaving the stream.
Live video with real-time chat, a cart viewers build together, custom payments, invoices and the admin behind it.
Related
Questions
Which marketplaces?
The ones you use. We confirm API access on the call, before any scope is written. We do not promise a marketplace whose access we have not checked.
What happens when stock runs out?
Stock is kept in step so a sale on one channel can reduce what the others offer. That is how overselling gets smaller. The exact rule, including what happens at zero, is written in the brief.
Can listings be translated?
Yes. Listing copy and translation can start with English and French, with category mapping and a quality check before a listing goes out.
What should your marketplace integrations do better?
You'll talk to Usama, who'd build it.
30 minutes · no slides · a written answer if it's not a fit