Getting Your Product Feed Accepted on Akakçe, Cimri, N11 and ÇiçekSepeti

If you sell into Turkey, your feed tooling was almost certainly built for Google Merchant Center and Meta first. That is a problem the moment you try to list on Akakçe, Cimri, N11 or ÇiçekSepeti: none of the major multi-channel feed platforms (DataFeedWatch, Channable, Productsup, Feedonomics or Confect among them) ship a native template for any of these four channels. N11 alone generates at least 13 distinct product-rejection reasons across its integration error set, from a GTIN that "does not belong to this category" to images over 5,000 pixels on a side. This guide is for anyone managing a feed for Turkey, in-house or at an agency, who needs to get products accepted on these four channels without reverse-engineering each one from scratch. By the end, you will know what each channel actually validates against, where the public documentation stops, and what to check before you submit.

Why the standard feed playbook breaks here

Google Shopping and Meta Catalog both publish a single, English-language, versioned attribute spec that every feed tool ingests the same way. Akakçe and Cimri are price-comparison engines, not marketplaces. They read a store's own XML or CSV feed rather than defining one shared schema, so "the spec" is really whatever your storefront platform's export plugin produces. N11 is a full marketplace with a catalog-matching model similar to Amazon's: you attach your offer to an existing catalog GTIN rather than freely describing your own product. ÇiçekSepeti is a vertical marketplace (flowers, gifts, and increasingly general retail) with same-day delivery windows that make stock-sync frequency a bigger failure point than attribute completeness. Treating all four like a single "Turkey channel" is the most common reason a feed that passes GMC validation still gets rejected here.

N11: catalog matching is the whole game

N11's public developer documentation exposes a category tree endpoint, GET https://api.n11.com/cdn/categories, that returns nested categories with an id, parentId, name and subCategories array; a category with subCategories: null is a leaf, and N11 requires you to submit products against that leaf-level category id, not a parent. Below the category tree, N11 runs a GTIN-first catalog match: if your product's barcode is not already registered against an N11 catalog entry, or is registered to a different seller, the listing is rejected rather than created fresh.

That error list comes from N11 integration partner AKINSOFT's own support documentation, which logs the exact strings its connector receives back from N11. Treat it as a field report from a live connector rather than N11's own published spec, since N11 keeps the authoritative version behind its developer portal.

Akakçe and Cimri: price-comparison feeds, not marketplace listings

Akakçe and Cimri don't run a checkout on most listings. They route the click to your own store and take a cost-per-click or, on Akakçe's managed "Kolay Sipariş" program, a commission near 3.9% of basket value on the orders they originate. Both accept a store's XML or CSV export directly; neither company publishes a versioned attribute dictionary the way GMC does. In practice, Turkish e-commerce platforms' own XML export plugins converge on a similar minimum field set: product name, price, stock status, category, product URL, image URL and, where available, a GTIN or MPN. That convergence is a market norm observed across implementers, not a documented requirement from either platform, so verify it against your own store platform's export before assuming it's complete. Because there is no formal spec to validate against, the practical failure mode isn't a rejection message. It's silent under-listing: products missing a stable identifier don't get matched against the "same product, multiple sellers" price-comparison view, so they show up as an isolated listing instead of competing in the comparison table you're paying to appear in.

ÇiçekSepeti: the clock matters more than the schema

ÇiçekSepeti runs its own seller academy and a separate developer portal (ciceksepeti.dev) alongside the standard panel-based product upload flow described there. The attribute set itself is unremarkable next to N11 or GMC. What's different is the category mix: flowers, plants and same-day gifting are perishable or time-windowed inventory, so a feed that syncs stock once a day will oversell against delivery cutoffs in a way a durable-goods listing rarely does. If you run ÇiçekSepeti alongside slower-moving categories, treat it as the channel that decides your minimum acceptable sync interval, not the one you sync least often because it "only has a few hundred SKUs."

Side by side

A before/after row: fixing an N11 catalog mismatch

Say your GMC-oriented feed exports this row for a kettle:

title: "Electric Kettle 1.7L Black"; category: "Home & Kitchen"; gtin: (blank); image: 6200x4100px

