ikas vs Ticimax vs T-Soft vs İdeaSoft: Whose Native Feed Is Actually Ready for Google and Meta

Google Merchant Center will start enforcing a minimum 500x500 pixel image requirement on January 31, 2027, and it already rejects listings the moment a variant's item_group_id or gtin value is missing or malformed. None of that is new. What is easy to get wrong is assuming your Turkish e-commerce platform already handles it for you. We compared how ikas, Ticimax, T-Soft and İdeaSoft generate product feeds natively, using each vendor's own documentation, and found real gaps between "there is an XML link" and "Google and Meta will accept what's in it." This is for merchants and agencies on one of these four platforms deciding whether their native export is enough, or whether they need a feed layer on top of it.

What "feed-ready out of the box" actually means

A platform's product feed isn't ready for Google or Meta just because it produces a file. It has to satisfy attribute-level rules that neither ad platform will bend on. The table below is the baseline we graded each platform against, sourced directly from Google's product data specification and Meta's catalog field reference.

How each platform's native export actually behaves

ikas

ikas ships a direct Google Merchant Center integration: you copy a catalog link from the ikas panel into Merchant Center's data source settings, and according to ikas's own support documentation, "changes you make to products in your ikas panel will automatically reflect" in the feed. Barcodes are sent as GTIN by default, and ikas gives you a toggle to send them as MPN instead if your barcode formats don't meet Google's GTIN standard, an honest and useful admission that not every merchant's barcode is a real GTIN. What the documentation does not describe is a native Meta catalog integration, or how item_group_id is assigned across size and color variants, so you're relying on ikas's product-variant model translating cleanly, unverified.

Ticimax

Ticimax's own support documentation routes Google Shopping data through fields it calls "Adwords alanları" on each product's Marketing tab, filled in manually per product or in bulk through an Excel export/import cycle. That is a materially different model from ikas: attribute mapping is not automatic, it is data entry you own. Shipping data in the XML output is also opt-in per feed, toggled through a dedicated shipping configuration rather than inherited from your live storefront settings, which is a common source of price-mismatch rejections when the toggle and the storefront drift apart.

T-Soft

