What a Amazon Marketplace integration gives you.
Your order operations team sees Amazon and direct-channel orders in one OMS or ERP queue. Picking, packing and dispatch are managed together, and tracking data reaches Amazon customers in real time.
Stock is allocated to Amazon listings on a per-region basis, with reserve pools for FBA and FBM. Oversell is prevented even during high-traffic periods, and stock levels stay synchronized across all channels.
Product prices and regional promotional rules are published to Amazon on a defined schedule. Pricing exceptions and manual overrides are logged and do not silently drift away from your commerce platform.
Settlement fees, referral charges and refunds are mapped to your nominal accounts in the ERP. Month-end reconciliation is automated where Amazon data is available, and exceptions are escalated to finance teams.
Dashboards show Amazon order count, cancellation rate, stock-out events, feed failures and seller-performance metrics. Alerts trigger when Amazon account health drifts or feeds fail.
Where a Amazon Marketplace integration earns its place.
If two or more of these are true, the integration usually pays for itself quickly.
Where off-the-shelf connectors fall short.
Vendor connectors are fine for simple cases. Here's where the real ones need more.
Amazon's standard feeds and API offer scheduled or near-real-time stock updates, but bulk feeds can lag. Multi-warehouse allocation and advanced reserve logic often require custom connectors or middleware to prevent oversell during peak traffic.
Amazon EU, UK, US and other regions operate as separate accounts with separate feeds and order streams. Synchronizing regional pricing, promotions and product data across accounts is not native; cross-region inventory pooling requires manual or custom logic.
Amazon controls which orders go to Fulfillment by Amazon (FBA) versus Fulfillment by Merchant (FBM). Your OMS may not have immediate visibility into FBA routing decisions or split shipments until after order confirmation.
Amazon settlement reports and refund data publish on a 14-30 day cycle depending on region. Real-time reconciliation with your ERP is difficult; late-arriving refunds or adjustments can create finance exceptions.
Amazon's product taxonomy and attribute requirements are rigid. Custom attributes, bundle logic or dynamic content often fall outside Amazon's standard schema, requiring manual fallback or content governance workarounds.
Inventory allocation rules and oversell prevention are often invisible until peak season; by then orders are unshippable and customer experience is already damaged.
Where this integration sits in your estate.
Amazon Marketplace holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.
Works across the whole stack. Connect Amazon Marketplace to your storefront, ERP and everything between.
- Channel-specific listings and attributes
- Order routing and FBA vs. FBM decisions
- Amazon payment processing and customer disputes
- Settlement and commission calculation
- Seller performance metrics and account suspension rules
- Product catalogue and master data (via PIM)
- Base and promotional pricing (via ERP or pricing engine)
- Inventory allocation and reserve policies
- Order fulfillment and dispatch confirmation
- Return and refund workflows
Systems this integration usually sits next to.
Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.
- Adobe Commerce
- Magento Open Source
- Shopify Plus
- BigCommerce
- Other storefronts
- ERP (inventory, pricing, customer accounts, order processing)
- PIM (product data, images, attributes)
- WMS (dispatch, tracking, stock movements)
- OMS (order routing, fulfillment orchestration)
- Payments (Amazon Pay, order settlement)
- Finance system (settlement reconciliation, commission tracking)
Not sure if this works with your stack?
Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.
The data flows we wire.
Each flow has a direction and an owner. We agree both before a line of code is written.
How iWeb configures the integration around your business.
Same method on every integration. The decisions come before the code.
- 01Amazon account and region strategy
We work with you to define which Amazon accounts and regions you will operate, how inventory is pooled, which products are listed where, and how pricing and promotions adapt by region. This prevents account sprawl and unowned data gaps.
- 02Product feed design and governance
We design the data flow from your PIM or ecommerce platform to Amazon, including attribute mapping, image handling, bundle logic and category rules. We enforce feed quality checks so bad data does not publish to Amazon.
- 03Order ingestion and routing
We build connectors that ingest Amazon orders into your OMS or ERP with Amazon order ID, FBA flags, shipping address and seller notes. Orders are routed to the correct warehouse or fulfillment partner based on your rules.
- 04Inventory and reserve management
We define how stock is allocated to Amazon, how FBA inventory is tracked separately from FBM, and how reserve or safety-stock rules are applied. We ensure Amazon listings reflect actual sellable inventory.
- 05Returns, refunds and reconciliation
We map Amazon return requests to your RMA workflow, link refunds back to the original order in your ERP, and reconcile refund amounts against settlement data. Late-arriving refunds and adjustments are tracked and escalated.
- 06Monitoring, alerting and exception handling
We set up dashboards and alerting for feed failures, oversell events, order ingestion lag, settlement discrepancies, Amazon account health and seller performance metrics. Exception queues are owned and cleared by named teams.
Who owns what.
The single most important table in any integration. One system owns each field; everything else reads it.
Built this before
iWeb has designed and built Amazon Marketplace integrations for retailers and brands across consumer, health, industrial and foodservice sectors. We understand the operational tension between Amazon's inventory control, your multi-region strategy and unified order fulfillment.
What we test before launch.
Every one of these is rehearsed before a customer ever sees the integration.
Common risks and where they bite.
We name these on day one. A risk written down is a risk you can plan around.
If stock updates to Amazon lag behind warehouse movements or storefront sales, listings can remain active after inventory is depleted. Amazon order ingestion during the lag window causes fulfilled orders to become unshippable.
If the order ingestion connector fails or falls into a retry loop, Amazon orders may not appear in your OMS or may be duplicated. Customer notifications and dispatch instructions are delayed or sent twice.
If product feeds to Amazon EU, UK and US accounts are not synchronized or region-specific pricing is not governed, listings in different regions may show conflicting prices or expired promotions.
If FBA stock is not tracked separately from your central inventory, or if FBA inbound shipments are not deducted from saleable stock during transit, the system over-allocates inventory to other channels.
If Amazon settlement reports arrive after your finance close window, or if refund amounts do not match order totals, reconciliation is delayed or incomplete. Chargebacks and Amazon fee adjustments are not captured.
If no team owns the queue of failed feeds, unshipped Amazon orders or refund mismatches, problems accumulate silently. By the time exceptions are noticed, orders are already late or customer experience is already damaged.
Relevant services and sectors.
Common questions about Amazon Marketplace integrations.
How do we keep Amazon listings in sync with our main storefront without overselling?
We design inventory allocation so stock is reserved or pooled for Amazon based on your sales mix and reserve policy. Stock updates to Amazon sync on a schedule you define (real-time, hourly or daily). FBA inventory is tracked separately so it is not oversold to other channels. During peak traffic, the integration monitors for oversell events and triggers alerts.
How do Amazon orders flow into our ERP and OMS?
We build a connector that ingests Amazon orders via the Selling Partner API, maps order data (customer address, items, Amazon order ID, FBA flag) to your ERP or OMS schema, and routes orders to the correct fulfillment location. Orders are tagged with Amazon order ID for later tracking updates.
How do we handle multiple Amazon regions or accounts?
We define a multi-region strategy so each Amazon account (EU, UK, US, etc.) is treated as a separate channel with its own inventory pool, pricing and promotions where needed. Product feeds and inventory syncs are region-aware, and settlement is reconciled per-region.
How do we manage pricing and promotions on Amazon?
Base pricing comes from your ERP or pricing engine. We apply region-specific markups or promotions via feeds to Amazon. Pricing changes are published on a schedule you define; manual overrides are logged so pricing drift is visible.
How do we track FBA (Fulfillment by Amazon) inventory separately from our own stock?
We separate FBA stock from Fulfillment by Merchant (FBM) stock in your inventory model. Inbound FBA shipments are deducted from saleable stock during transit. Inventory counts from Amazon sync back to your ERP so reconciliation is possible.
How do Amazon returns and refunds get back into our system?
Return requests from Amazon flow into your RMA or customer service system. We match refund amounts to original orders in your ERP. Refunds are tagged with the Amazon return reason so your team can identify patterns (wrong item, damage, etc.).
How is Amazon settlement and commission fees handled in our ERP?
We map Amazon settlement reports (which arrive on a 14-30 day cycle) into your finance system. Commission, referral fees and refunds are recorded against defined nominal codes. Month-end reconciliation is automated where data is available; exceptions are flagged for finance review.
What happens if the feed to Amazon fails or lags?
We monitor feed publish times and failure rates. If a feed fails, alerts are triggered immediately and a named team is paged. Retry logic is built in; old feeds are not re-published. You can see which products are out of sync and why.
How do we prevent orders from being duplicated or lost?
We use Amazon order ID as a unique key and track each ingestion. Idempotency checks prevent duplicate orders if the connector retries. Orders in a failed state are surfaced in an exception queue for manual resolution.
Can we use FBA (Fulfillment by Amazon) and FBM (our own fulfillment) at the same time?
Yes. We track FBA and FBM inventory separately and let Amazon route orders based on its algorithm. We can also apply rules (e.g., direct FBA orders to Amazon's warehouse, FBM orders to your own). Dispatch instructions differ by fulfillment type.
How do we get tracking information back to Amazon customers?
After your WMS or fulfillment partner ships an order, we capture the carrier and tracking number and push it back to Amazon via the Selling Partner API. Amazon then notifies the customer. Tracking updates are real-time or near-real-time depending on your WMS.
What dashboards or reports do we get to see Amazon channel performance?
We set up operational dashboards showing Amazon order volume, cancellation rates, stock-out events, feed publish times, settlement status and seller performance metrics (cancellation rate, return rate, late shipment rate). Alerts notify you of degradation.
How do we test the Amazon integration before going live?
We use Amazon's Sandbox environment for order ingestion and feed testing. We test oversell prevention by simulating inventory depletion and concurrent orders across channels. We validate refund and settlement reconciliation with test data. We stress-test feed publishing during simulated peak traffic.
What happens if Amazon's API or feed service is down?
We design retry logic and queuing so failed feeds are retried with exponential backoff. We alert you immediately so you can manually manage Amazon listings if needed. We do not auto-disable your storefront during Amazon outages.



