Choosing marketplace integration software: tests to run in the demo

Search for marketplace integration software and the first page is largely filled by the companies selling it. The feature lists look alike: connections to Amazon, eBay and your own store, stock sync, bulk price updates, shipping labels. When the lists match, the decision often comes down to price or to how well the person running the demo presents.

This article recommends no particular tool. It sets out how to test one in the demo and which answers to get in writing before you sign, and towards the end it looks at where an off-the-shelf tool reaches its limits. There is no single answer to "which is the best marketplace integration software?" Run the tests below with your own products and your own workflow, and it becomes clear which tool fits your business.

What does an integration tool bring into one place?

An integration tool usually moves six kinds of data: product information, stock, prices, orders, invoices and shipping labels. Before the demo, find out which direction each one flows in.

• Products and prices usually flow from the tool to the marketplace. If you change a price by hand in the marketplace's seller dashboard, does the change come back to the tool, or is it overwritten with the old price at the next sync?
• Stock has to flow both ways. The sale happens on the marketplace, the reduction reaches the tool and from there it is passed on to the other channels.
• Orders come from the marketplace into the tool; status updates such as dispatched and delivered go back.
• Invoices and shipping labels raise one question: does the tool produce them itself or hand them over to other software?

With a one-way flow, every correction made in the marketplace dashboard can disappear at the next sync. You can see this in the demo. Ask the vendor to change a product's price in the marketplace dashboard and watch together what happens in the tool.

If your product data comes from a supplier as an XML or CSV feed, the chain gains one more link. The tool reads the supplier's file at set intervals and sends the products to the marketplace through its own connection. In that case, ask whether the rule between the supplier's price and your selling price, meaning margin and rounding, can be set separately for each channel.

How do you test stock sync in the demo?

The test that reveals most about a tool is to keep a product with a single unit left on sale in two channels at once. During busy sales periods, a product that sells out on one marketplace can stay on sale in another channel for a few more minutes, and an order that arrives in that gap has to be cancelled. Cancellations of this kind can count against your seller performance. On eBay, for example, an order the seller cancels because the item is out of stock counts as a transaction defect under its seller performance standards.

Ask for these steps in the demo, ideally with a trial account connected to your own store:

1. List a product with a stock of 1 on one marketplace and on your own website or a second marketplace.
2. Place an order in one of the channels and note the time.
3. Watch for the moment the stock reaches zero in the other channel.

The gap between the two is the tool's real sync speed. This test shows what the vendor means by "real time". Some tools receive orders through a notification sent by the marketplace; others query the marketplace at set intervals. Ask which method is used, how many minutes the interval is and whether it changes with the plan you buy.

Add two questions to this test. What happens if orders arrive from two channels in the same minute? Can you set a safety stock? Showing a product as zero on the marketplaces once stock falls below three units, for example, closes most of the risk within the sync interval.

What should you check in variant and category mapping?

The product structure on your own site rarely matches the structure a marketplace expects. A colour defined as "Navy" on your site may have to be selected under a different value in the marketplace's colour list. Size charts differ by category. Each marketplace has its own category tree, and marketplaces make certain attributes mandatory by category; a product missing one of them may be rejected or may never go live.

Bring the most complex product in your catalogue to the demo: the one with the most variants, the one that could fit two categories. Ask the vendor to map it in front of you and watch for the following:

• Once size and colour values are mapped, are they remembered for the next products?
• Are the marketplace's mandatory fields marked separately on the tool's screen?
• When a field is missing, does the tool show clearly why the product was rejected?
• Can bulk mapping be saved as a rule? Once "Women > Dresses" has been mapped, a new product added to that category should go to the right place by itself.
• What happens to existing mappings when the marketplace updates its category tree?

As the catalogue grows, mapping becomes the most labour-intensive part of the integration. If mapping cannot be saved as a rule, the same work is repeated for every new product.

How do returns, cancellations and invoices flow?

The stock and order demo usually runs smoothly. The difference between tools tends to show in returns and cancellations, when an order comes back.

If stock rises automatically as soon as a return is approved, a faulty or opened product can go back on sale without being checked. In a properly configured flow, the product reaches the warehouse, is inspected and returns to stock after approval. Ask whether the tool offers a separate approval step for returns. For an order cancelled before dispatch, stock should come back straight away.

