Sync inventory, route orders, and close the fulfillment loop between your Shopify store and Amazon seller account — without the oversells, manual reconciliation, and data gaps that channel apps leave behind.
Talk to an integration expert →Shopify's native Amazon channel and third-party listing apps handle one thing well: getting products listed on Amazon and pulling orders back into Shopify. At low volume, that's enough. At mid-market scale — multiple SKUs, FBA and FBM fulfillment paths, peak trading periods, and an ERP sitting behind both channels — it isn't.
A Celigo-built Shopify Amazon integration covers the full operational layer: real-time inventory reservation across both channels so the same unit can't sell twice, conditional order routing based on fulfillment method, fulfillment confirmation flowing back from Amazon to Shopify, and return processing handled without manual intervention. If NetSuite or another ERP is in the picture, the integration is built to feed that system too — not bolted on afterwards.
The standard channel connector works for simple single-channel flows. Multi-channel sellers at volume face a different set of problems.
The central risk in any Shopify Amazon integration is the same unit selling on both channels simultaneously before inventory counts update. App-store connectors manage this with periodic polling — syncing inventory every few minutes. At volume, a few minutes is long enough to oversell. A Celigo-built integration uses near-real-time inventory reservation logic, updating available counts immediately on each sale event from either channel and applying buffer stock rules where appropriate.
Many mid-market sellers use FBA for standard Amazon orders and their own fulfillment — a 3PL or in-house warehouse — for everything else, including Shopify DTC and Amazon FBM orders. The integration needs to know which orders go where based on channel, SKU, customer location, or stock availability. This routing logic lives in Celigo flows, not in a settings panel.
Amazon identifies products by ASIN. Shopify uses your internal SKU. These don't match by default, and for catalogue-heavy sellers with hundreds of variants, mapping them manually is error-prone. The integration requires a clean mapping table — ASIN to SKU, including all variant combinations — before any product or inventory flow can work reliably.
Sellers operating across Amazon US, EU, and other marketplaces have separate Seller Central accounts per region. Each region is a separate API connection, and inventory allocation rules differ by region. A single Celigo integration can manage multiple Amazon connections, but the scoping needs to cover each region's fulfillment model explicitly.
Most businesses at this scale have NetSuite or a similar ERP sitting behind both Shopify and Amazon. Orders from both channels need to reach the ERP for finance, inventory accounting, and fulfillment. Building the Shopify Amazon integration in isolation — without accounting for how both channels feed the ERP — typically means rebuilding flows later. We scope the full picture upfront, even if we build in phases.
The first conversation covers your fulfillment model: which SKUs are FBA, which are FBM, how you handle inventory allocation between channels, and whether an ERP needs to receive orders from both. This determines the flow architecture before any configuration starts.
Audit your product catalogue and build a clean mapping between Amazon ASINs and Shopify SKUs, including all variant combinations. This is foundational — every other flow depends on it.
Set up real-time or near-real-time inventory flows with buffer stock rules. Define separate inventory pools for FBA-held stock and merchant-held stock so counts stay clean across both channels.
Configure the Amazon SP-API connection in Celigo to pull orders on a defined schedule or via event trigger. Map Amazon order fields to Shopify order fields. Define routing rules for FBA vs FBM orders.
Build the return path — FBA ship confirmations back to Shopify, tracking numbers populated, orders closed correctly. Refund and return events handled automatically without manual intervention.
Define what happens when an inventory update fails, when an order comes in with an unmapped SKU, or when Amazon rate limits a request. Every failure mode gets an alert and a retry path.
Typically 4–6 weeks for a single Amazon marketplace. Multi-region or ERP-connected builds add 2–4 weeks depending on complexity.
Most businesses running Shopify and Amazon at meaningful volume also have an ERP — typically NetSuite — that needs to receive orders from both channels, update inventory, and handle finance. Building the Shopify Amazon integration without accounting for the ERP layer usually means adding it later under pressure.
We build Shopify Amazon integrations as standalone projects and as part of broader multi-system architectures. If NetSuite is in scope, the flows are designed from the start to feed the ERP correctly — Amazon orders to NetSuite, Shopify orders to NetSuite, and inventory positions consolidated across all three systems.
Entech has delivered 200+ integrations on Celigo across ecommerce, ERP, and marketplace systems. For Youth Athletes United, a Shopify integration handling 12,000+ records per hour replaced a manual reconciliation process that had topped out at 200 records per hour. The same approach — webhook-driven flows, proper error handling, and volume testing before go-live — applies to every Shopify Amazon build we deliver.
Tell us your fulfillment model — FBA, FBM, or both — and where the current setup is breaking down. We'll scope the integration and tell you exactly what it covers.