A catalog with a performance signal on every product
Akakçe reads your products from the feed. Feedance sends a complete, valid feed plus the signals Akakçe does not have on its own.
AkakçeChannel · Comparison shoppingFeedance builds your Akakçe feed and adds product-level labels for score, 4T segment, price position and broken sizes, so every product carries its own performance signal.
Akakçe reads your products from the feed. Feedance sends a complete, valid feed plus the signals Akakçe does not have on its own.
Akakçe is Turkey's largest price comparison engine, launched in 2000. Rather than selling products directly, it aggregates offers from thousands of Turkish retailers so shoppers can compare price, stock and seller reputation for the same product side by side before clicking through to buy. For merchants, Akakçe works on a cost-per-click model: your listing is free to appear, but you pay only when a shopper clicks through to your store, which makes feed data quality (accurate pricing, matching titles, live stock) directly tied to how much of that spend converts into a sale rather than a bounce.
Akakçe is one of the highest-intent traffic sources in Turkish e-commerce: shoppers arrive already comparing prices for a specific product, not browsing casually, so a click is close to a purchase decision. That intent only converts if what a shopper sees on Akakçe matches what they find on your site. A price shown as available that's actually out of stock, or a price that differs from your live checkout price, gets the listing suppressed or the click wasted. Connecting your feed through Feedance keeps price and stock synced automatically as they change on your store, instead of relying on a periodic manual export that's already stale by the time Akakçe re-crawls it.
Akakçe charges on a cost-per-click (CPC) basis: appearing in Akakçe's price comparison results is free, and you only pay when a shopper clicks through from Akakçe to your product page. Because you're billed per click regardless of whether it converts, feed accuracy has a direct cost dimension here that it doesn't have on channels billed per impression — a click sent to a product that's actually out of stock, or a price that doesn't match your checkout, is money spent on a shopper you were about to lose anyway.
Akakçe pulls your product data itself — you don't push anything to them. You publish a single XML file at a URL you control, and Akakçe's own servers request that URL at the intervals they determine; every product you want listed, and every price, stock or listing change, has to be reflected in that same file, since publishing and un-publishing products only happens through what's currently in the feed.
The file must be UTF-8 encoded XML with a <products> root element containing one <product> element per item. Akakçe documents exactly which IP addresses will be requesting your feed URL — if your server or firewall restricts access by IP, these need to be allowed, or the feed will simply never be fetched:
| Requesting IP |
|---|
| 85.105.26.146 |
| 178.251.45.163 |
| 178.251.45.210 |
| 185.67.125.150 |
No file-size limit, alternate delivery method (FTP/API) or compression format is documented beyond this pull-by-URL model, so the safest approach is serving plain, uncompressed XML at whatever URL you provide unless Akakçe's team has told you otherwise directly.
Akakçe's XML schema has 9 required fields and 8 optional ones. The table below follows Akakçe's own field names exactly, so they map one-to-one onto the tags in your feed.
| Field | Required | Format | Example | Notes |
|---|---|---|---|---|
sku | Yes | string | 404718 | Your own unique product code, numeric or alphanumeric |
name | Yes | string, max 200 chars | Braun Series 1 150s-1 Şarjlı Tıraş Makinesi | |
url | Yes | string, max 255 chars | https://www.site.com/product_404718.html | |
imgUrl | Yes | string, max 255 chars, min 250px | https://img.site.com/404718.jpg | |
price | Yes | decimal, XXXX.XX | 109.69 | VAT-included, single-payment price in TL |
shipPrice | Yes | decimal, XX.XX | 7.90 (0.00 if free) | |
dayOfDelivery | Yes | integer | 3 (0 = same-day) | Business days to ship |
expressDeliveryTime | Only if same-day | integer, hour only, 24h format | 16 | Required whenever dayOfDelivery is 0 |
productBrand | Yes | string, max 60 chars | Braun | |
productCategory | Yes | string | Elektronik > Telefon > Cep Telefonu | Full breadcrumb (">" separated) or category name |
additionalimages | No | nested <imgUrl> tags | up to 5 | |
description | No | string, HTML allowed | wrapped in CDATA | Must be inside <![CDATA[...]]> |
distributor | No | boolean | true / false / empty | true = distributor-guaranteed, false = parallel import, empty = unknown |
quantity | No | integer | 12 (0 = out of stock) | |
barcode | No | string | 4210201616641 | EAN-13 or UPC, manufacturer-issued only |
localDelivery | No | comma-separated string | 34,6,35 | City plate codes, no leading zero — only for your own-fleet regional delivery |
campaignCode | No | string, max 16 chars | 3A2O | Max 1 per product |
Feedance maps your existing product catalog straight onto Akakçe's field names, so you're not hand-building an XML template from scratch.
name, url, imgUrl, price, shipPrice, productBrand and productCategory tags. Two mappings need attention specifically for Akakçe: productCategory should carry your full category breadcrumb ("Elektronik > Telefon > Cep Telefonu"), not just the leaf name, and any HTML in description is automatically wrapped in <![CDATA[...]]> so the feed doesn't break on Akakçe's parser.Akakçe's own servers decide when to re-fetch your feed — the specification doesn't commit to a fixed interval, which means you don't control how quickly a change reaches Akakçe, only whether it's already true at your URL by the time they next pull it. Because of that, the file you publish should reflect your live price, shipPrice and quantity continuously, not a batch export refreshed once a day: a price mismatch between your feed and what a shopper is actually charged at checkout is exactly the kind of inconsistency that puts a listing at risk. Setting quantity to 0 the moment something sells out matters more here than on channels you push updates to yourself, since Akakçe has no other signal that stock changed until it re-reads your file.
| Error | Likely cause | Fix |
|---|---|---|
| Product not showing up | A required field is missing or empty for that product | Confirm sku, name, url, imgUrl, price, shipPrice, dayOfDelivery, productBrand and productCategory are populated for every <product>, not just a sample |
| Listing flagged over price | price not sent in XXXX.XX format, or excludes VAT | Send the VAT-included, single-payment TL price exactly as charged at checkout, formatted as XXXX.XX |
| Same-day delivery not showing | dayOfDelivery is 0 but expressDeliveryTime is empty | expressDeliveryTime is required whenever dayOfDelivery is 0 — send the cutoff hour in 24h format |
| Description renders broken or feed fails to parse | HTML in description sent without CDATA wrapping | Wrap all description content in <![CDATA[...]]>, especially if it contains HTML tags |
| Image rejected or listing looks broken | imgUrl below the 250px minimum, or the URL exceeds 255 characters | Serve images at 250px or larger and keep the URL within 255 characters |
| Product lands in the wrong category | productCategory sent as a single leaf word instead of the full path | Send the complete breadcrumb separated by ">" (e.g. "Elektronik > Telefon > Cep Telefonu") |
| Feed never gets picked up at all | Server or firewall blocking Akakçe's request IPs | Allow 85.105.26.146, 178.251.45.163, 178.251.45.210 and 185.67.125.150 to reach your feed URL |
| Regional delivery info ignored | localDelivery sent for a product not actually delivered by your own fleet, or plate codes with a leading zero | Only populate localDelivery for genuine own-fleet regional delivery, plate codes comma-separated with no leading zero |
Send the full category breadcrumb, not just the leaf name. Akakçe's own documented example is "Elektronik > Telefon > Cep Telefonu" — the full path gives Akakçe more context to place your product correctly than "Cep Telefonu" alone.
Use quantity, don't just remove the product. Setting quantity to 0 is the documented way to signal out-of-stock; pulling the product from the feed entirely means Akakçe has no record to reactivate later.
Keep price and shipPrice honest and current. Since Akakçe pulls on its own schedule rather than reacting to a push, any gap between your feed price and what a shopper is actually charged is a mismatch Akakçe will eventually catch.
Provide a manufacturer barcode when you have one. barcode is optional, but a real EAN-13 or UPC gives Akakçe a stronger signal to match your listing to the right product rather than creating a duplicate.
Add extra images through additionalimages. Up to five extra <imgUrl> entries are supported — for categories shoppers compare visually, that's a trust signal a single hero image doesn't give.
Wrap CDATA properly and only where needed. If you send HTML in description, it must be inside <![CDATA[...]]> — malformed CDATA is a common way a feed fails to parse at all.
Does Akakçe support formats other than XML?
No — Akakçe's documented feed system is XML only, a single file with a <products> root and one <product> element per item.
How does Akakçe fetch my feed?
You publish it at a URL, and Akakçe's own servers request that URL at intervals they determine — you don't push updates to them. Changes only take effect the next time Akakçe re-reads your file.
What should I send when a product is out of stock?
Send quantity as 0. Removing the product entirely instead means Akakçe loses its record of that listing.
Is stock quantity required?
No, quantity is optional — but if you track it, 0 is how Akakçe expects out-of-stock to be signalled.
What happens if my feed price doesn't match my checkout price?
Akakçe's documentation states it reserves the right not to publish products from the feed at all — a price mismatch is exactly the kind of inconsistency that puts a listing at risk.
Do I need to provide a barcode?
No, barcode is optional, and only manufacturer-issued EAN-13 or UPC codes should be sent, never a self-generated one.
Does Akakçe support same-day delivery information?
Yes — set dayOfDelivery to 0 for same-day shipping, and you must also send expressDeliveryTime with the cutoff hour in 24-hour format.
Akakçe is Turkey's largest price comparison engine, launched in 2000. It does not sell products itself. Instead, it collects offers from thousands of Turkish online retailers so shoppers can compare price, stock and seller reputation for the same product side by side, then click through to buy on the retailer's own site.
Shoppers use Akakçe through its website and mobile apps, mostly when they already know what they want and are looking for the best offer. That makes its traffic high-intent: a click is often close to a purchase decision.
Merchants list products by publishing a single XML product feed at a URL. Akakçe's servers fetch that file on their own schedule, and every product, price and stock change has to be reflected in it. Appearing in results is free, and merchants pay per click when a shopper visits their store.
Because every click costs money, feed accuracy matters directly. A product shown as in stock that is sold out, or a price that differs from the checkout price, wastes paid clicks and can get listings suppressed, so keeping prices and stock in sync is essential on Akakçe.
Connect your feed and GA4. We show Product Score, 4T, Price War and Broken Size on your own catalog.