On invoices, the first question is who issues the invoice for a marketplace order: the tool itself, your accounting software or a separate invoicing service? Whichever issues it, matching the invoice to the marketplace order and getting it to the customer belong to the same flow, so see that step in the demo as well.

For the accounting or ERP connection, look at how sales are transferred. Is each order posted as a separate customer record and stock movement, or are orders sent in bulk at the end of the day? How do marketplace commission and shipping deductions appear in the accounts? These questions decide how much manual correction your accountant will make at month end.

For this section, run one order from start to finish in the demo. The order arrives, the invoice is issued, the shipping label is printed, and then the product is returned. At each step, count how many screens you switch between and how many times you enter information by hand.

Where should the master stock record live?

In a sound integration, one system is treated as the source of correct stock and the others read from it. Make this decision before choosing a tool, because it largely determines whether a tool suits you.

If you use an ERP and warehouse movements such as goods receipt, stocktakes and production are recorded there, the ERP is the master. The tool takes stock from the ERP and reports sales back to it. The first question is then whether the tool has a ready connection to your ERP.

If you have no ERP and most of your sales come from marketplaces, the tool can be the master. You record stock intake and stocktake corrections in the tool.

If your own online store is at the centre of your sales, product content and stock can be held on the site, and the tool reads from it and distributes to the marketplaces. Here the deciding factor is which information your store platform can share with the tool.

The most common problem is two systems both acting as the master. A correction entered in the ERP after a stocktake is overwritten with the old value at the tool's next sync. Ask in the demo: "Where do I enter a stock correction after a stocktake?" The answer should be one place.

When is an off-the-shelf tool no longer enough?

For a store that sells from a single warehouse, has a simple variant structure and uses no ERP, a well-configured off-the-shelf tool is usually sufficient. Custom development in that case is a cost with no return.

If one of the following applies to you, you are approaching the limit of an off-the-shelf tool:

• Stock across several warehouses or shops. Rules such as which channel sells from which warehouse, or whether to switch to another warehouse when one runs out, are not always part of a tool's standard settings.
• B2B pricing. Separate trade and retail prices, discounts per account or price breaks by quantity fall outside the standard settings of most marketplace integration tools.
• Bundles. When a set of three products sells, three separate stock levels have to fall. Some tools support bundles; if bundle contents change often or the same product appears in several bundles, the limit shows quickly.
• Custom ERP fields. Fields added to your ERP over time, such as lot, shelf location or production batch, are usually missing from the tool's standard connection.

In these cases the work often runs on spreadsheet exports and manual corrections at the end of the day. These in-between steps look small at first and turn into a daily workload as order volume rises. In such a setup it is sounder to build the connection between your ERP and the marketplaces around your own business rules. The part the off-the-shelf tool does well can stay, and custom software takes on only the rules the tool does not cover. Our ecommerce development page sets out when a standard platform is the right choice and when a custom build, including two-way sync with an ERP, makes sense.

What should you ask before signing the contract?

In the demo you see what the tool does today. What happens when your sales grow, when a marketplace changes its rules or when you decide to leave the tool is written in the contract. Get these answers in writing before you sign:

• Data export. If you leave, in what format can you take your product records, category and variant mappings and order history? Mappings take months of work; if you are given only a product list, that work stays in the tool.
• API limits. Marketplaces limit the number of requests made through their connection. As an example from the Turkish market, Trendyol has applied these limits on its product services since 14 September 2026 per service group, scaled to the seller's listing tier. Product create, update and delete requests within the same minute share one limit, while price and stock updates sit in a separate group and are also capped per barcode (Trendyol service limits). Ask how the tool manages such limits and how long a bulk price update takes to reach every channel across the whole catalogue.
• The tool's own API. Can your website or ERP connect to the tool, and what limits apply to that connection?
• Price change terms. Does the licence fee rise with the number of orders, products or channels? What happens if you exceed your plan's limit during a sales peak? Under what conditions can the price change at annual renewal?
• Marketplace changes. When a marketplace updates its connection rules or category structure, who makes the adjustment, and how are your sales affected in the meantime?

Tools that look alike in feature lists give different answers to these questions. Compare what you were shown in the demo with what the contract says, point by point, and put anything you saw in the demo but cannot find in the contract in writing before you sign.