Magento Amazon Integration: Connectors, Cost and Timeline
Amazon rations how fast you can pull orders: getOrders is documented at 0.0167 requests per second with a burst of 20. Whether you buy an extension or build on the Selling Partner API, the integration has to work around those token buckets with notifications and feeds instead of polling.
✦ WHAT SYNCS
What moves between Amazon Seller Central (Selling Partner API) and Magento.
| DATA | DIRECTION | NOTES |
|---|---|---|
| Products and listings | Out of Magento | Catalog and listing data goes to Amazon through feeds or listing APIs. ECOSIRE lists listing sync among its features; Webkul exports simple products only, with SKU, price and quantity. |
| Inventory | Out of Magento | Stock levels are pushed to Amazon, and FBA stock is reconciled against Magento sources (ECOSIRE). |
| Prices | Out of Magento | Prices are pushed to Amazon. Webkul applies fixed or percentage price rules, and M2E lists repricing in its Business and Enterprise plans; the Starter section mentions an Amazon repricing tool, so confirm with M2E. |
| Orders | Into Magento | Amazon orders arrive as native Magento sales orders (ECOSIRE). |
| Shipments | Out of Magento | Shipment and tracking confirmation write back to Amazon. |
| Customers | Into Magento | Buyer data is limited. Operations that return personally identifiable information need a Restricted Data Token. |
✦ THE API
The Amazon Seller Central (Selling Partner API) API.
| ASPECT | DETAIL |
|---|---|
| API type | Selling Partner API (SP-API): HTTP-based, with versioned endpoints per resource, for example Orders v0 and v2026-01-01. |
| Authentication | Login with Amazon (LWA) OAuth 2.0. The LWA access token expires after one hour and goes in the x-amz-access-token header. A Restricted Data Token is required for operations that return PII. |
| Rate limits | A token bucket per operation, per selling partner and application pair. Orders v0: getOrders 0.0167 requests per second with a burst of 20; getOrder and getOrderItems 0.5 per second with a burst of 30; confirmShipment 2 per second with a burst of 10. Orders v2026-01-01: searchOrders 0.0056 per second with a burst of 20; getOrder 0.5 with a burst of 30. Usage plans can be standard or dynamic. Throttled calls return 429, so back off. |
| Documentation | Amazon Seller Central (Selling Partner API) API docs (opens in a new tab) |
✦ CONNECTOR OPTIONS
Connector options.
| NAME | TYPE | NOTES | LINK |
|---|---|---|---|
| ECOSIRE Amazon marketplace connector | Extension | Build-to-order connector on SP-API with LWA OAuth. Listings, inventory and price sync, order import, shipment write-back, FBA and FBM, and multi-region marketplaces. Priced from $999 after a quote request. | Vendor page (opens in a new tab) |
| M2E Pro | Extension | Priced on monthly sales across connected marketplaces (GMV; Amazon, eBay and Walmart combined) as shown on M2E's pricing page: Starter $89/month up to $15K GMV, Business $199/month up to $50K GMV or $399/month up to $100K, Enterprise $799/month up to $200K. Overage is +$6, +$5 or +$4 per extra $1,000 depending on plan. M2E lists repricing in its Business and Enterprise plans; the Starter section mentions an Amazon repricing tool, so confirm with M2E. M2E offers a 30-day free trial. Its Amazon page lists 20 marketplaces, including the US, Canada, Mexico, UK, Germany, France, Italy, Spain, Japan and Australia, and says FBA orders are handled through a separate Magento FBA extension. | Vendor page (opens in a new tab) |
| Webkul Amazon Connector | Extension | Shown at $299.00 on Webkul's store, with a $299.00 add-on for Adobe Commerce editions. Works with Seller Central only and needs SP-API credentials, which means Amazon developer registration and an AWS account. You pick the marketplace per Amazon account, and several accounts can connect. Imports simple and configurable products but exports simple products only. Price and quantity changes in Magento push to Amazon in real time. Products can be exported as FBA products; Multi-Channel Fulfillment is a separate Webkul product. | Vendor page (opens in a new tab) |
| CedCommerce Amazon integration | Extension | CedCommerce shows no price, only a yearly single-license subscription and a Get Quote button. Lists shipment tracking, category mapping, product data validation, a cron scheduler, order management and multi-account support. Its menu has separate Amazon US and Amazon UK connectors, and it does not mention FBA or repricing, so ask for both in writing. | Vendor page (opens in a new tab) |
| Adobe Amazon Sales Channel | Native | Adobe discontinued the Amazon Sales Channel extension effective October 1, 2024, and it is no longer on the Adobe Commerce Marketplace. Adobe points to partner and third-party extensions instead. Treat it as a legacy install only. | Vendor page (opens in a new tab) |
| Celigo (Amazon FBA listed for Magento) | iPaaS | Celigo's Magento page lists Amazon FBA under logistics integrations covering fulfillment, shipping and inventory levels. It does not describe a Seller Central listing sync, so confirm scope with Celigo. | Vendor page (opens in a new tab) |
| Custom build on SP-API | Custom | Direct SP-API integration using notifications and the Feeds or Reports APIs in place of heavy polling, which is what Amazon recommends. | Vendor page (opens in a new tab) |
✦ COST AND TIMELINE
Cost and timeline.
| LEVEL | SCOPE | TYPICAL RANGE | TIMELINE |
|---|---|---|---|
| Level 1 | Connector set up and configured | $3,000-8,000 | 2-4 weeks |
| Level 2 (this integration) | Custom API integration (orders, inventory, customers) | $10,000-25,000 | 4-8 weeks |
| Level 3 | Complex ERP sync (B2B pricing, multiple warehouses, middleware) | $25,000-75,000+ | 8-16 weeks |
Typical range, quoted after a scoping call.
Listing, stock and order sync is level 2 whether you buy an extension or build, mostly because of category and attribute mapping, FBA versus FBM, and marketplace rules. Setup order: get a Seller Central account, register as an SP-API developer (Webkul's connector also needs an AWS account), connect each Amazon account and marketplace, then map categories and attributes before any listing goes live. To choose: check the marketplaces you sell on against each vendor's list, then FBA and repricing, then price. M2E Pro bills on your Amazon sales, so cost rises with volume, while Webkul lists a flat $299.00. An extension is enough for a simple catalog on one or two marketplaces. Webkul exports simple products only, so a catalog built on configurables points to a custom build or a connector whose vendor confirms configurable export, such as ECOSIRE, whose page lists parent and child variations. Several marketplaces, repricing rules or heavy order volume add effort.
✦ WHERE THESE PROJECTS GO WRONG
Where these projects go wrong.
- Slow order polling. At 0.0167 requests per second for getOrders, you cannot poll your way to fresh orders. Use notifications where Amazon offers them.
- Overselling. Magento stock changes have to reach Amazon quickly, and FBA stock needs its own reconciliation.
- Category and attribute rules. Amazon product types and required attributes do not line up with your Magento attribute sets by default.
- Parent and child listings. Amazon variation families have to map onto Magento configurables.
- Missing buyer details. PII needs a Restricted Data Token, which limits what an order import can carry.
- Token expiry. LWA access tokens last one hour, so the integration must refresh them without dropping calls.
- Money that does not match. Marketplace fees, taxes and refunds do not map straight onto Magento order totals.
✦ QUESTIONS MERCHANTS ASK
Amazon Seller Central (Selling Partner API) integration FAQ.
Which Amazon API does a Magento integration use?+–
What are the rate limits?+–
Is there a ready-made connector?+–
Do these connectors handle FBA and repricing?+–
How do I avoid throttling?+–
What does it cost?+–
✦ KEEP EXPLORING
Related integrations.
Magento POS Integration: Connectors, Cost and Timeline
A POS integration is really a decision about who owns stock. Lightspeed, Square, Clover and Shopify POS each expose a different API with different limits, so the sync you build depends on which one is at your counter.
Magento QuickBooks Integration: Connectors, Cost and Timeline
QuickBooks Online and QuickBooks Desktop need two different integrations. Online talks REST and OAuth 2.0. Desktop talks qbXML through the Web Connector. Find out which one you run before anyone quotes you a price.
SOURCES
- Amazon SP-API: Orders API rate limits (opens in a new tab)
- Amazon SP-API: Usage plans and rate limits (opens in a new tab)
- Amazon SP-API: Connect to the SP-API (opens in a new tab)
- ECOSIRE: Amazon marketplace connector for Magento (opens in a new tab)
- Celigo: Magento integrations (opens in a new tab)
- M2E Pro: pricing (opens in a new tab)
- M2E Pro: Magento Amazon integration (opens in a new tab)
- Webkul: Amazon Connector (opens in a new tab)
- CedCommerce: Amazon integration (opens in a new tab)
- Adobe: Amazon Sales Channel guide (opens in a new tab)