Marketplace Integration: Managing Stock, Prices, Orders and Invoices Across Every Marketplace From One Place

Marketplace integration is the automatic synchronisation of product, stock, price, order, shipping and invoice data between every marketplace you sell on and your own ERP. Stock is deducted from one pool, orders reach the ERP without retyping, and invoices and tracking numbers flow back. The risk of overselling drops sharply, and nobody has to hop between seller panels.

Why selling panel by panel eventually breaks

For a seller starting out on one marketplace with a few hundred products, downloading orders and updating stock by hand is manageable. With a few dozen orders a day and one warehouse, one person can handle it in part of their working day. Add a second marketplace and then your own web shop, and the same item suddenly has stock held in three places, three price points shaped by different commission structures and orders sitting in three separate screens. Stock updated in the evening can't see what sold elsewhere during the day.

The outcome is familiar: an out-of-stock item sells, the order is cancelled, the customer complains and your store rating drops. The warehouse tracks which order ships with which carrier from separate lists, while finance sees a marketplace payout land in the bank without knowing which orders it covers. We look at where this spreadsheet-driven way of working runs out of road in outgrowing spreadsheets.

What multichannel selling without integration costs

For most Turkish businesses that sell online, marketplaces are the main sales channel. According to TurkStat's ICT Usage Survey in Enterprises, 2025, 80.4% of enterprises making web sales in 2024 used online marketplaces, while only 51.6% sold through their own website or app. Competition is growing too: the Turkish Ministry of Trade's E-Commerce in Türkiye 2025 report puts the number of businesses engaged in e-commerce at 634,611 in 2025, up from 600,800 in 2024.

Even so, most sellers stay on a single marketplace:

According to the Ministry of Trade's E-Commerce in Türkiye 2025 report, 79.2% of businesses selling on marketplaces operate on just one; 13.7% sell on two and 4.6% on three.

In the same report's survey of 781 businesses, most of them micro-enterprises, 48.8% said they sell through both their own web shop and marketplaces. So a seller who expands to a second marketplace is taking a step most competitors haven't yet taken; but without integration, overselling, cancellations and manual data entry become the bottleneck that sets the pace of growth.

Which data should flow where in a marketplace integration?

Each type of data needs a single source of truth. The most common mistake is changing prices by hand in both the ERP and the marketplace panel, then not knowing which one is valid.

The stock line is only as good as your warehouse records. See our guides to a warehouse management system (WMS) for accurate bin-level stock and to handheld terminal stock counts for closing count differences. If you sell products with expiry dates, the rule for which batch ships first also affects the stock you publish.

The invoice line matters just as much, because every marketplace sale has to be documented with the right type of e-invoice. We explain the e-Archive and e-Invoice split, and how documents reach the Revenue Administration (GİB), in our e-invoice integration guide.

An 8-step plan for marketplace integration

1. Clean up product master data. Duplicate item cards, missing barcodes and inconsistent units surface as separate errors on every marketplace. We cover the method in data quality and duplicate records.
2. Map categories and attributes. Every marketplace has its own category tree and mandatory attributes. Map once and store the mapping centrally, and new listings go live faster.
3. Set up a shared stock pool and safety buffers. For low-stock items, rather than showing the full quantity on every channel, hold back a small buffer per channel to limit overselling during sync delays.
4. Write your pricing rules. Commission, shipping contributions and campaign participation differ by channel. Generate prices centrally from rules instead of editing them in each panel.
5. Connect the order flow to the ERP. An incoming order should reserve stock, create a sales record in the ERP and drop a pick list in the warehouse. We compare the technical options in API integration explained.
6. Automate shipping and invoicing. Labels should print as the order is picked, and the tracking number and invoice should return to the marketplace automatically. In warehouses shipping hundreds of orders a day, grouping orders through wave picking makes carrier cut-off times easier to meet.
7. Design the returns flow. Returned goods should be inspected and restocked, with the credit note and accounting entry created in the same flow.
8. Reconcile and monitor payouts. Each marketplace settlement report should be matched in the ERP against orders, commission and deductions, with anything that doesn't match dropped onto an exceptions list.

