Marketplace Integration for E-Commerce: How It Works

Marketplace integration is the connection that moves product, price, stock, order and shipping data automatically between your own system (an ERP, a web store or an inventory tool) and marketplaces such as Amazon, Trendyol, Hepsiburada or N11. There are three ways to build it: connect directly to the marketplace API, use a multi-channel integrator that puts several marketplaces behind one interface, or switch on the module your e-commerce platform already ships. For a single marketplace and a store running its own software, a direct API build is typically 5-15 working days; if you sell on two or more channels, an integrator is almost always cheaper. Below are the differences between the three routes, the four flows an integration actually consists of, what it really costs and the mistakes that hurt sellers most.

What marketplace integration actually does

Marketplace integration is not one connection but four independent flows. When you collect quotes, ask about each of them separately — “we do marketplace integration” usually means only the first two:

• Catalogue publishing: opening your products against the marketplace category tree and its mandatory attribute schema. This is not a one-off job; every new product and every category change goes through it.
• Stock and price sync: updating quantity and price on the marketplace within minutes of your own stock changing. This is the most critical and most frequently broken part of the whole integration.
• Order retrieval: pulling the marketplace order into your system with customer, address, line items and commission data, and honouring the acceptance window.
• Shipping, invoicing and returns: generating the label from the marketplace carrier, issuing the invoice, and reflecting cancellations and returns back into your system.

All four run over the marketplace REST API. We covered the general concepts behind these flows in what is API integration; the difference here is that marketplace APIs also enforce commercial rules — acceptance windows, handling times, category commissions and return periods.

Three routes: direct API, integrator, built-in module

One question decides the route: how many marketplaces will you sell on, and where does the single truth about your stock live? Remember that this is a commercial decision, not a technical one.

• Direct API: you connect from your own software using the marketplace developer documentation. The right pick for a single marketplace, custom business rules (campaign pricing, multi-warehouse logic, separate B2B stock) and companies that already run an ERP. No subscription, but maintenance is yours: when the marketplace changes its API version, updating is your job.
• Multi-channel integrator: ready-made services that put several marketplaces behind one panel, priced monthly or as a share of revenue. On two or more channels they are almost always cheaper because development cost drops close to zero. The trade-off is flexibility: a business rule the panel does not support simply cannot be applied.
• Built-in platform module: the marketplace modules that Shopify and similar platforms ship. The fastest start — often a few hours of configuration if you already use the platform. Its limits are the platform’s limits.

A practical threshold: single channel plus your own software means direct API; two or more channels means an integrator. Connecting directly to three marketplaces means maintaining three API contracts forever, and that cost shows up not on the first invoice but in year two.

The hard part: catalogue mapping

What inflates timelines is not connecting to the API — it is the catalogue. A product in your database and a product as the marketplace expects it are not the same thing. They diverge in four places:

• Barcode requirement: most marketplaces require a valid GTIN/EAN to list a product. If you manufacture your own goods and have no barcodes, that is an operational problem to solve before the integration starts.
• Category tree: what you call “Women > Dresses” has its own id and mandatory fields on the marketplace. Each category needs its own mapping table.
• Mandatory attributes: fields like fabric, warranty period or country of origin vary by category, and a product with them empty never even reaches review. Most stores simply do not hold this data; it has to be produced.
• Variants: for colour-and-size products, stock is tracked at variant level. Until an item that looks like one product on your side is broken out by variant, accurate stock sync is impossible.

That is why half the effort in a realistic project goes into catalogue preparation. A week for 200 products and months for 20,000, this work costs more than the integration itself in stores with messy product data. If you are planning a store from scratch, we broke the budget down line by line in what it costs to build an e-commerce site.

Stock sync and overselling

When you sell the same item on your own site and on three marketplaces, there is only one truth: the quantity in the warehouse. The real job of the integration is to reflect that single truth in four places at once. When it fails, you get overselling — selling stock you do not have. Marketplaces answer that with performance penalties, a falling seller score and, if repeated, suspension.

A correct setup combines three defences: measuring the sync interval in minutes rather than hours, automatically delisting an item once it falls below a critical level, and sending a quantity that subtracts a safety buffer from real stock. On a fast-moving product, working without a buffer guarantees cancellations on campaign days.

Order, invoice and shipping flow

Once an order lands, the clock starts. Marketplaces require orders to be accepted and handed to the carrier within a set window, and delays are written straight into your seller score. This makes the order flow the part that most needs automation: the order enters your system, stock is reserved, the invoice is issued, a label is produced for the marketplace carrier, and the tracking number is written back to the marketplace.

We covered two links of that chain separately: e-invoice integration for the invoicing side and shipping carrier integration for dispatch and tracking. The notable difference on a marketplace is that you usually do not pick the carrier — the marketplace contract carrier is imposed and the label comes from its system.

Cost: what are you actually paying for?

Selling on a marketplace is never a single cost line, and the integration is the smallest part of it. Write out four items separately when you build your margin model:

• Commission: varies by category, and the spread between categories on the same marketplace is significant. Do not assume one rate; confirm the current rate for your categories in the seller panel.
• Service and transaction fees: per-order service charges, shipping contributions and campaign participation fees sit on top of commission.
• Integrator subscription: a fixed monthly or revenue-based fee on multi-channel services.
• Development and maintenance: one-off build on the direct API route plus a few API-change maintenance rounds a year. Catalogue preparation is a separate line and is missing from most quotes.

Setting marketplace prices before adding up those four items is the most common commercial mistake. A price that is profitable on your own site can lose money on a marketplace once commission and service fees are deducted.

Common mistakes

• Running stock sync hourly: on campaign days an hour is enough to sell the same unit dozens of times.
• One-way integration: pushing products and stock but pulling orders by hand from the panel. It works for a week and collapses as volume grows.
• Leaving returns and cancellations out of scope: if returns never come back into the system, stock and accounting drift apart within months.
• Managing price in more than one place: a campaign price edited by hand in the marketplace panel is overwritten on the next sync, and the campaign quietly breaks.
• Going live without a test environment: most marketplaces offer a sandbox. Experimenting on the live catalogue means hundreds of faulty products stuck in review.
• No logging or alerting: API errors pile up silently. Without a screen showing which product failed and why, the problem is only noticed when sales drop.

Conclusion

Marketplace integration is technically an API connection, but in practice it is catalogue discipline plus managing the truth about stock from a single source. Direct API is the right start on a single channel with your own software; an integrator is the right start on two or more channels — and in both cases, budget half the effort for catalogue preparation. If you would like a roadmap for connecting your system to marketplaces, take a look at our custom software development service or request a quote and we will define the scope together.