ERP for Marketplace Sellers — software for Amazon, eBay, Otto, Kaufland, real.de
A marketplace seller does not run an online shop; they run a portfolio of selling channels across Amazon, eBay, Otto, Kaufland, real.de (now Kaufland.de), Zalando Marketplace and increasingly TikTok Shop and Temu. Each marketplace has its own category structure, image requirements, listing rules, return policies, payout schedule and fee structure. An ERP for marketplace sellers therefore has to behave less like a classic e-commerce shop system and more like a multi-channel data hub: a single product master that pushes channel-specific listings, a single inventory pool that synchronises across all channels in seconds, per-channel pricing rules that respect minimum margins, and a unified order stream that flows into one fulfilment process. Mismanaged inventory sync is the dominant cause of marketplace suspensions; mismanaged pricing is the dominant cause of margin erosion.
Requirements
The first requirement is real-time multi-marketplace inventory synchronisation. If 50 units of an item are listed on Amazon, eBay and Kaufland simultaneously and an order arrives on Amazon, the eBay and Kaufland listings have to update within minutes — otherwise the seller risks selling stock they no longer have, which triggers metric penalties (ODR on Amazon, defect rate on eBay) and eventually account suspension. The ERP has to be the single source-of-truth and push updates via marketplace APIs at high frequency.
The second is fulfilment-model heterogeneity: Amazon FBA (Fulfilment by Amazon) means the seller ships pallets to Amazon warehouses and Amazon picks-packs-ships; eBay typically means self-fulfilment from the seller's own warehouse; some sellers run a hybrid model with FBA for fast-moving SKUs and self-fulfilment for tail SKUs. The ERP has to track inventory in each fulfilment location separately and produce a unified view for re-stocking decisions. The third is cross-border VAT under OSS (One-Stop-Shop) for B2C below the EU-wide €10,000 threshold and country-specific VAT registrations above it, plus IOSS for sub-€150 imports.
Mandatory functions
Mandatory functions for a marketplace-seller ERP: multi-channel listing management with marketplace-specific attribute mapping (Amazon flat-file, eBay category templates, Otto attribute set, Kaufland feed format); real-time inventory sync via marketplace APIs (Selling Partner API for Amazon, eBay Sell API, Otto Partner API, Kaufland Marketplace API); per-channel pricing rules with minimum-margin enforcement; automated repricing integration with tools like RepricerExpress, BuyBoxBuddy or Aura for Amazon Buy Box optimisation.
On the fulfilment side: FBA shipment planning, FBA inbound creation, FBA inventory reconciliation, self-fulfilment warehouse management with carrier integration (DHL, DPD, GLS, Hermes, UPS), label printing, return handling. On the financial side: marketplace-fee reconciliation against payout statements (Amazon settlement reports, eBay financials), OSS-VAT calculation per destination country, IOSS handling for sub-€150 imports, integrated DATEV export and a clean P&L by marketplace and SKU to understand which combinations actually make money after fees and returns.
Vendor landscape
The German-speaking marketplace-seller ERP landscape is dominated by vertical specialists. plentyOne (formerly plentymarkets) is the long-time market leader for multichannel and marketplace sellers in DACH, with the broadest set of pre-built marketplace connectors and a strong B2B-distributor heritage. JTL-Wawi is the price-sensitive option with strong Amazon and eBay coverage, popular in the under-€10 mEUR turnover segment. Xentral targets digital-native sellers with a more modern UI and a cloud-first deployment model.
Tradebyte (now part of Zalando) is a marketplace-integration middleware rather than a full ERP, typically combined with an upstream ERP for finance. ECOM World and Afterbuy serve specific niches. On the international side, ChannelEngine, ChannelAdvisor and Linnworks compete for cross-border sellers. Larger sellers above €30 mEUR turnover often move to Microsoft Dynamics 365 Business Central or NetSuite with a marketplace-integration layer (CedCommerce, Modern Bazaar) because the financial-accounting depth of the vertical specialists becomes a constraint.
Trends and outlook
Three trends are reshaping the segment. First, the rise of TikTok Shop, Temu and Shein as new marketplaces with different listing logic and aggressive pricing dynamics forces ERP vendors to add connectors at a higher cadence than ever. Second, Amazon's ongoing changes to FBA fee structures (storage, removal, ageing inventory) push sellers to model FBA economics inside the ERP rather than after-the-fact, which raises the bar for cost-allocation logic.
Third, the EU's General Product Safety Regulation (GPSR) in force from December 2024 and the upcoming Digital Product Passport (DPP) require sellers to attach safety-information and material-composition data to listings, which has to live in the ERP master and be pushed per marketplace.
Related Topics
Frequently Asked Questions
Can we run marketplace sales out of a generic ERP or out of Shopify directly?
Below roughly €1–2 mEUR turnover with one or two marketplaces: Shopify plus a connector app (Codisto, Marketplace Connect) can work. Above that, the absence of integrated FBA management, per-channel pricing rules and OSS-VAT logic typically costs more in operational overhead than the licence delta to plentyOne, JTL or Xentral. Generic ERPs without a marketplace-integration layer are almost never the right answer for serious marketplace sellers.
How critical is real-time inventory sync versus near-real-time?
For top-velocity SKUs (more than 10 units per day across channels): real-time matters because the cost of overselling is high — Amazon ODR penalties, eBay defect-rate impact and account-suspension risk. For long-tail SKUs: a 5–15 minute sync window is fine. Vendors that publish their sync latency transparently and offer webhook-driven push (rather than only polling) are operationally safer.
What does OSS-VAT mean for the ERP requirement?
OSS (One-Stop-Shop) lets sellers report cross-border B2C EU sales centrally instead of registering for VAT in each destination country, but only below the EU-wide €10,000 threshold. Above the threshold, the destination-country VAT rate applies per sale, which the ERP has to calculate correctly and which has to be reported quarterly. ERPs that ship pre-built OSS reports and per-country VAT-rate tables save the seller from a manual Excel reconstruction that becomes painful above ~5,000 cross-border orders per quarter.