Skip to main content
Talk to an expert
commercetools logo

commercetools marketplace integration for ecommerce

Unified orders and stock across every marketplace channel iWeb connects commercetools with your marketplaces, ERP and fulfilment systems to keep product listings, inventory allocation and order flow accurate and in step across channels. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: marketplace connector, feed integration, channel plugin, app.

commercetoolsiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a commercetools integration gives you.

Unified channel visibility

All orders from Amazon, eBay, Shopify and other channels appear in commercetools tagged by source, giving operational teams a single place to see incoming demand and make fulfilment decisions.

Protected inventory across channels

Stock is managed centrally through commercetools with channel-specific allocation and buffering rules, so you sell each unit once and avoid oversell penalties or customer cancellations.

Channel-specific product data confidence

Attributes, pricing and images are mapped to each channel's requirements before publish, so listings arrive complete and reduce merchant processing time and customer questions.

Faster fulfilment and tracking

Orders flow from commercetools to ERP or OMS without manual reentry, and dispatch confirmations travel back to marketplaces automatically, so customers get tracking details faster.

Cost control through automation

Reduce manual channel management, data re-entry, exception handling and customer service escalations by automating order flow, stock sync and returns reconciliation.

02 · When it's worth it

Where a commercetools integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Publishing product listings with channel-specific attributes, pricing and stock to Amazon, eBay, Shopify, Etsy or other marketplace platforms
Ingesting orders from multiple marketplace channels back into commercetools, then routing them to ERP or OMS for fulfilment
Syncing stock availability and reserved inventory across all channels to prevent oversell
Pushing dispatch confirmations, tracking numbers and cancellations back to each marketplace
Managing channel-specific returns and refunds with reconciliation back to ERP
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Channel-specific attribute mapping is manual

commercetools does not natively know how your product attributes map to Amazon's, eBay's or Shopify's data models. Each channel's required fields, naming conventions and picklist values must be configured and tested in the connector or middleware.

Stock buffering and allocation logic requires custom rules

by default, commercetools syncs inventory but does not automatically reserve stock for channels with different lead times, or buffer for flash sales. Allocation rules, safety stock and channel-specific thresholds must be designed and built.

Order routing to OMS or fulfilment is not automatic

Orders land in commercetools, but the decision of where to fulfil them (warehouse A, warehouse B, dropship, branch for click-and-collect) requires OMS logic or custom routing rules. commercetools does not make that choice by default.

Channel-specific refund and return workflows are incomplete

Returns and refunds initiated on a marketplace may not automatically map back to the right credit-note, stock movement or customer account in ERP. Each channel's return policy and reconciliation rules must be built into the connector.

Failure and exception handling is not named

If a channel feed fails, an order does not arrive, or a tracking sync breaks, there is no default alerting or queue to catch it. Exception handling, retries and escalation paths must be designed before launch.

04 · The real work

Multi-channel operations fail silently when stock allocation, order tagging and tracking sync are not explicitly named and monitored; commercetools can be the hub, but only if ownership boundaries and exception paths are clear from the start.

05 · Where it sits

Where this integration sits in your estate.

commercetools 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.

Commerce platform agnostic. Connect commercetools across your entire technology stack.

System of record
Source / owner
commercetools
Multi-channel order and inventory orchestration hub
  • Channel-specific product listings and attributes
  • Marketplace order deduplication and tagging
  • Stock allocation rules and buffers per channel
  • Dispatch status and tracking reconciliation
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Direct-to-consumer storefront catalogue and checkout
  • Own-brand pricing and promotions
  • Direct customer account and order records
Connected neighbours
Integration layer
Marketplaces (Amazon, eBay, Shopify, Etsy, etc.)
Order source and destination for channel-specific listings and shipment confirmation.
Integration layer
ERP or accounting system
Source of base pricing, stock levels and destination for orders, invoices, returns and credit notes.
Integration layer
PIM or product data system
Source of product attributes, descriptions and media that feed into commercetools for channel-specific transformation.
Integration layer
OMS or order management layer
Receives orders from commercetools and orchestrates routing, split shipment and fulfilment for different channels or locations.
Integration layer
WMS or fulfilment system
Source of stock movements, dispatch confirmations and tracking that flow back through commercetools to marketplaces.
Two-way sync where relevant
06 · Surrounding systems

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.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • Amazon Marketplace
  • eBay
  • Shopify
  • ERP (SAP, NetSuite, Dynamics)
  • PIM or product data sources
  • OMS or order management system
  • WMS or fulfilment centre
  • Payment processors
