Selling on Amazon, eBay, Zalando or a B2B marketplace operated by one of your key customers: this is now a reality for a growing number of SMEs and mid-market companies across Europe. But when orders flow in from five different channels simultaneously — with stock to synchronise in real time and commission reconciliation eating up accounting hours — manual management hits its limits fast.
ERP–marketplace integration is the technical and strategic answer to this challenge. This guide helps you choose the right architecture for your situation — whether you’re an Amazon seller processing 200 orders a day or a B2B marketplace operator managing 50 merchants on a sector-specific platform.
Why Marketplace–ERP Integration Is Now Essential in 2026
The Growth of Marketplace Sales Across Europe (B2C and B2B)
Marketplaces are no longer a secondary channel. Across Europe, they now represent a large and growing share of e-commerce transactions — a trend that has accelerated every year since 2020, according to data from Ecommerce Europe and national trade associations. On the B2B side, adoption is equally rapid: professional purchasing via marketplace (spare parts, industrial supplies, MRO) is growing strongly in manufacturing and distribution.
The Mirakl platform, which powers more than 450 marketplace operators worldwide — including Carrefour, Decathlon, Airbus Helicopters, Macy’s and ASOS — generated $11.2 billion in GMV in 2024, a 30% year-on-year increase (Mirakl 2024 results). That single figure illustrates the scale of the commercial shift towards marketplace platforms — and the pressure it places on sellers’ IT systems to keep pace.
The Risks of Unintegrated Operations: Stock Discrepancies, Duplicate Orders, VAT Errors
Without ERP integration, your team manually juggles the Amazon Seller Central back-office, the eBay interface, the Mirakl flows from your customer, and your management software. The operational consequences are predictable and well-documented:
- Overselling: you accept an order on Amazon when stock is exhausted, because the inventory decrement hasn’t yet been pushed to the ERP. The customer receives a cancellation, and your Amazon seller score takes a hit.
- Duplicate data entry: the same order is manually re-entered into your ERP, introducing errors in item references or quantities — and driving up return rates.
- VAT errors: VAT rules vary by delivery country, marketplace type, and fulfilment method (FBA vs FBM). Without automation, errors are inevitable at any meaningful volume.
- Accounting reconciliation delays: commissions, refunds and Amazon settlements arrive in bulk. Reconciling them manually at month-end can consume several full days of an accountant’s time.
The Hidden Cost of Manual Marketplace Order Entry
Manual order processing carries a real cost, one that is routinely underestimated in marketplace channel profitability calculations. For a merchant handling 300 orders per day across three marketplaces, data entry and verification time can be equivalent to one or two full-time administrative positions. Add to that the cost of error correction: poorly tracked returns, credit notes issued outside the ERP, inventory reconciled at month-end rather than in real time.
The real question is not “integrate or not integrate” — it is “at what order volume does the investment become worthwhile”. For the vast majority of active multi-channel sellers, that threshold is reached well before 100 orders per day.
The 3 ERP–Marketplace Integration Architectures
There is no single way to connect an ERP to a marketplace. The right choice depends on the number of channels, order volume, and the IT resources available.
Architecture 1: Native Direct Connector (Vendor Module)
A native connector is built directly by the ERP vendor or a certified partner. Odoo offers an official Amazon Connector maintained by the Odoo team. SAP Business One and SAP S/4HANA have marketplace connectors available via the SAP App Center. Microsoft Dynamics 365 integrates with selected platforms through AppSource-certified extensions.
Advantages:
- Simple deployment: no middleware to maintain
- Vendor support included in the maintenance contract
- Consistency with the ERP data model (no transformation between two heterogeneous systems)
Limitations:
- Rigidity: data transformation logic is set by the vendor; edge cases require custom development
- Dependency on update cycles: if Amazon releases a new API version, you wait for the vendor to publish a compatible patch (as happened with the MWS to SP-API migration)
- Generally suited to one or two marketplaces at most
Best for: SMEs with one or two channels, moderate volume (under 300–500 marketplace orders per day), limited IT resources.
Architecture 2: Middleware and iPaaS (Celigo, Boomi, MuleSoft, Make)
An iPaaS middleware sits between the ERP and the marketplaces and orchestrates data flows: an Amazon order is received via the SP-API, transformed according to business rules defined in the platform, and injected into the ERP. The shipment confirmation then flows back to Amazon with the carrier tracking number.
Platforms such as Celigo, Dell Boomi and MuleSoft offer ready-to-use connectors for Amazon SP-API, Mirakl, and dozens of other channels. Make (formerly Integromat) is a more affordable alternative for mid-market companies with manageable volumes.
Advantages:
- Maximum flexibility: transformation rules can be configured without heavy development
- Multi-ERP capable: suited to groups running multiple ERP instances (SAP in the UK, Dynamics 365 in a German subsidiary)
- Independence from ERP update cycles: the middleware absorbs marketplace API changes without touching the ERP
Limitations:
- Monthly iPaaS service cost (from a few hundred to several thousand euros per month, depending on transaction volume)
- Requires an IT resource or integrator to configure and maintain flows
- A misconfigured flow can silently duplicate orders or block stock updates with no native alerting
Best for: Mid-market companies with 2–5 marketplaces, multiple ERPs or e-commerce platforms, 500–5,000 orders per day.
Architecture 3: Dedicated OMS as Intermediate Layer (ChannelEngine, Stock&Buy, Pipe17)
A multi-channel OMS (Order Management System) goes further than simple middleware: it centralises the business logic across all sales channels. ChannelEngine, a leading European player in this segment, connects to more than 1,300 marketplaces worldwide and offers native integrations with SAP, Microsoft Dynamics 365 Business Central, NetSuite and Exact Online.
The OMS manages channel-specific stock rules (safety stock reservation per marketplace), order prioritisation by margin or lead time, differentiated pricing rules, and reverse logistics (returns). It acts as the multi-channel single source of truth — the ERP receives processed orders and consolidated stock movements.
Advantages:
- Complete centralisation of multi-channel business logic in a single dedicated system
- Unified view of available stock per channel in real time
- Scalable: add a new marketplace via configuration without an IT project
- Suited to complex operations: parallel FBA/FBM, differentiated channel rules, multi-origin returns
Limitations:
- An additional layer in the IT architecture: a third system to maintain and evolve
- Higher cost than a native connector — ROI is realised above a certain volume threshold
- Operational teams need training (order tracking moves from the ERP to the OMS)
Best for: Advanced multi-channel retailers with 5 or more marketplaces, high volumes (over 1,000 orders per day), or complex stock rules requiring dedicated orchestration.
Amazon Seller Central and Your ERP: A Practical Overview
Amazon remains the dominant marketplace in Europe for third-party sellers. Its ERP connection is typically the first integration project for IT teams.
Amazon SP-API: What Can Be Synchronised
The Amazon SP-API (Selling Partner API) replaced the legacy MWS (Marketplace Web Service) system. Migration is mandatory: Amazon decommissioned the Orders, Reports, and Merchant Fulfillment sections of the MWS API as of 31 August 2023 (Amazon Seller Central, official forum). Any ERP connector still based on the legacy MWS API should have been updated. If it hasn’t, flows are either interrupted or degraded on routes that have not yet been fully shut down.
Via the Amazon SP-API, your ERP or OMS can synchronise:
- Orders: near-real-time retrieval with statuses, delivery addresses, and buyer information
- Inventory: update of available quantities declared to Amazon by SKU
- Pricing: price changes via the Listings Items API
- Shipments: shipping confirmation with carrier tracking number (critical for payment timing)
- Reports: retrieval of sales, commission and FBA inventory reports
FBA vs FBM: A Major Impact on ERP Stock Management
This is one of the most frequently misconfigured settings during a first integration.
With FBA (Fulfilment by Amazon), your inventory is physically held in Amazon’s warehouses. This stock must not be included in your ERP’s available stock for other channels. A misconfiguration generates overselling on your own website or on eBay using stock that is physically already at Amazon.
With FBM (Fulfilment by Merchant), you ship from your own warehouse. The ERP is the source of truth, and Amazon must be synchronised with a decrement after each sale.
Correctly managing both modes in parallel — many sellers use FBA for best-sellers and FBM for long-tail references — requires precise configuration in the ERP or OMS, with separate stock locations and differentiated synchronisation rules per mode.
VAT Calculation Service (VCS): Tax Automation and Accounting Reconciliation
Amazon offers a VAT calculation service (VCS — VAT Calculation Service) for pan-European sales. It calculates the applicable VAT based on the delivery country and OSS (One Stop Shop) rules. However, VCS does not automatically generate accounting entries in your ERP. A mapping must be configured so that VAT amounts calculated by Amazon are correctly posted to your chart of accounts.
Without this mapping, your accounting either understates or overstates collected VAT — an anomaly typically detected during an audit or tax investigation, rarely during the financial year.
Common Amazon-Specific Pitfalls
- Settlement delay: Amazon pays sellers every 14 days. This lag must be managed in the ERP (a separate Amazon debtor holding account) to avoid cash flow anomalies in monthly reporting.
- Fee reconciliation: variable commissions by product category, FBA fees calculated by dimensions and weight, Sponsored Products advertising costs — all must be retrieved from Amazon reports and posted to the ERP to calculate real channel margin.
- Multi-country: if you sell on Amazon.co.uk, Amazon.de and Amazon.fr, each is a separate account with its own order flows and applicable VAT rules.
Mirakl and B2B Marketplaces Operated by Your Customers
Mirakl has become the de facto standard for enterprises operating their own marketplace — distributors, industrial players, B2B procurement hubs. With more than 450 operators worldwide using the platform (mirakl.com), there is a strong chance that one or more of your customers or partners has deployed Mirakl.
Mirakl API: The Operator Standard in Europe
The Mirakl API is structured in two distinct parts:
- Seller API (MMP — Mirakl Marketplace Platform, merchant side): used by merchants to push product catalogues, receive orders, update inventory, and confirm shipments
- Operator API: used by the marketplace operator to manage merchants, categories, commission rules, and financial flows
For a seller integrating Mirakl into their ERP, the Seller API is what matters day-to-day. Odoo, Microsoft Dynamics 365, and Sage have official or certified Mirakl connectors. For less common ERPs, an iPaaS platform (Celigo, Boomi) typically offers a ready-to-use Mirakl connector.
For Sellers (Merchants): ERP Connection via Mirakl Connector
On the seller side, Mirakl integration is similar in structure to an Amazon integration: order retrieval, stock updates, shipment confirmation with tracking. The key structural difference lies in the multiplicity of operators. If you sell simultaneously on Carrefour’s marketplace, Leroy Merlin’s marketplace, and a sector-specific industrial marketplace, you must manage as many distinct Mirakl instances — each with its own categories, data formats, and commission rules.
An OMS such as ChannelEngine or Stock&Buy centralises these flows by exposing a unified interface on the ERP side. The ERP receives normalised orders regardless of the source Mirakl operator.
For Operators: Back-Office ERP Integration for Buyers
If your company itself operates a Mirakl marketplace — for your resellers or suppliers — back-office ERP integration is more complex. You must connect incoming merchant order flows to your procurement ERP, automate commission invoicing, and synchronise product data with your ERP catalogue and negotiated pricing system.
Sector Use Cases
B2B MRO Marketplace (Maintenance, Repair, Operations): an industrial supplies distributor opens a marketplace for its suppliers and subcontractors. The ERP receives consolidated orders, automatically triggers supplier restocking, and feeds the commission billing system at month-end.
Automotive Spare Parts Marketplace: a parts manufacturer exposes its catalogue to garages and workshops via a Mirakl platform. ERP integration ensures real-time availability, generates invoices based on customer-negotiated pricing, and feeds batch traceability for safety-regulated parts.
Key Metrics for Measuring Integration ROI
The ROI of an ERP–marketplace integration is measured primarily across three dimensions: operational cost reduction (less manual entry), service quality improvement (fewer stockouts, fewer order errors), and the ability to scale without adding administrative headcount.
| KPI | Before Integration | After Integration | Estimated Gain |
|---|---|---|---|
| Marketplace order processing time | 3 to 6 hours | 10 to 30 minutes | -80 to -90% |
| Stockout rate on marketplace | 3 to 8% of active references | Under 1% | -70 to -90% |
| Cost per order (incl. manual entry) | €2 to €5 per order | €0.10 to €0.50 | -80 to -95% |
| Order error rate (wrong item, wrong quantity) | 1 to 3% | Under 0.2% | -85 to -95% |
| Monthly accounting reconciliation time | 2 to 4 days | 2 to 4 hours | -80 to -95% |
These estimates are indicative. They vary based on order volume, the complexity of business rules, and the maturity of the existing IT landscape before integration.
The 5 Pitfalls to Avoid
1. Syncing prices without a channel rule
Amazon’s price is not necessarily the same as your own website or your Mirakl price. Without channel-specific price rules in the ERP or OMS, a global price update propagates everywhere. On Amazon, price parity is a contractual obligation — selling cheaper elsewhere violates seller terms. Your OMS or ERP must manage per-channel price lists with explicit exception rules.
2. Not managing safety stock by channel
Reserving a safety stock buffer per channel — for example, 10% of available stock reserved for your own website, 20% for Amazon FBM — is a critical business rule. Without it, a sales spike on Amazon can leave your website entirely out of stock for 24 to 48 hours, with a direct impact on full-margin sales.
3. Ignoring marketplace returns and RMAs in the ERP
Marketplace returns (Amazon customer return, Mirakl return) must be recorded in the ERP as proper stock movements, with a quality control status. Without traceability, your ERP stock progressively diverges from physical reality — and you end up reselling products that are not in a condition to be sold.
4. Neglecting marketplace commission reconciliation in accounting
Every marketplace charges a commission on each sale, varying by product category. These commissions must be posted as expenses, line by line, to calculate real channel margin. Leaving them in Excel files outside the ERP is a frequent source of errors at quarterly close and complicates any channel-level profitability analysis.
5. Running an unmigrated Amazon MWS connector
The MWS API was officially decommissioned for its main sections from August 2023. An unmigrated ERP connector may continue to work partially via routes not yet fully cut — until the day Amazon definitively disables the last endpoints. Check the version of your connector with your ERP vendor or integrator now.
Checklist for Choosing Your Integration Solution
| Criterion | Native Connector | iPaaS (Celigo, Boomi, Make) | Dedicated OMS (ChannelEngine) |
|---|---|---|---|
| Number of active marketplaces | 1 to 2 | 2 to 5 | 5 or more |
| Orders per day | Under 500 | 500 to 5,000 | Over 1,000 |
| Target ERP | Single ERP | Multi-ERP possible | Native multi-ERP |
| Indicative annual budget | €5k to €20k | €15k to €60k | €20k to €100k |
| Internal IT resources required | Low | Medium | Medium to high |
| Typical deployment time | 4 to 8 weeks | 8 to 16 weeks | 12 to 24 weeks |
| Parallel FBA/FBM management | Partial | Configurable | Native |
To go deeper on your multi-channel IT architecture, two complementary resources on this blog: our article on ERP iPaaS integration architectures covers integration patterns between heterogeneous systems in detail. For companies structured around physical and online retail, our analysis of omnichannel retail ERP and stock management is also relevant for understanding how to centralise inventory across points of sale and digital channels.