T-Soft generates feeds from fixed, predictable URLs, for example siteadresiniz.com/xml/googleshopping.com.php for Google and a separate facebookmagaza.com.php endpoint for Meta, according to T-Soft integration documentation from an authorized e-commerce consultant (T-Soft's own help center returned a 404 on the specific article at the time of writing, so verify the current path in your panel before relying on it). Product inclusion is controlled through a reseller "member group" mechanism: you assign categories or brands visibility to a group named for the channel, and only visible products appear in that channel's XML. That's a working access-control model, but it is not the same thing as attribute mapping, and neither the endpoint documentation nor the consultant writeup describes automatic GTIN, MPN, or item_group_id population.

İdeaSoft

İdeaSoft's export, reached through Entegrasyonlar → Idea Output Çıktı Sistemi in the admin panel, is the most attribute-aware of the four on paper. Per İdeaSoft's own help documentation, the XML output includes brand, GTIN/barcode, and MPN "when available," alongside the standard name, description, price, stock and image fields. It also carries the most explicit warning of any platform we checked: if your barcodes are not internationally valid GTINs, you must manually disable the GTIN field, because sending an invalid one causes product rejection rather than a graceful fallback. Variant correctness for color, size and product grouping is flagged as the merchant's responsibility, not automated.

The comparison

What a real gap looks like in a feed row

Here's the pattern that shows up most often once a merchant on any of these four platforms actually submits to both channels. A product with three sizes is exported as three separate rows, correctly priced and in stock, but the underlying platform did not assign a shared group identifier consistently:

row 1: id=SKU-TSHIRT-S, title=Cotton T-Shirt, item_group_id=(blank)
row 2: id=SKU-TSHIRT-M, title=Cotton T-Shirt, item_group_id=(blank)
row 3: id=SKU-TSHIRT-L, title=Cotton T-Shirt, item_group_id=TSHIRT-GROUP-04

Google and Meta both read this as three unrelated products, not one item with three variants, because Meta's own variant documentation is explicit that "the name of the product and the item_group_id fields match" across every row in the group. The same blank-attribute pattern is what drives most of the Meta Commerce Manager catalog disapprovals we've documented separately. The fix is not a platform setting, it is a pre-submission validation pass that confirms every variant row carries the same, non-empty group value before the feed goes anywhere near an ad account.

Where this comparison breaks down

This is a comparison of documented native export behavior, not a hands-on benchmark against live test accounts on all four platforms, so treat specific claims about any one platform as a starting point for your own panel check, not a final verdict. Platform vendors update their integrations regularly; T-Soft's own help center had already moved or removed the specific article we'd have preferred to cite, which is itself a sign these docs shift. None of the four platforms compared here are evaluated on checkout, theme, logistics or their app ecosystems, only on feed export, because that is the only axis this article is about.

If your catalog sits on a global platform instead of one of these four, the comparison doesn't transfer directly: DataFeedWatch and Channable both maintain broader pre-built connector libraries across dozens of non-Turkish platforms, and if your business runs on one of those rather than ikas, Ticimax, T-Soft or İdeaSoft, that connector breadth is a genuine reason to look at them first. For a single small store with a simple, non-variant catalog, a platform's native export plus careful manual QA may honestly be enough, and buying a feed tool for ten SKUs is not a good use of budget.

A short pre-submission checklist

• Every variant row shares an identical, non-empty item_group_id with every other size/color combination of the same product
• GTIN values are real, scannable barcodes, not internal SKUs relabeled as GTIN — if in doubt, switch to the MPN + brand pattern
• Product images meet 500x500px minimum now, not after Google's January 2027 enforcement date
• Price and availability in the feed match what the storefront shows at the same moment, not what it showed when the export was last configured
• A second, correctly shaped file exists for Meta if your platform's native export was built Google-first

Frequently asked questions

Does ikas support Meta catalog exports natively, the same way it does Google Merchant Center?

ikas's own support documentation describes the Google Merchant Center catalog-link integration in detail but does not document an equivalent native Meta catalog connection. Check your current panel version before assuming feature parity.

Why does Ticimax ask me to fill in Adwords fields manually instead of mapping them automatically?

Ticimax's product data model treats Google Shopping attributes as editable marketing fields on each product record rather than values derived automatically from your catalog structure, which is why bulk Excel editing is the documented workaround for updating many products at once.

What happens if T-Soft's XML output includes a product without a valid GTIN?

Neither the available T-Soft documentation nor the consultant writeup we cited specifies automatic GTIN handling, so an invalid or missing identifier will surface as a standard Google Merchant Center rejection rather than being caught before submission.

Why does İdeaSoft warn me to manually disable the GTIN field?

Because İdeaSoft can include barcode data as GTIN automatically, and if that barcode is not internationally valid, Google rejects the product rather than accepting it with a warning, so İdeaSoft's documentation puts the responsibility on the merchant to catch invalid barcodes before they reach the feed.

Is item_group_id the same thing as a SKU?

No. A SKU (mapped to id) must be unique per product variant row. item_group_id is a separate, shared value that groups those variant rows together as one product with options, and per Google's documentation each attribute combination should occur only once within a group.

Can I just submit the same XML feed to both Google and Meta?

Not reliably. Google accepts TSV, XML or the Content API; Meta accepts CSV, TSV, RSS XML, ATOM XML or Google Sheets, and required fields differ slightly between the two (Meta requires condition and brand on every row, for example, where Google's requirement for brand is conditional). A feed built to satisfy one channel's schema will often fail the other's validation even when the underlying product data is correct.

Does switching platforms fix these feed gaps?

Not by itself. The gap is in attribute mapping and pre-submission validation, not in the platform's core commerce functionality, so migrating to a different Turkish e-commerce platform without addressing GTIN, item_group_id and image compliance directly just relocates the same problem.

How often should I re-check a native export against current Google and Meta requirements?

At minimum whenever either channel announces a policy change, such as Google's January 2027 image enforcement date, and whenever the e-commerce platform ships a panel update that touches product or integration settings, since none of the four platforms compared here version their export documentation publicly enough to notify merchants automatically.

Feedance connects to feeds from any of these four platforms, enriches the attributes each channel actually requires, and publishes to more than 200 advertising and marketplace channels — including Akakçe, Cimri, N11 and ÇiçekSepeti alongside Google and Meta — without you maintaining separate Google-shaped and Meta-shaped exports by hand. If you want to see exactly which attributes your current feed is missing before Google or Meta finds them for you, run it through the free product feed audit tool.