Short answer: what a WooCommerce Amazon integration should do
A proper WooCommerce Amazon integration keeps one source of truth for stock (WooCommerce or your ERP), pushes available quantities to Amazon within a minute of every change, and pulls Amazon orders back so they reduce the same stock. The same pattern extends to bol.com and Kaufland. You can get there with a plugin, a multichannel tool or a custom integration; the right choice depends on catalogue size, variants and where your stock really lives.
If you sell a few hundred simple products on one or two marketplaces, a tool is usually enough. If an ERP owns stock, you run several warehouses or FBA alongside your own fulfilment, a custom sync removes daily manual fixes.
Why marketplace stock gets out of sync
Overselling rarely comes from one big failure. It comes from small delays that add up:
- Sales in other channels. A unit sold on your site, in a shop or on bol.com is still live on Amazon until something updates it.
- Slow order import. If Amazon orders arrive in WooCommerce every hour, that unit is sold twice in the meantime.
- Mismatched identifiers. A variation SKU in WooCommerce does not match the seller SKU on Amazon, so the update silently goes nowhere.
- Manual edits in Seller Central. Someone fixes a quantity by hand and the next sync overwrites it, or does not.
- Bundles and kits. A gift set uses three components; selling the set must reduce all three.
Every cancelled order hurts. Amazon tracks your pre-fulfilment cancel rate and expects it below 2.5% for merchant-fulfilled orders;1 bol.com and Kaufland have similar performance scores. Breaching them costs visibility and, eventually, your account.
Which option fits your store?
| Criterion | WooCommerce plugin (e.g. WP-Lister for Amazon) | Multichannel tool (Linnworks, ChannelEngine, Channable, Base.com) | Custom integration |
|---|---|---|---|
| Setup cost | low | low to medium | fixed-price project |
| Monthly cost | licence | subscription, often by orders or channels | hosting and maintenance |
| Marketplaces covered | usually one per plugin | dozens | the ones you need |
| Stock from an ERP | rarely | via connectors | yes, two-way |
| Bundles and kits | limited | good | fully custom |
| Per-channel pricing rules | basic | good | any logic |
| Data ownership | your server | the vendor's platform | your server |
A plugin is enough when WooCommerce is your only stock record, you sell on one marketplace and volumes are modest.
A multichannel tool fits when you sell on three or more marketplaces with a standard catalogue. It becomes the order hub; WooCommerce becomes one channel among several.
A custom integration pays off when Business Central, SAP or another ERP is the stock master, you have thousands of variants, or you need logic the tools do not offer: different margins per marketplace, channel exclusions by brand, per-warehouse availability.
How the APIs differ: Amazon, bol.com and Kaufland
| Amazon | bol.com | Kaufland | |
|---|---|---|---|
| API | Selling Partner API (SP-API) | Retailer API | Seller API |
| Stock update | Listings Items API or JSON listings feed | offer stock endpoint | unit (offer) update |
| Orders | Orders API plus notifications | orders endpoint | order units endpoint |
| Own-warehouse model | Fulfilment by Amazon (FBA) | Logistics via bol (LVB) | Kaufland fulfilment in some markets |
| Fee model | monthly plan plus referral fee per category | commission per category plus fixed fee per item | monthly basic fee plus commission per category |
| Markets | UK, DE, NL, US and more | NL, BE | DE, AT, CZ, SK, PL, FR, IT, NL and others |
Fees change often, so check each seller portal before you price. As a guide: Amazon's Professional plan is £25 a month in the UK and €39 in Germany (excluding VAT), plus a referral fee that depends on the category. bol.com charges a category commission made up of a percentage and a small fixed fee per item that depends on the selling price. Kaufland lists commissions of 7–16% depending on category (13% for most), plus a basic monthly fee from €39.95 excluding VAT.
On Amazon, the older XML and flat-file listings feeds have been retired in favour of the Listings Items API and the JSON listings feed. If a plugin you are evaluating still relies on the old feed types, treat it as a warning sign.
Step by step: building a stock sync that does not oversell
- Pick the stock master. Either WooCommerce or the ERP holds the real number. Marketplaces only ever receive a calculated "available to sell" figure; they never write stock back.
- Map identifiers. Every WooCommerce product or variation gets one seller SKU per marketplace, stored on the product. Use stable IDs, not names, and keep the EAN or GTIN consistent across channels.
- Calculate available stock per channel. Available = physical stock minus open orders minus channel buffer. For FBA or LVB, keep a separate pool.
- Push on change, not on a timer. Hook into stock changes (order placed, refund, ERP update) and queue an update. In WooCommerce, Action Scheduler handles the queue so the admin stays fast.
- Batch and respect rate limits. Marketplace APIs throttle requests. Group changes every few seconds and retry with back-off on throttling errors.
- Import orders fast. Use push notifications where offered (Amazon's notifications, webhooks) and poll every one to five minutes as a fallback. Create the order in WooCommerce with the channel as source, reduce stock, and suppress WooCommerce customer emails.
- Send shipping back. When the parcel ships, send carrier and tracking to the marketplace so the order is confirmed on time.
- Reconcile nightly. Compare every offer's quantity and price with the master and fix differences. Log what changed, so you can see which channel drifts.
Stock pools: FBA, LVB and your own warehouse
Fulfilment by Amazon and Logistics via bol (LVB) change the maths. Units you have sent to their warehouses are no longer yours to sell elsewhere, so treat them as separate pools:
| Pool | Who sells it | Synced from | What you sync |
|---|---|---|---|
| Own warehouse | website, merchant-fulfilled Amazon, bol.com, Kaufland | WooCommerce or ERP | available quantity, every change |
| Amazon FBA | Amazon only | Amazon | read-only: inbound, available, reserved |
| bol.com LVB | bol.com only | bol.com | read-only: stock at bol, replenishment needs |
The integration reads FBA and LVB levels to plan replenishment, but never pushes your own warehouse stock to those offers. A common mistake is a plugin that sets the FBA SKU quantity from WooCommerce stock, which at best fails and at worst mixes up fulfilment channels on the listing.
Per-channel pricing that protects your margin
Marketplace fees mean the same price earns you less on every channel. Decide the rule once and let the integration apply it:
| Channel | Fee assumption | Site price | Channel price rule | Channel price |
|---|---|---|---|---|
| Your website | payment fee ~1.5% | €100.00 | base | €100.00 |
| Amazon | referral 15% | €100.00 | site price × 1.15, round to .99 | €114.99 |
| bol.com | commission ~12% + fixed fee | €100.00 | site price × 1.12 + €1, round to .99 | €112.99 |
| Kaufland | commission ~10% | €100.00 | site price × 1.10, round to .99 | €109.99 |
Fee assumptions are examples; use the rates in your own seller accounts. Keep a floor price per product as well, so a supplier price drop or a repricing tool can never push a channel below cost.
Common errors and what they mean
- Amazon error 85412: your listing data conflicts with the existing Amazon catalogue entry for that ASIN. Check title, brand and identifiers against the ASIN you are matching.
- Amazon error 8572: the UPC or EAN you submitted does not match the product. Use the brand owner's GS1-registered GTIN, not a barcode bought from a reseller; Amazon may ask for a GS1 certificate or brand authorisation.
- HTTP 429 Too Many Requests: you are over the API rate limit. Batch updates and back off.
- Stock stays at zero after a restock: the update went to the wrong seller SKU or was blocked by a manual change. Reconciliation logs will show it.
- Orders appear twice in WooCommerce: the importer does not store the marketplace order ID as a unique key. Make import idempotent.
- Bundles oversell: component stock is not linked to the kit. Compute kit availability from its scarcest component.
What does marketplace integration cost?
Ranges below are market estimates excluding VAT and excluding marketplace fees.
| Option | One-off (estimate) | Monthly (estimate) | Best for |
|---|---|---|---|
| WooCommerce plugin for one marketplace | €0–€300 | licence or €0 | small catalogue, one channel |
| Multichannel tool | €0–€1,500 onboarding | €50–€900, grows with orders | 3+ channels, standard catalogue |
| Custom marketplace module | €2,000–€6,000 | part of maintenance | ERP, variants, own rules |
| ERP plus multi-marketplace hub | Enterprise quote | SLA | high volume, several warehouses |
At Raao, marketplace sync is an add-on module for an existing store or part of the Enterprise package; see pricing. You get a fixed quote after a free 30-minute call, pay 30% upfront and the rest by milestone, with no sales commission and no licence fees. Hosting and maintenance start at €89 a month and include monitoring of sync jobs.
The maths is simple: if a tool costs €450 a month, a custom module usually pays back within 12–18 months, and you own it. If your catalogue is small and standard, the tool is the better deal, and we will tell you so.
Marketplaces also need clean product data. The same catalogue that feeds Amazon should feed Google; our guide to the WooCommerce Google Shopping feed covers that side.
How we did it for Kuiba
Kuiba is not an Amazon seller, but it solves the same core problem: a large catalogue that must reach several channels accurately without manual data entry.
- A custom store with 10,000+ configurable products from 25+ European brands, kept current by automated supplier imports with AI-assisted category mapping.
- Google Merchant, Meta, TikTok and Pinterest feeds generated from that one catalogue, so price and availability come from a single source.
- Orders pushed automatically to Microsoft Business Central through the client's CRM layer.
- Thousands of products and combinations managed without manual data entry.
Adding a marketplace to a store like this is the same architecture with one more channel: one stock master, a sync queue and nightly reconciliation. See what else we connect on our ecommerce page, or book a free 30-minute call to walk through your catalogue.
Based on Amazon Seller Forums posts and Seller Central account health pages, which show the 2.5% pre-fulfilment cancel rate target; Amazon can change account health targets. Checked October 2026. ↩
Amazon does not publish a public reference for listing error codes; the meanings of 8541 and 8572 are based on Amazon Seller Forums answers and third-party guides. Checked October 2026. ↩