80 percent of people in Germany search online for information about goods and services, and 70 percent bought or ordered online in the past three months (Destatis). A considerable share of that search does not start in a merchant's own shop but on a marketplace. For online shop operators, this means: the marketplace is not a side channel but a distribution channel of its own, with its own technology, its own product data requirements and its own legal duties. In this guide you will learn how technical marketplace integration works, which platforms matter for the German market, and what the Regulation on online intermediation services and the Digital Services Act mean for merchants.
Marketplaces as a Second Distribution Channel
Retail trade in Germany posted 2.7% higher revenue in real terms in 2025 than in the previous year (Destatis). Internet and mail order retail grew by 10.1% over the same period (Destatis). The gap between the two figures is the actual finding: online trade is growing markedly faster than retail as a whole. How much of that runs through marketplaces is not reported separately by official statistics – and platform-level share figures are not available in a form that can be verified. For e-commerce merchants, the question therefore remains one about their own numbers: how much revenue today comes from channels other than the shop itself?
Anyone selling on a marketplace is, in legal terms, a business user of an online intermediation service. Regulation (EU) 2019/1150 obliges the provider to set out in its terms and conditions the main parameters determining ranking and the reasons for their relative weighting. For merchants this is the only solid basis for assessing the visibility of their own listings: what decides the value of a channel is not a ranking of platforms but whether your assortment is found there under the disclosed rules.
| Marketplace | Interface | Technical Characteristic |
|---|---|---|
| Amazon.de | SP-API (Selling Partner API) | Access via OAuth 2.0, optional FBA connection |
| Zalando | Partner API | Fashion attributes, size charts, curated assortment |
| eBay.de | REST API (replacing Trading API) | Auction and fixed price in one catalog |
| OTTO Marketplace | OTTO Partner Connect (REST) | Approval step per category before listing |
| Kaufland.de | Marketplace API | CSV and API feeds, focus on FMCG and household goods |
The marketplace landscape keeps shifting: platforms open up to third-party sellers, others curate more strictly, category boundaries move. Publicly available figures on trading volume and growth of individual platforms mostly come from market reports that do not disclose their population or methodology – which is why we do not reproduce them here. For planning purposes, what matters is less the ranking than whether your technical integration can carry another channel without an additional manual process.
What Speaks for a Second Distribution Channel
The benefit of a second channel is structural: selling exclusively through your own shop reaches the people who already know it or find it through a search engine. Being listed on a marketplace as well puts your assortment into a search that usually already carries purchase intent. We deliberately do not reproduce revenue-uplift figures from individual vendors – they come from surveys whose population is not disclosed. What the omnichannel strategy formulates as a core principle applies unchanged: customers expect availability where they search.
The second point concerns customer retention, and it is less favorable: a marketplace purchase happens on the platform, not in your shop. What access merchants have to the data arising from it must be explained by the provider in its terms and conditions under Article 9 of Regulation (EU) 2019/1150 – including the case where no such access exists. Reading that section before integrating tells you what the channel delivers beyond the individual sale, and what it does not.
Reach Without Own Marketing
On a marketplace your assortment appears in a search that usually already carries purchase intent – without having to build that reach yourself.
One Catalog, Several Channels
Product data maintained cleanly once can be distributed to several platforms through transformation rules instead of being maintained again per channel.
Disclosed Ranking Rules
Providers of online intermediation services must set out the main ranking parameters in their terms and conditions (Regulation (EU) 2019/1150).
How many channels make sense cannot be generalized: it depends on the assortment, the margin and how much maintenance the product data can bear. What matters is not the number but that every additional channel runs through the same integration (Amazon integration) and does not create a manual process of its own. A second marketplace maintained by spreadsheet costs more than it brings in.
Do not launch on all marketplaces simultaneously. Start with the channel that has the highest relevance for your product category – typically Amazon for most industries, Zalando for fashion, or OTTO for the premium segment. Once processes are stable, expand to the next marketplace. The reason is mundane: every platform has its own category trees, its own mandatory attributes and its own approval steps. Learning two of them at once costs time on both.
Key Marketplaces in Detail
Amazon Marketplace: The Dominant Channel
Amazon is the obvious first channel for most assortments. Amazon integration is done via the SP-API (Selling Partner API), which replaces Amazon MWS. Access runs through OAuth 2.0: the connecting application obtains limited access to the seller account without knowing its credentials (RFC 6749). The SP-API enables automated exchange of product data, orders, inventory levels and shipping information.
For the technical connection to your online shop, several integration levels are relevant: product feed with EAN/GTIN mapping, automated order import into the shop system, bidirectional real-time inventory sync, and FBA connection for Prime shipping. On top of that comes a tax duty borne not by the merchant but by the platform: under section 22f of the German VAT Act the operator of an electronic interface records the supplies of the traders selling through it, and under section 25e it is liable for VAT left unpaid on those supplies. In practice this means for merchants: incomplete or incorrect master data leads to account suspension, not to a follow-up question.
- SP-API Integration: Product upload, order retrieval, real-time inventory sync via the REST-based Selling Partner API
- FBA Connection: Automated warehousing, Prime shipping, and returns management through Amazon's logistics network
- A+ Content and Brand Registry: Enhanced Brand Content for higher conversion synced directly from your PIM system (blog article on PIM implementation)
- Advertising API: Data-driven Amazon PPC campaign management with automated reporting to your BI system
- Repricing: Dynamic price adjustment based on competition and demand data via the Notifications API
eBay: Broad Assortment, Loyal Buyer Base
eBay remains a market of its own above all for collectibles, electronics and automotive, with a loyal buyer base. The eBay REST API is gradually replacing the older Trading API and offers modern integration options. Anyone running both in parallel should plan the migration early: the attribute models differ, and the older interface no longer receives new fields.
For merchants already selling on Amazon, eBay is the logical second channel: product data can be largely reused, and the integration effort is manageable with existing middleware infrastructure. For price presentation the same rule applies on every channel as in your own shop: anyone offering goods to consumers must state the total price (section 3 of the German Price Indication Ordinance).
OTTO and Kaufland: German Alternatives with Potential
The OTTO Marketplace positions itself as a curated alternative: the platform does not accept every assortment and reviews before activation. Integration is done via OTTO Partner Connect with a REST API interface. For merchants the approval step means a longer lead time, but your offer meets fewer identical competing listings there than on open platforms.
Kaufland.de has its focus on FMCG and household goods – a segment where competitive density looks different from the general assortment. Zalando is the obvious channel in fashion, but requires domain-specific attributes such as size charts and material details that many shop systems do not hold as dedicated fields. All platforms can be managed through a central integration solution – the difference lies not in the transfer but in preparing the product data per target.
Technical Architecture of Marketplace Integration
A professional marketplace integration is built on three pillars: the central product feed, bidirectional inventory synchronization, and automated order processing. Without these foundations, overselling, inconsistent product data, and manual errors emerge that compromise both customer satisfaction and marketplace rankings. Consistent product data across all channels is not a matter of convenience: a listing that states different dimensions or a different scope of delivery on one platform than on the next produces returns and reviews that hit both channels.
Central Product Feed
Product data is maintained once in the shop or PIM system and transformed marketplace-specifically: category mapping, attribute assignment, EAN/GTIN maintenance, and image-optimized variants.
Real-Time Inventory Sync
Bidirectional inventory synchronization in real-time or near-real-time (5–15 min intervals) prevents overselling and cancellations across all connected channels.
Order Automation
Orders from Amazon, eBay, OTTO, and other marketplaces flow automatically into the central ERP or shop system – including shipping confirmation and tracking.
Repricing and Monitoring
Automated price adjustment based on competitive data and marketplace algorithms while maintaining minimum margin requirements.
Middleware vs. Direct Integration
For integration architecture, two approaches are available: direct integration via native API connections and middleware-based integration via central connectors. For merchants with more than two marketplaces, the middleware solution is typically more economical, as it centralizes maintenance effort and controls cross-marketplace processes like inventory sync and order routing in one place. Our guide on middleware integration describes the architecture in detail.
| Criterion | Direct Integration | Middleware Solution |
|---|---|---|
| Effort per Marketplace | High (separate integration each) | Low (configure once) |
| Inventory Sync | Individual per channel | Central across all channels |
| Scalability | Linearly increasing effort | New channels quickly added |
| Data Sovereignty | Full control | Depends on provider |
| Typical Use Case | 1–2 marketplaces | 3+ marketplaces |
| Cost (Setup) | Medium per channel | Higher initial, cheaper to scale |
The choice of the right architecture depends on assortment size, number of target marketplaces, and existing IT landscape. If fulfillment is outsourced, you additionally need clean feedback of shipping and inventory events into your own system – otherwise two inventory states run side by side, and overselling becomes a matter of time. Connecting a PIM system (blog article on PIM implementation) significantly simplifies product data maintenance across all channels.
Product Data Management for Multi-Marketplace
A key operational challenge in marketplace integration is product data management. Every marketplace has its own requirements for category structures, mandatory attributes, image formats, and product descriptions. Amazon requires detailed backend keywords and A+ Content, eBay relies on Item Specifics and Condition Descriptors, OTTO expects ICECAT-compliant attribute sets. Without central data management, the effort multiplies with each additional channel.
The solution lies in a central PIM system that serves as the single source of truth for all product data. From there, data is transformed marketplace-specifically and distributed via middleware or direct connections. Integration with the Google Merchant Center follows the same principle – one central feed, multiple output channels. The effort thus shifts from repeated maintenance per channel to maintaining the transformation rules once.
- EAN/GTIN stored and validated for all products
- Category mapping defined for Amazon, eBay, OTTO, and other target platforms
- High-resolution product images on white background available (check minimum dimensions per platform)
- Marketplace-specific mandatory attributes fully maintained
- Automated feed generation from PIM or shop system configured
- Repricing rules with minimum margin defined
- Inventory buffer for multi-channel configured (prevent overselling)
Fulfillment Strategy: FBA, Self-Shipping, or Hybrid?
The fulfillment decision directly impacts conversion, costs, and customer satisfaction. Amazon FBA offers Prime eligibility and thus access to the most purchase-ready customer group on Amazon, but incurs storage fees and reduces margins. Self-shipping through your own logistics system gives full control but does not achieve Prime status. Multi-Channel Fulfillment (MCF) from Amazon enables shipping eBay and OTTO orders through Amazon's warehouse.
In practice, a hybrid model has proven effective: FBA for high-volume Amazon orders with short delivery times, self-shipping for other marketplaces with individual packaging and branding. The technical challenge lies in inventory splitting: how much goes to Amazon's warehouse, how much stays in your own? An intelligent ERP integration manages this distribution automatically based on sell-through rates and seasonality.
Platform Operator Duties That Affect Merchants
Since Regulation (EU) 2022/2065 (Digital Services Act), online platforms allowing consumers to conclude distance contracts with traders carry concrete duties towards their merchants. Article 30 requires that traders may only use the platform once they have provided certain information – from address and payment account through to the trade register number. Article 31 requires an interface that enables traders to comply with their pre-contractual information, compliance and product safety obligations. For integration this means: these mandatory details belong in the product feed and in master data maintenance, not in a downstream manual step.
Besides the large marketplaces there are price comparison sites and specialist platforms that can be connected through standardized feeds. Whether such a channel pays off is not decided by the platform's reach figure but by how often your assortment appears there in a search with purchase intent, and at what price it can compete. Technically, adding them to your multi-channel architecture is feasible through standardized feeds and APIs; the effort lies in maintaining category and attribute mapping.
Common Challenges and Solutions
Marketplace integration comes with specific challenges that lead to significant problems without professional planning. Typical pitfalls involve inventory consistency, price parity, data quality, and compliance with platform-specific guidelines.
Prevent Overselling
Without real-time inventory sync, overselling occurs when simultaneous orders come in across multiple channels. Solution: safety stock buffers and event-based sync mechanisms with max 5-minute latency.
Manage Price Parity
Amazon penalizes prices that are lower on other channels by removing the Buy Box. Solution: cross-channel repricing with defined price corridors and minimum margins.
Maintain Category Mapping
Each marketplace has its own category trees and mandatory attributes. Solution: central PIM with marketplace-specific transformation rules and automated validation.
Handle API Changes
Marketplace APIs change regularly (e.g., Amazon MWS to SP-API transition). Solution: abstraction layer in middleware that absorbs API updates without changing shop logic.
Amazon takes prices on other platforms into account. If a product is offered more cheaply elsewhere, the listing can lose the Buy Box. Since the Buy Box carries the purchase button, this directly affects orders. A cross-channel pricing strategy is therefore not optional but business-critical – and the total price to be stated applies equally on every channel (section 3 of the German Price Indication Ordinance).
Implementation in 5 Phases
Successful marketplace integration follows a structured process from analysis to ongoing operations. With existing shop infrastructure, expect several weeks per marketplace as a rule; catalog size and data quality determine the schedule.
- Analysis and Strategy: Marketplace selection based on assortment, target audience, and competitive analysis. Definition of pricing strategy and fulfillment models per channel.
- Product Data Preparation: EAN/GTIN validation, category mapping, image optimization, and creation of marketplace-specific product texts. Integration with PIM system or building a central data repository.
- Technical Integration: API connection or middleware configuration, inventory sync setup, order routing, and shipping integration. Testing phase with limited assortment.
- Go-Live and Optimization: Activation of the complete assortment, monitoring of performance metrics, and fine-tuning repricing, inventory buffers, and feed quality.
- Ongoing Operations: Monitoring marketplace KPIs, API maintenance, assortment expansion, and continuous optimization of advertising campaigns and product listings.
The critical success factor is product data quality: incomplete or incorrect data leads to rejected listings, poor rankings, and high return rates. Investing in professional data enrichment and structured product data pays off across all channels – not least for visibility in Google search.
Costs, ROI, and Profitability
The cost of a marketplace integration consists of the one-time integration fee, ongoing marketplace commissions and optional advertising budgets. How high the commission turns out to be is set out in the provider's terms and conditions; under Article 3 of Regulation (EU) 2019/1150 these must be drafted in plain and intelligible language and be easily available at all times, and every proposed change must be notified to affected merchants in advance on a durable medium. So do not calculate with a commission rate from a market report, but with the terms that apply to your contract.
Commission rates differ considerably by platform and category and they change; what is binding is always the provider's current fee schedule. What matters for the calculation is not the rate alone but the overall picture compared with Google Ads or social media: on a marketplace your offer meets a search that usually already carries purchase intent, yet visibility stays permanently tied to the commission. Your own channel costs more upfront and builds reach that stays. Anyone running both should track cost per order separately by channel.
The figures in this article come from the German Federal Statistical Office: internet use and online purchases by private individuals, and retail revenue for 2025. The legal requirements come from Regulation (EU) 2019/1150 on online intermediation services, Regulation (EU) 2022/2065 (Digital Services Act), sections 22f and 25e of the German VAT Act, section 3 of the German Price Indication Ordinance and RFC 6749. We deliberately do not list market share, trading volume or return figures for individual platforms: they regularly stem from surveys whose population and methodology are not disclosed and that cannot therefore be verified.
Frequently Asked Questions About Marketplace Integration
It depends on the assortment. Amazon is a broad channel across many categories, eBay is strong in collectibles, electronics and automotive, OTTO curates in the premium segment, Zalando in fashion, Kaufland.de in FMCG and household goods. Publicly available market share figures for individual platforms mostly stem from surveys without disclosed methodology – a marketplace analysis against your own assortment helps more with prioritization than a ranking.
In our experience project duration runs to a few weeks per marketplace, provided the shop infrastructure is in place. The effort depends on assortment size, data quality, and the chosen integration method. When using a middleware solution, connecting additional marketplaces is usually faster since the base architecture is already in place. Product data preparation is typically the most time-intensive step.
Costs consist of three components: the one-time integration fee for technical connection, ongoing marketplace commissions, and optional advertising budgets. Commission rates differ by platform and category and they change; what is binding is the provider's fee schedule, which under Article 3 of Regulation (EU) 2019/1150 must be drafted in plain and intelligible language and be easily available. Calculate with the terms that apply to your contract.
Overselling occurs when orders come in simultaneously across multiple channels without timely inventory synchronization. The solution consists of three elements: bidirectional inventory sync with short latency, a safety stock buffer per channel, and event-based sync mechanisms that immediately update inventory across all channels upon each order. A professional middleware integration ensures this.
With more than 500 products and two or more marketplaces, a PIM system (blog article on PIM implementation) is typically a sound economic investment. Each marketplace has its own requirements for categories, attributes, and product texts. Without central data management, manual effort multiplies with each additional channel. The PIM serves as the single source of truth and feeds marketplace-specific feeds through transformation rules.
The decision depends on your assortment, margins, and shipping complexity. FBA offers Prime eligibility and thus visibility with customers who filter for it. The downside: storage fees and reduced margins, which can tip the calculation on low unit prices. A hybrid model has proven effective in practice: FBA for high-volume Amazon bestsellers, self-shipping for other marketplaces with individual packaging. The shipping integration manages both paths automatically.