Against N11 this fails twice: the category is a parent node, not a leaf, and the missing GTIN means there's no catalog entry to attach to. You'll get "Reselect Product Category and Properties" and then a GTIN-not-found response. The corrected row uses the actual N11 leaf category id from the categories endpoint, a real GTIN pulled from your product master (or proposed fresh through the panel if none exists), and an image resized under the 5,000px cap:

title: "Electric Kettle 1.7L Black"; category_id: 1003924 (leaf: "Su Isıtıcı"); gtin: 8690123456789; image: 2000x1333px

Nothing about that fix is exotic. It's the same discipline GMC enforces with its own category taxonomy and image minimums. The difference is that N11 will not tell you the category is wrong until the GTIN match already failed, so checking category depth first saves a round trip.

Pre-flight checklist

• Every N11-bound row maps to a leaf category id pulled from the live /cdn/categories tree, not a cached list from onboarding
• Every N11-bound row carries a GTIN that is either already matched in N11's catalog or has been proposed through the panel
• Titles are within N11's 2–65 character window and images are under 5,000px on the long edge
• Akakçe and Cimri rows include a stable identifier (GTIN or MPN) even though neither platform rejects its absence outright: it's the difference between competing in the comparison view and being invisible in it
• ÇiçekSepeti stock sync frequency is set by your fastest-moving delivery cutoff, not your average SKU velocity
• Campaign or sale pricing is reflected in the same field the channel actually reads — a mismatched "was" price is one of the more common causes of a listing looking cheaper on your site than on the channel

What this doesn't cover, and where it breaks down

If you sell on a single Turkish platform and nowhere else, a native plugin from your storefront (İdeaSoft, Ticimax, T-Soft and similar all ship built-in Akakçe/Cimri XML generators) will get you listed with less setup than any multi-channel feed tool, Feedance, DataFeedWatch and Channable included. You don't need rules, enrichment or cross-channel governance for one destination. This guide also doesn't cover Trendyol or Hepsiburada, which run their own, separately documented onboarding; and it doesn't cover Akakçe's or Cimri's full commercial terms, which change independently of their feed mechanics and are worth confirming directly with each platform before you commit engineering time. Where Akakçe and Cimri have no public attribute spec at all, treat the field list above as the common denominator observed across Turkish e-commerce platform connectors, not a guarantee. Verify against your own account's onboarding material before a first submission.

FAQ

Do Akakçe and Cimri require a GTIN?
Neither publishes a hard requirement, but products without one are less likely to be grouped correctly against competing sellers' listings for the same item, which is the entire value of appearing on a price-comparison site.

Why did my N11 listing get rejected after passing on GMC?
Almost always a category or GTIN catalog-match issue. N11's category-matched listings work differently from GMC's free-text category field; see the error table above.

Does N11 have a public API I can build against directly?
Yes, at developer.n11.com, including a category tree endpoint and RestAPI product upload; older documentation under magazadestek.n11.com now redirects there.

How often do I need to sync stock to ÇiçekSepeti?
Frequently enough to clear your tightest same-day delivery cutoff. There's no published minimum; the constraint comes from the product category, not the platform's technical limits.

Is ÇiçekSepeti only for flowers?
No, it has expanded into gifts and general retail categories, but its delivery-window model still applies across categories listed on it.

Can a single feed file serve N11, Akakçe and Cimri at once?
Only if it's built with each channel's mapping rules layered on top. N11 needs category ids and GTIN matching that Akakçe and Cimri don't enforce, so a single flat export tends to under-serve N11 specifically.

What image size does N11 actually accept?
Up to 5,000 pixels on a side, per N11 integration partner documentation; there's no published minimum, but very small images tend to fail category-specific image-quality checks downstream.

Do these four channels support custom_label-style segmentation like Google Shopping?
No, segmentation and bid logic are a Performance Max/Google concept. These channels work off flat category and price-comparison logic, not campaign-side labels.

Feedance connects to Akakçe, Cimri and 200+ other advertising and marketplace channels from one managed feed; if you want a second opinion on where your own feed would fail before you submit it, run it through the free product feed audit tool.