Asking the right questions before choosing a marketplace integrator is far cheaper than paying for the wrong choice. The 15 questions below cover channels, product matching, migration, daily operations, security, and cost. Under each one you will find why it matters and what a good answer sounds like. Take this list to the sales call and get answers in writing.
Channel coverage and connectivity
1. Does it connect to every marketplace I sell on today and plan to enter next year?
Why it matters: Integration is set up once and used for years. If you sell on Amazon and eBay now but plan to test Etsy, Walmart, or a regional marketplace like Trendyol or noon, a platform without those channels forces you into a second tool within a year. A good answer shows you the channel list and gives dates for anything labelled "coming soon". You can review the current list here.
2. Is the connection built on the marketplace's own API?
Why it matters: Tools that rely on indirect methods break whenever the marketplace changes its interface. An API-based connection is more stable and safer from an authorization standpoint. One-click authorization for channels like Etsy and eBay is a good sign; you should not be copying API keys around by hand.
3. If a channel goes quiet, who notices, and how fast?
Why it matters: Two hours without orders from one channel is sometimes normal and sometimes a broken connection. The system should tell you which. Ask how often channels are polled and where the alert lands (panel, email, phone notification). Bulutegra checks every channel continuously; a silent channel raises an alert and pushes a notification to your phone.
Products and matching
4. What key are my products matched on: SKU, barcode, or both?
Why it matters: Matching is the foundation of the whole integration. Systems that match on product title alone will update stock on the wrong item. Using SKU and barcode together keeps variants (color and size) aligned. See product matching with SKU and barcode for details.
5. Does it read my catalog source directly?
Why it matters: You do not want to re-enter products by hand. If you run Shopify, WooCommerce, or a Turkish platform such as ikas, Ticimax, T-Soft, or İdeasoft, you need a direct connection; if you work from an XML feed, you need feed import. A single catalog source means every channel receives the same content.
6. Can one tool manage a product on one channel while another tool manages it elsewhere?
Why it matters: During migrations this is unavoidable. Without a product-by-channel ownership flag that says "who manages this channel", two tools overwrite each other and stock shows two different values within the same hour.
Migration and testing
7. Can I watch the system in read-only mode before going live?
Why it matters: The biggest risk is in week one: wrong stock, wrong prices. Shadow mode means the system reads for one to two weeks without writing anything; once the numbers reconcile, write access is switched on channel by channel. If an integrator does not offer this step, ask why. Details are in testing integration with shadow mode.
8. How many steps does setup take, how many days, and what is expected of me at each step?
Why it matters: "Set up in a day" usually excludes matching and testing. Ask for a step-by-step plan with durations and responsibilities. Bulutegra's setup has four steps: Connect, Match, Observe, Hand over; each has a stated duration. The steps are described in the four-step setup guide.
9. What happens to open orders and returns when I switch from my current system?
Why it matters: On migration day there are orders not yet shipped and returns still in progress. Where those close must be agreed up front. A good answer is a date-based cut-off and a short period where both systems run side by side.
Daily operations
10. What data is written to my ERP, and when?
Why it matters: If accounting and fulfilment live in your ERP, each order must arrive automatically with customer, line items, carrier, and payment details. If you run Nebim V3, Logo, Mikro, or SAP, ask for a sample flow with your own ERP, and make it clear that invoicing and shipping must keep running in your existing setup.
11. Does the system reconcile payouts and commissions, or do I?
Why it matters: Missing payouts, returns where commission was never refunded, and orders that net negative are the hardest items to catch by hand. Can the system list them and hold a status and a note on each? More in payout and commission reconciliation.
12. Can I manage stock and prices in bulk during sales events?
Why it matters: During a campaign, hundreds of prices and stock levels change within hours. Without a price matrix (channel × list/sale/floor price), a campaign calculator, and low-stock alerts, the work falls back into spreadsheets and midnight manual edits.
Security, support, and cost
13. Are there user roles and two-factor authentication?
Why it matters: Warehouse staff should not be able to change prices, and accounting should not be able to delete content. Without roles such as Admin / Content / Warehouse / Accounting and 2FA, everyone shares one password; that is the most common security hole. See security, 2FA, and roles.
14. When something breaks, whom do I contact, how, and how fast do I hear back?
Why it matters: Support that goes silent on campaign night is the most expensive kind. Ask about the support channel, hours, and whether there is a system health screen that shows whether the problem is on your side, the integrator's, or the marketplace's before you open a ticket.
15. What is the total cost: monthly fee, setup, per-channel add-ons, per-order fees?
Why it matters: A low monthly fee combined with per-order charges gets expensive as you grow. Ask for pricing in writing, with plan names and the number of channels included. For a payback calculation see integration cost and return; current plans are on the pricing page.
Checklist before the call
- Write down your current and planned channels.
- Note your catalog source and your ERP.
- Have your monthly order and SKU counts ready.
- Ask for shadow mode and channel-by-channel handover.
- Get answers in writing; ask for dates on anything "coming soon".
- Ask them to match a few of your own products during the demo.
Short rule: a feature that cannot be shown does not exist. Do not trust anything you did not see on the demo screen.
How this works with Bulutegra
Bulutegra answers most of these 15 questions as product features: 24+ channels in one Integration Panel, SKU and barcode matching, a one- to two-week shadow mode, channel-by-channel handover, automatic order write-back to your ERP, role-based access, and two-factor authentication. The software was born inside the founding company's own multichannel retail operation, so the questions come from the same place the answers do. Request a demo and see it running against your own channels.
Frequently asked questions
What does a marketplace integrator actually do?
It sits between your marketplaces, your web store, and your ERP. It pulls orders into one place, keeps stock and prices identical across channels, and tracks returns and payouts so you never have to log in to each marketplace's seller panel separately.
How long does marketplace integration take to set up?
Connecting channels usually takes half a day and product matching one to three days. After that, expect a one- to two-week read-only observation period before the system is allowed to write. A realistic plan is close to three weeks; a "one-day setup" claim usually skips matching and testing.
Is switching integrators risky?
Not if it is planned. You agree on a cut-off date for open orders and returns, run the new system in read-only mode for a while, and hand over write access channel by channel. The real effort is redoing product matching, not the switch itself.