Not sure?

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.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into SALES CHANNELS & COMMERCETOOLS & ERP
↔BOTH WAYS
Channel feed export: Product catalogue, pricing, stock and images flow from commercetools into each marketplace or channel system, often with channel-specific attribute mapping, currency conversion and inventory buffering
Data is usually pushed on schedule or triggered by catalogue changes.
Marketplace orders: Customer orders, line items, addresses and payment status arrive from each marketplace into commercetools, tagged with the channel source so OMS or ERP can route them correctly
Order acknowledgement and reservation status flow back out to the marketplace.
Order and inventory movement: Orders acknowledged in commercetools move into ERP for invoicing and accounting; stock movements from WMS or branch systems flow back into commercetools to refresh channel availability
Channel returns feed back into the inventory and credit-note workflows.
Dispatch and tracking: Once fulfiled, tracking numbers, carrier details and dispatch confirmations travel from ERP, WMS or OMS back into commercetools and then out to each marketplace so customers see up-to-date shipment status.
Stock and channel allocation: Stock levels sync both ways; commercetools holds the allocation logic for each channel, while ERP or WMS provides the authoritative inventory counts
Oversell protection and stock reservation rules are enforced at the commercetools layer.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Channel attribute and pricing transformation

    iWeb maps your product attributes, descriptions, pricing and images to each marketplace's schema and requirements, handling currency conversion, regional pricing and channel-specific rules automatically.

  2. 02
    Order ingestion and deduplication

    iWeb builds the connector to pull orders from each marketplace into commercetools, deduplicates across channels, adds rich context (channel source, shipping address validation, payment status) and prepares them for routing to ERP or OMS.

  3. 03
    Stock allocation and oversell prevention

    iWeb designs buffer stock rules, channel-specific reservation windows and stock-movement handling so inventory published to each channel reflects true availability without overselling or channel conflicts.

  4. 04
    Dispatch and tracking reconciliation

    iWeb builds the reverse flow so that once orders fulfil in ERP or WMS, tracking numbers and dispatch events travel back into commercetools and out to each marketplace in real time.

  5. 05
    Monitoring, alerting and exception handling

    iWeb sets up monitoring for feed health, order arrival, stock sync and tracking flow, with named escalation queues and alerting so issues are caught before customers notice.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataChannel-specific listing data (attributes, images, pricing, inventory)
Source / ownercommercetools
Maintained byProduct and channel operations teams, with transformations defined in the connector
NotesEach marketplace may require different attribute names, picklist values or imagery; commercetools holds the canonical copy and the connector applies channel-specific rules before publish.
DataMarketplace orders and line items
Source / ownercommercetools (initially), then ERP or OMS
Maintained byMarketplace connectors ingest orders; commercetools deduplicates and tags by channel; ERP or OMS takes ownership for invoicing and fulfillment
NotesOrders flow from marketplace into commercetools for orchestration, then move to ERP or OMS for accounting and warehouse routing. Acknowledgement status flows back through commercetools to the marketplace.
DataStock levels and channel allocation
Source / ownerERP or WMS (physical truth), commercetools (channel view and allocation rules)
Maintained byERP or WMS provides available inventory; commercetools applies channel-specific buffers, reservations and allocation logic; stock movements sync both ways
NotesStock originates in ERP or WMS; commercetools holds the channel allocation layer and prevents oversell. Stock movements from fulfillment flow back into both systems.
DataDispatch confirmation, tracking and shipment status
Source / ownerERP, WMS or carrier system (source of truth)
Maintained byERP or WMS generates dispatch events; connector flows them back through commercetools to each marketplace in real time
NotesTracking and shipment events originate in fulfillment systems and flow outbound to each marketplace. commercetools acts as a pass-through for status and reconciliation.
DataReturns, refunds and credit notes
Source / ownerERP (financial record); commercetools and marketplace (initiation point)
Maintained byReturns initiated on a marketplace flow into commercetools and trigger ERP credit-note and stock-movement workflows; reconciliation happens in ERP
NotesReturn authorisation may start on the marketplace, flow through commercetools for orchestration and hit ERP for financial and inventory accounting. Each system must agree on the original order, customer and line items.
DataIntegration exceptions, monitoring and alerting
Source / ownerIntegration layer (owned by iWeb and operations team)
Maintained byiWeb designs and operates monitoring; operations team owns escalation and remediation
NotesFeed health, order delays, stock sync breaks and tracking failures are detected and escalated by the integration layer. Exception queues and playbooks are owned jointly.
10 · Experienced integrator

Built multi-channel orchestration before

iWeb has built commercetools integrations for retailers and brands managing orders across multiple marketplaces. We understand how to design attribute mapping, stock allocation, order deduplication and tracking sync so that orders and inventory stay accurate and channels do not conflict.

Design channel-specific attribute mapping and pricing transformation so product listings arrive complete and compliant on each marketplace.
Build order ingestion, deduplication and channel-source tagging so orders from Amazon, eBay and other marketplaces land safely in commercetools and route to ERP or OMS.
Implement stock allocation and buffer rules at the commercetools layer so inventory is reserved per channel and oversell is prevented across all channels.
Set up dispatch and tracking reconciliation so fulfillment events flow from WMS or ERP back through commercetools to each marketplace in real time.
Design monitoring, alerting and exception handling so feed failures, missing orders and tracking delays are caught and owned before customer impact.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify product feed: sample listings from commercetools match required attributes, pricing and images on each target marketplace before full publish.
Test order flow: create test orders on Amazon, eBay and Shopify and confirm they arrive in commercetools tagged by channel, deduplicated and ready for ERP routing.
Validate stock sync: update inventory in ERP and confirm availability updates appear in commercetools within the agreed SLA, then appear on each marketplace.
Confirm dispatch and tracking: fulfil a test order in WMS and verify tracking number flows back through commercetools to the marketplace within agreed time.
Exception handling: simulate a failed marketplace feed, a missing order and a broken tracking sync; confirm alerts fire and exception queues populate correctly.
Rollback and failover: confirm the integration can be paused, rolled back and resumed without losing or duplicating orders or stock movements.
Performance baseline: confirm feed publishing, order ingestion and stock sync stay under agreed latency budgets under peak load (flash sales, Black Friday).
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Channel listings go live with incomplete or wrong attributes

