Akakçe Integration

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:

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.

Feedance maps your existing product catalog straight onto Akakçe's field names, so you're not hand-building an XML template from scratch.

1. Add your feed. Connect your store or upload your product data in the Feedance Dashboard.
2. Map to Akakçe's fields. Feedance maps your catalog's title, URL, image, price, shipping cost, brand and category onto Akakçe's 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.
3. Export the feed URL. Feedance generates the XML at a stable URL and keeps it current as your prices and stock change — you give that URL to Akakçe once, and Feedance keeps what's behind it accurate for every future pull.

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.

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.