Marketplace Integration Setup in 4 Steps

Marketplace integration setup is completed in four steps: Connect (half a day), Match (one to three days), Observe (one to two weeks, the system only reads), and Hand over (write access channel by channel). The whole thing takes close to three weeks, and sales continue throughout. This guide explains what happens at each step, what is expected of you, and what to check before moving on. Bulutegra's setup follows exactly these four steps; the order was field-tested before it became the product.

Before you start

The cleanliness of your product data decides how long setup takes. Spend a day preparing the following:

• The list of marketplaces you sell on and the account owner for each.
• Your catalog source: Shopify, WooCommerce, an XML feed, or a Turkish platform such as ikas, Ticimax, T-Soft, or İdeasoft.
• If you use an ERP, its name (Nebim V3, Logo, Mikro, SAP) and the person responsible for it.
• Whether the SKU and barcode fields in your product list are filled.
• The person responsible for setup and their backup.
• The people who will use the panel as admin, content, warehouse, and accounting.

This fits on one page and cuts day one in half. If you have not chosen an integrator yet, start with 15 questions to ask before choosing an integrator.

Step 1: Connect (half a day)

In this step marketplaces, the catalog source, and the ERP are connected to the panel. Nothing is written; connections are established and reading begins.

1. Authorize the API for each marketplace. Etsy and eBay offer one-click authorization; for others you obtain a key from the seller panel.
2. Connect the catalog source. Products, SKUs, and barcodes are read from here.
3. Set up the ERP connection. This defines how each order is written with customer, line items, carrier, and payment details; invoicing and shipping keep running in your existing setup.
4. Turn on channel monitoring. Polling continuously begins; a silent channel raises an alert.
5. Create users. Each person gets their own account, role, and two-factor authentication; details in security, 2FA, and roles.

Check before moving on: Are the latest orders from every channel visible in the panel? Does the product count match the catalog? Does the system health screen show every connection green?

Step 2: Match (one to three days)

Matching links your product to its listing on each marketplace. The keys are SKU and barcode; a product where both agree is a confirmed match. Detailed rules are in product matching with SKU and barcode.

1. Run automatic matching; confirmed matches fill the list.
2. Review single-key matches; fix the missing field on the channel side.
3. Link unmatched items manually.
4. Check variants; every color and size is its own row.
5. Resolve duplicate listings.
6. Set the ownership flag: for each product × channel, "who manages this channel?" must have one answer. Channels staying on the old system during migration are marked "external system".

Check before moving on: Is the unmatched count zero, or deliberately out of scope? Do source and channel stock agree on ten random products? Is the ownership flag correct for every channel?

One day or three? If product data is clean and barcodes are filled, one day; if many listings were created by hand on the channel, three.

Step 3: Observe (one to two weeks, shadow mode)

In this step the system runs on real data but writes to no channel. It compares the stock and price it computes with the actual values and lists the differences. This is shadow mode; details in testing integration with shadow mode.

1. Review differences daily for the first three days.
2. Find the cause of each: a matching error, a manual change on the channel, or a delay between source and ERP.
3. Fix matching errors; the gap should close immediately.
4. Validate order flow: every channel order appears in the panel with the same totals.
5. Get through a weekend; the weekend rhythm is different.
6. Switch to sampling in week two.

Check before moving on: Has the stock and price gap been zero for three days? Did every order appear in full? Was the channel monitoring alert tested, and did the notification reach a phone?

Rule: before the system writes on your behalf, it must show that it arrives at the same numbers you do. This step is never skipped and never shortened.

Step 4: Hand over (channel by channel)

When the numbers reconcile, write access is enabled, but one channel at a time, never all at once. If something goes wrong, only that channel is affected and rollback is easy.

1. Start with the lowest-volume channel.
2. Enable stock writing only; check differences for two days.
3. If there is no gap, enable price writing; check for two more days.
4. Update the ownership flag to "managed by Bulutegra" and turn off the old system's write access on that channel.
5. Move to the next channel. The highest-volume channel comes last.
6. Once every channel is handed over, retire the old system; the cut-off for open orders and returns should have been agreed at the start.

Check before moving on: Does each channel have exactly one managing system? Is the gap zero for two days after handover? Does the team know the rollback path (turn off write access)?

The first month and a summary checklist

Handover is not the end; the first month is when the panel settles into daily use.

• Set the thresholds for low-stock alerts and the days-of-stock report using what you saw in the observation period; see critical stock and days of stock.
• Fill in the price matrix (channel × list/sale/floor price); if you will use repricing, the floor price is mandatory.
• Check the payout and reconciliation page in the first payment cycle.
• Close the missing title, color, and category findings in the quality tab.
• Narrow or widen user roles based on actual use.
• Confirm that notifications reach the team through the mobile interface.

Setup checklist (summary)

• Preparation: channel list, catalog source, ERP, and responsible people ready.
• Connect: all connections green, orders and products visible in the panel, users created.
• Match: unmatched at zero, variants correct, ownership flag set.
• Observe: three days at zero difference, order flow validated, alert tested.
• Hand over: channel by channel, stock first then price, old system retired.
• First month: thresholds, price matrix, payouts, quality, roles reviewed.

How this works with Bulutegra

Bulutegra's setup follows these four steps: Connect, Match, Observe, Hand over. The duration of each step is stated up front and the exit check for each is visible in the Integration Panel. 24+ channels, the main catalog sources, and Nebim V3, Logo, Mikro, and SAP connections all go through the same process. The software was set up in this exact order inside the founding company's own multichannel retail operation, so the steps are field-tested. To see a setup plan for your own channels, request a demo; we explain why we follow this order on the Why Bulutegra? page.