If attribute mapping is not tested per channel before the first feed run, products may publish to Amazon or eBay with missing or misnamed fields, causing low visibility, customer confusion or merchant policy violations.

Orders are lost or duplicated between marketplace and commercetools

If order ingestion is not deduplicating across channels, or if acknowledgement is not flowing back to the marketplace, you risk duplicate order creation in ERP or silent order loss that customers notice when tracking does not appear.

Stock oversells because reservation windows are not respected

If a product sells on multiple channels but the stock buffer does not account for different channel lead times or marketplace sync delays, you may sell the same unit twice and face cancellations, penalties or refund storms.

Dispatch confirmations do not reach the marketplace on time

If tracking sync from ERP or WMS back to commercetools is slow or breaks silently, customers see no shipment status on the marketplace and file service tickets, harming seller ratings and increasing support costs.

Returns and refunds reconcile incorrectly to ERP

If a return initiated on eBay does not correctly map to the original order, customer and invoice in ERP, finance teams cannot reconcile credits and inventory counts drift.

Channel feed failures are not noticed until customer escalation

If monitoring and alerting are not in place, a broken marketplace feed or stalled order sync may go undetected for hours, meaning products go offline or orders stop flowing into fulfillment.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about commercetools integrations.

How do I publish product listings to multiple marketplaces with different attribute requirements?

iWeb maps your product attributes, pricing and images in commercetools to each marketplace's required fields. The connector applies channel-specific transformations (currency, UOM, attribute names, picklists) before pushing the feed. Testing per channel catches mismatches before listings go live.

What happens when an order lands in commercetools from multiple channels?

iWeb builds deduplication logic to ensure each marketplace order is tagged with its channel source, de-duplicated by order ID and enriched with merchant notes, then routed to ERP or OMS. Acknowledgement flows back to the marketplace to confirm receipt.

How do I prevent overselling stock across Amazon, eBay and my own storefront?

iWeb designs buffer stock rules, channel-specific reservation windows and stock-movement sync so each marketplace sees only inventory you are comfortable selling on that channel. Sold units are reserved in ERP and reflected back in real time.

How does stock from my warehouse or branch get back to the marketplace?

iWeb builds a sync from ERP or WMS into commercetools when stock levels change. commercetools then publishes updated inventory to each marketplace, respecting your buffer rules and allocation logic.

Can I set different pricing or promotions per channel in commercetools?

Yes. commercetools supports channel-specific pricing and promotional rules. iWeb ensures those rules are applied when the feed publishes to each marketplace, and handles currency and regional pricing conversions.

How do dispatch confirmations and tracking numbers get back to the marketplace?

Once ERP or WMS confirms dispatch, the connector flows tracking number and carrier details back into commercetools, which pushes them to each marketplace in real time so customers see shipment status.

What happens if the marketplace feed breaks or orders stop arriving?

iWeb sets up monitoring and alerting on feed health, order arrival and stock sync. If a feed stalls or fails, the integration layer detects it immediately and alerts operations so you can investigate before customers notice.

How do returns initiated on a marketplace flow back to my ERP?

Return authorisation and refund requests from the marketplace flow into commercetools, then trigger credit-note and stock-movement workflows in ERP. iWeb ensures the original order, customer and line items are correctly matched so finance can reconcile.

Can I see all orders from all channels in one place?

Yes. commercetools ingests orders from each marketplace tagged by channel source, so operations teams see all demand in a single system. Orders then route to ERP or OMS for fulfillment and accounting.

How are exceptions and failed syncs handled?

iWeb names exception queues for failed orders, missing stock syncs, broken tracking feeds and refund rejections. Each queue is owned by a team, with playbooks and escalation paths so issues are resolved quickly.

What if I add a new marketplace or want to remove one later?

iWeb designs the connector architecture so new marketplace channels can be added and tested independently. Removing a channel is straightforward; existing orders remain in commercetools and ERP for reconciliation.

How do I know which system owns which data?

Before any integration work starts, iWeb creates an ownership map that names which system holds each piece of data (stock, pricing, orders, tracking, returns, exceptions) and who maintains it. This is agreed with stakeholders and documented.

What commerce platforms does this work with?

commercetools integrates with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts. The marketplace connectors are independent of your storefront choice, so you can use any ecommerce platform alongside marketplaces.

Can I run commercetools alongside my existing PIM or ERP?

Yes. iWeb typically positions commercetools as the channel orchestration layer, with product data flowing in from PIM and stock flowing in from ERP. Orders and returns flow back out to ERP for accounting and fulfillment.

Next step

Have a commercetools integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →