Inventory sync both ways
An Amazon sale reduces the Shopify quantity and a Shopify sale updates the Amazon offer, so the same last unit cannot be sold on both. One stock figure rather than one per channel.
Keeping an Amazon catalogue and a Shopify store in step, through the official Selling Partner API. The packaged integration is in active development. If you need Amazon connected before it ships, we scope and build it against your catalogue — that part is available today.
Running Amazon alongside a Shopify store, handled automatically.
An Amazon sale reduces the Shopify quantity and a Shopify sale updates the Amazon offer, so the same last unit cannot be sold on both. One stock figure rather than one per channel.
Amazon orders arrive in the same fulfilment queue as your Shopify orders, with line items and shipping details intact, so you pick and pack from one screen instead of two consoles.
Shopify products matched to the right ASIN, with the attributes each category requires. Where no listing exists yet, the product is prepared as a new offer rather than silently skipped.
Fulfilled by Amazon stock is Amazon's to count and merchant-fulfilled stock is yours. The two are tracked separately so FBA quantities never overwrite what you hold yourself.
Draft titles, bullet points and attributes from the product data you already have, so a catalogue arriving on Amazon is not thin. You review everything before it publishes.
Through the Amazon Selling Partner API with scoped authorisation. We never see or store your Seller Central password, and you can revoke access from Amazon at any time.
Every marketplace has its own rules, and the ones that matter are the ones that cost you money when an integration ignores them.
On Shopify a product is your record. On Amazon you are attaching an offer to a catalogue entry that may already exist, with attributes the category dictates rather than ones you choose. Matching to the right ASIN is most of the work, and getting it wrong is worse than not listing at all.
FBA inventory sits in Amazon's warehouses and Amazon is the authority on the count. Merchant-fulfilled stock is yours. An integration that treats both as one number will overwrite real quantities with warehouse ones, which is why we keep them apart.
The Selling Partner API meters requests per operation, so a sync has to queue and batch rather than push everything at once. Built well this is invisible; built badly it is why stock updates arrive an hour late.
Both accounts are connected through their official APIs and one stock figure is held per product, so an Amazon sale lowers the Shopify quantity and a Shopify sale updates the Amazon offer. The packaged Amazon integration is in active development; a custom build scoped to your catalogue is available now.
Not as a packaged integration — it is in active development and we are not going to tell you it ships today when it does not. What is available now is a custom build: we scope it against your real catalogue and fulfilment setup and build it for your shop.
Yes. FBA quantities are held by Amazon and merchant-fulfilled quantities are yours, and the two are tracked separately so warehouse figures never overwrite the stock you hold and sell yourself.
Yes. Products are matched to the correct ASIN where one exists, with the attributes the category requires. Where no catalogue entry matches, the product is prepared as a new offer rather than skipped without telling you.
That is the point of the hub. Shopify holds the stock figure and every connected channel reads from it, so adding Amazon to a shop already selling on eBay or Etsy does not split your inventory three ways.
The packaged integration is still in build, but a custom one scoped to your catalogue is not. Tell us how your shop runs and we will scope it against your real listings.
Tell us about your setupTwo-way sync and eBay to Shopify migration, available today. Plans from $19/mo.
Two-way inventory and order sync through the Etsy Open API v3.
What is live, what is in build, and what we will scope for you.
Four steps from connecting a store to the first sync running.