Ticimax, İdeasoft and T-Soft Marketplace Integration
Use your Ticimax, İdeasoft or T-Soft store as the master catalog and sell on Trendyol, Amazon and 24+ channels from one stock pool. Setup and order flow.
If your online store runs on Ticimax, İdeasoft or T-Soft, three of the most widely used e-commerce platforms in Türkiye, you do not need a separate product catalog to sell on marketplaces. Your store becomes the master catalog source; the integration panel reads products from it, maps them to Trendyol, Hepsiburada, Amazon, N11 and other channels, collects orders on one screen and updates stock everywhere after every sale. Whatever your store says, the marketplaces repeat.
Three platforms, one principle
Ticimax, İdeasoft and T-Soft each have their own admin panel, variant logic and category tree. For marketplace integration, though, the same principle applies to all three: product master data stays in the store, and each marketplace listing is a reflection of it.
Sellers who break this principle end up managing both sides by hand. A price changes on the store and is forgotten on Trendyol. A new image is uploaded to Hepsiburada and the store keeps the old one. The result is a team that no longer knows which data is correct. Integration removes the duplication: the store is the source, the channels follow.
Bulutegra supports Ticimax, İdeasoft, T-Soft and XML feeds as master catalog sources alongside ikas. Whichever platform you use is connected, the product list is read, and the rest follows the same flow. For the basics, see what marketplace integration is.
What is read from the source
The integration panel takes the following from your store:
- Product identity: product code, SKU and barcode. All matching is done on these three.
- Variants: colour, size and model options, each with its own barcode.
- Stock: the sellable quantity, which forms the single stock pool.
- Prices: list and sale price. Channel-specific differences are handled in the panel's price matrix.
- Content: title, description, images, category and attribute fields.
The three platforms structure variants differently; on one, size is an attribute field, on another it is a separate variant row. The panel closes that gap during matching. The only thing you need to check is that every variant carries a single, correct barcode.
A variant with an empty barcode either fails to match or creates a duplicate listing. Barcode cleanup is the most valuable work you can do before setup.
Writing to the marketplace: categories and mandatory fields
A category called "Women > Dresses" on your store sits under a different tree on each marketplace, and that category has its own mandatory attributes: fabric, fit, length, pattern and so on. For a product to go live, those fields must contain the values the marketplace expects.
The panel asks you to make this mapping once per category. Every new product in that category then follows the same rule. Missing fields are listed in the quality tab, where missing colour, title or category findings can be fixed with one click. Product content and quality score covers this in depth.
Do not forget image rules. Marketplaces set image dimensions, background colour and image count limits; check the current rules in each marketplace's seller documentation. If your store images comply, they are transferred as they are.
Order flow and where the ERP fits
An order from a marketplace appears in the panel under its channel tab. You can search by date range, customer name or SKU and export to CSV. The moment the order lands, stock is deducted from the pool and every channel is updated. The overselling logic is explained in stock synchronisation and overselling.
Businesses running an ERP have one more step. The order is written automatically to Nebim V3, Logo, Mikro or SAP with the customer, line items, carrier and payment details. Invoicing and shipping continue in the business's own process. The integration does not replace your invoicing software; it delivers the order to the right place with the right data.
A frequent question here is whether stock should come from the store or the ERP. If warehouse management happens in the ERP, the ERP must be the stock source and the store stays a content source only. If the warehouse is managed outside the ERP, the store can own stock. This decision is made on day one of setup and written down.
Setup steps
Bulutegra setup follows the same four steps for Ticimax, İdeasoft and T-Soft:
- Connect: your store's API credentials and marketplace accounts are registered in the panel. About half a day.
- Match: products are matched by SKU and barcode to existing marketplace listings. One to three days; unmatched items are your call.
- Watch: shadow mode. For one to two weeks the system only reads, reporting stock and price differences without writing to any channel.
- Hand over: write access is enabled channel by channel. The lowest-risk channel first, then the rest.
Shadow mode proves its worth on a store that is already trading. A wrongly matched product with live writes on shows wrong stock on every channel; in shadow mode it is a single report line. See shadow mode integration testing.
The ownership flag comes into play at hand-over. For each product × channel, the setting "is the integration managing this channel or an external system?" is kept separately. A channel you are not ready to hand over is flagged as external; it is read, never written to.
Pre-migration checklist
Before setup, check the following in your store:
- Does every variant have a filled, unique barcode?
- Do product codes follow the same logic as the stock codes on your marketplaces?
- Is the category tree tidy enough to map onto marketplace categories?
- Are mandatory attribute fields (brand, colour, size, fabric) filled?
- Are inactive products actually inactive at the source, or merely hidden?
- Have you set a critical stock threshold and a per-channel price rule?
- Are user roles agreed? Admin, Content, Warehouse, Returns, Accounting and Reporting roles work with separate permissions.
Businesses that complete this list get a short shadow mode report and a fast hand-over. Those that skip it spend longer in the matching phase, because barcode and category problems only surface then.
How it works with Bulutegra
Bulutegra connects your Ticimax, İdeasoft or T-Soft store as the master catalog source and manages more than 24 marketplaces from one Integration Panel. Alongside Trendyol, Hepsiburada, Amazon, N11, Çiçeksepeti, Pazarama, PttAVM, Modanisa, Flo and İdefix, the global channels Amazon, eBay, Etsy, Walmart, Ozon, Temu, SHEIN and Jumia draw from the same stock pool. Orders are gathered in channel tabs, stock and prices update after every sale, channels are checked continuously and a silent channel raises an alert. If you have an ERP, orders are written to Nebim V3, Logo, Mikro or SAP automatically. The software grew out of the founding company's own multichannel retail operation, where this flow ran first.
To see how it connects to your platform, fill in the demo form or browse the Channels section.
Frequently asked questions
How does Ticimax marketplace integration work?
The integration panel reads products, variants, stock and prices from your Ticimax store. Products are matched to marketplace listings by SKU and barcode, stock flows from one pool to every channel, and marketplace orders are collected in the same panel. You keep editing products in Ticimax; the channels follow.
How do I push İdeasoft products to Trendyol?
İdeasoft is connected as the master catalog source and products are converted to Trendyol's format through category and mandatory attribute mapping. Items with a barcode and complete required fields are matched or listed; gaps appear in the quality tab and can be fixed with one click. Write access is enabled after shadow mode.
Can I use T-Soft together with an ERP?
Yes. T-Soft holds product master data while the ERP keeps order, customer and accounting records. A marketplace order is written to the ERP automatically with customer, line items, carrier and payment details; invoicing and shipping continue in your own process. Which system owns stock is decided during setup.


