ikas Marketplace Integration: One Catalog, Many Channels

ikas marketplace integration lets you keep managing products in your ikas store while selling the same items on Trendyol, Hepsiburada, Amazon, Etsy, eBay and other channels from a single stock pool. ikas becomes the master catalog source; the integration panel reads that catalog, maps it to each channel, collects orders and updates stock everywhere after every sale. You edit product data in one place, and the channels follow.

What a master catalog source means

The most common problem in multichannel selling is having five versions of the same product in five places. The title on Trendyol is different, the barcode on Amazon is missing, the price on your own store is out of date. After a few months nobody can say which version is correct.

A master catalog source ends that. Product name, description, images, variants, barcode and cost, in short the product master data, live in one system. If you run ikas, that system is ikas. Every other channel is fed from it and never writes back to it.

Bulutegra accepts ikas, Ticimax, T-Soft, İdeasoft and XML feeds as master catalog sources. When you pick ikas, the panel reads your ikas product list and you decide which product matches which listing on each channel. If you are new to the topic, start with what marketplace integration is.

The rule is simple: edit the product in ikas, not on the marketplace. A manual change made on the marketplace falls behind the source at the next sync.

What data flows from ikas to the marketplaces

Not every field travels to every channel in the same way. The general flow looks like this:

• Products and variants: colour, size and model variants in ikas are mapped to each marketplace's variant structure.
• Stock: the sellable quantity in ikas forms the single stock pool. A sale on one channel lowers the quantity on all the others.
• Prices: list, sale and floor prices can be set per channel. The ikas price is the base; channel rules are defined in the panel's price matrix.
• Images and descriptions: content from the source is adapted to each marketplace's character and image rules.

The barcode is the backbone of this flow. Marketplaces mostly identify a product by its barcode. A variant with an empty barcode in ikas either fails to match or is created as a brand new product. That is why the first day of setup is usually spent cleaning barcodes. See matching products by SKU and barcode for the details.

Every marketplace also has its own commission model; check the current agreement for actual rates. The channel × list/sale/floor price matrix exists to manage that difference. When the ikas price changes, the matrix rule is recalculated.

Where orders land

Marketplace orders are collected in the integration panel with one tab per channel. You can search Trendyol, Amazon and Etsy orders on the same screen by date range, customer name or SKU, and export the result as CSV.

The moment an order arrives, stock is reduced on every channel. This is the main defence against overselling. Selling the last unit of an item on two channels at once costs you a cancellation and marketplace rating points. The topic is covered in stock synchronisation and overselling.

If you run an ERP, the order is written to it automatically with the customer, line items, carrier and payment details. Invoicing and shipping then continue inside your own process. ikas and an ERP can work side by side: ikas owns the catalog, the ERP owns accounting and warehouse data.

Setup: connecting ikas in four steps

Bulutegra setup follows the same four steps for every source. For ikas the typical timing is:

1. Connect (half a day): your ikas store and the marketplaces you sell on are linked to the panel. Etsy and eBay use one-click authorisation; Turkish marketplaces need API credentials.
2. Match (1–3 days): ikas products are matched by SKU and barcode to existing listings on each marketplace. Unmatched items go to a separate list and you decide what to do with them.
3. Watch (1–2 weeks): shadow mode. The system reads every channel, reports stock and price differences, but writes nothing. Matching errors surface here, not in production.
4. Hand over (channel by channel): you decide where write access is switched on. One channel first, then the rest.

Shadow mode matters most when you migrate from a store that is already trading, which is exactly the ikas case. A single mismatched barcode with live writes enabled can zero the stock of hundreds of listings. In shadow mode the same mistake is one line in a report. Read more in shadow mode integration testing.

The ownership flag: who manages which channel

Some businesses want to keep managing one channel the old way for a while, for example Amazon listings maintained by hand by a separate team. In that case the integration must not write there.

That is what the product × channel ownership flag is for. For every product on every channel, the answer to "is the integration managing this channel or an external system?" is stored separately. Channels flagged as external are read and reported, never written to. This lets you migrate piece by piece: finish one channel, flip the flag, move to the next.

Checklist for ikas users

Before setup starts, check the following on the ikas side:

• Does every variant have a filled, unique barcode?
• Are SKU codes built with the same logic as your marketplace listings?
• Do category and brand fields match the values each marketplace makes mandatory?
• Do image sizes meet marketplace rules?
• Is a critical stock threshold defined? The critical stock alert and days-of-stock report in the panel work from it.
• Are pricing rules clear? On which channels will commission differences be reflected in the price?
• Who works with which role? Admin, Content, Warehouse, Returns, Accounting and Reporting roles are defined during setup.

Most of these items are tracked in the quality tab, which lists missing colour, title or category findings and fixes them with one click. The link between content and marketplace quality scores is explained in product content and quality score.

How it works with Bulutegra

Bulutegra takes your ikas store as the master catalog source and connects it to more than 24 marketplaces from one Integration Panel. In Türkiye that includes Trendyol, Hepsiburada, Amazon, N11, Çiçeksepeti, Pazarama, PttAVM, Modanisa, Flo and İdefix; globally Amazon, eBay, Etsy, Walmart, Ozon, Temu, SHEIN and Jumia draw from the same stock pool. Orders are collected in channel tabs, stock and prices update after every sale, channels are checked continuously, and a channel that goes quiet triggers a push notification on your phone. If you have an ERP, orders are written to Nebim V3, Logo, Mikro or SAP automatically. Setup starts within half a day and goes live channel by channel after shadow mode.

The software was born inside the founding company's own multichannel retail operation, so the ikas-to-marketplace flow was tested there before it was ever sold. See the full list under Channels, or use the demo form to see it running with your own ikas store.