The last step is the one most often forgotten. Splitting a single marketplace payout across hundreds of orders and deductions is a textbook case of the rule-based matching we describe in bank reconciliation automation.

Which indicators show the integration is working?

Four indicators are enough to compare against the month before go-live:

• Stock-related cancellation rate: orders cancelled for lack of stock as a share of all orders. This is the most direct measure of how well the shared stock pool works.
• Order-to-dispatch time: the time from an order arriving to it being handed to the carrier. Marketplaces often use it when rating sellers.
• Orders touched by hand: orders corrected manually because the transfer failed. Don't expect zero, but do classify the causes.
• Reconciliation time: hours spent matching payout reports against ERP records.

Turkish regulations to keep in mind

Under Law No. 6563 on the Regulation of Electronic Commerce, e-commerce service providers in Türkiye, including those selling through marketplaces, must register with the Ministry of Trade's Electronic Commerce Information System (ETBİS); check the Ministry's ETBİS announcements for the current scope and conditions. For distance sales to consumers, the right of withdrawal set out in the Distance Contracts Regulation shapes your returns flow directly. Returns are therefore part of the integration core, not an afterthought.

On the invoicing side, sales to consumers are usually documented with an e-Archive invoice, while an e-Invoice must be issued when both seller and buyer are registered for e-Invoice. Buyers' names and addresses are personal data under KVKK, Türkiye's Personal Data Protection Law No. 6698; data collected for delivery should not be reused for other purposes without a legal basis, and retention periods and access rights need defining.

Off-the-shelf connector or bespoke integration?

There are ready-made services that manage several marketplaces from one panel. If your product range is simple, your ERP talks to them directly and your warehouse process is standard, one can be a quick start. With variants and bundles, multiple warehouses, reservations coming from production, custom ERP fields, or B2B and marketplace orders shipping from the same warehouse, the gaps end up being closed by hand again.

We set out the decision criteria in custom versus off-the-shelf software. If you also sell to dealers, see our B2B ecommerce ERP integration guide for connecting the same ERP to your trade channel.

After integration: putting the data to work

Once every channel meets in the same data, you can see which product earns how much, on which marketplace and after which commission. Sales history also becomes the core input for retail inventory optimisation. If you also run physical shops, our retail and chain store solutions bring store stock into the same pool. And customers asking "where's my order?" can be answered by a customer service chatbot connected to order and shipping data.

How we do this at Digital Bridge

We build e-commerce platforms that connect marketplaces, your own web shop and your B2B channel to the same stock and order data, shaped around your business rules:

• Discovery and requirements analysis. We map the channels you sell on, your product structure, pricing and commission rules, warehouse flow and returns process, and decide who owns each type of data.
• We connect the hub. Marketplace seller APIs, your ERP, carriers and your e-document provider are brought into one flow as part of our API integration work. If your ERP can't carry the load, we look at the ERP side too.
• We speed up the warehouse. The flow from order to pick list, label and dispatch is built with warehouse and inventory management software and handheld terminals.
• We start with a pilot. We begin with one marketplace and a limited product group, add further channels once stock and order flows are proven, and log every transfer on a monitoring screen.

For product images, spec sheets and marketplace agreements, SmartFiles from our Smart360 family keeps files in department-based storage areas and saves every upload with the same name as a new version. We don't sell packaged software; scope, phases and cost are set out in a written proposal after the requirements analysis.

Next step

Take three numbers from last month: how many orders were cancelled for lack of stock, how many were keyed into the ERP by hand, and how many hours marketplace payout reconciliation took. Bring that table to us via our contact page and we'll work out an integration scope for your channels. More guides are collected under Software Development.