Marketplace XML Integration 2026: Supplier Connection, Automated Product Feed & Stock-Price Sync Guide

The 2026 Turkish Marketplace XML Landscape at a Glance

The cards below summarize the eight platforms and supplier networks covered in this guide — keep them in view as you read each deep-dive section.

1. How Marketplace XML Integration Works in 2026

The Three-Layer Sync Architecture

Modern marketplace integration runs on a three-layer architecture: a supplier ingestion layer, a master catalog layer, and a per-marketplace push layer. Each layer has its own scheduling, deduplication and error handling.

• Layer 1 — Supplier Ingestion: pulls XML (or REST, or CSV) from the wholesaler / ERP. Schedule: 15 minutes. Output: rows normalized to a canonical schema.
• Layer 2 — Master Catalog (Local): the seller-owned source of truth. Applies markup rules, category mappings, and the MIN-stock dedup policy.
• Layer 3 — Marketplace Push (Targets): Trendyol REST, Hepsiburada Listing API, n11 SOAP/REST, Amazon SP-API, Çiçeksepeti REST, Pazarama REST. 15-minute cron + event-driven push.

Master → Local → Targets: The Critical Flow

The hardest bug class is "stock looked correct in the panel but was wrong on the marketplace." In almost every documented case the root cause was master → local desync, not local → marketplace. The June 2026 MIN-stock dedup fix was precisely this class of bug: the local layer was summing duplicates instead of taking the minimum.

Cron vs Event-Driven Push

The 2026 industry standard is both:

• Scheduled cron at 15 minutes — full catalog refresh, catches anything the event layer missed. Resilient to event-bus failures.
• Event-driven push on order events — every successful order triggers an immediate stock decrement to all other marketplaces. Average latency: under 30 seconds.

Sellers who run cron-only sync (daily, or even hourly) routinely oversell during flash sales. The 15-minute cron is the minimum acceptable schedule in 2026.

2. Trendyol — XML Integration for the Dominant Marketplace

Trendyol at a Glance

Trendyol is the gravitational center of Turkish e-commerce. Founded in 2010 in Istanbul and majority-acquired by Alibaba in 2018, it now serves 30M+ active customers, hosts 240K+ sellers, and reaches roughly 55–60% of Turkish internet users monthly. The platform began as fashion-only "Trendyol Mall" and has expanded into every category, but fashion remains the most heavily merchandised vertical.

The Trendyol Marketplace API + XML Flow

Trendyol exposes two ingestion paths: the REST Marketplace API (canonical path for stock/price updates, orders, returns; token + supplierId auth) and the bulk XML import (used for initial catalog onboarding and large category migrations). For ongoing operations Zunapro uses REST exclusively, with bulk XML reserved for migrations. Stock and price updates are batched into 1,000-SKU chunks per cron tick.

Trendyol Commission Bands 2026

Trendyol's commission schedule is tiered by category, with three broad bands plus optional Trendyol Ads on top. Commissions are updated by Trendyol's Seller Center periodically.

Trendyol XML Field Mapping

The canonical Trendyol payload requires barcode (GTIN-13, primary match), stockCode (seller SKU, secondary match), title (≤120 chars), listPrice + salePrice (KDV-inclusive), quantity (where MIN-stock dedup applies), categoryId, attributes[] (color/size/material, category-dependent), and images[] (1–8, HTTPS, square preferred).

3. Hepsiburada — Heritage Marketplace with HepsiJet Logistics

From 1998 Pioneer to NASDAQ-Listed Marketplace

Hepsiburada is Turkey's oldest large-scale e-commerce platform, founded in 1998 by Hanzade Doğan Boyner as part of the Doğan Group. After a 2021 NASDAQ IPO (HEPS), the marketplace serves 13M+ active customers and hosts 100K+ third-party sellers. Electronics, home appliances and big-box categories remain its strongest verticals — partly due to the HepsiJet delivery network's ability to handle large items.

HepsiJet and HepsiLojistik — The Logistics Stack

HepsiJet is Hepsiburada's in-house last-mile delivery brand. HepsiLojistik is the FBA-equivalent: sellers ship inventory to Hepsiburada warehouses (Gebze, Esenyurt), and Hepsiburada handles picking, packing and dispatch via HepsiJet. Listings fulfilled through HepsiLojistik carry a "Hızlı Kargo" badge and earn priority placement.

Hepsiburada XML Integration Path

Hepsiburada's Listing API accepts both JSON-REST and XML payloads — 2026 best practice is JSON-REST for incremental updates and XML for bulk imports. Field mapping requires merchantSku (primary), barcode (secondary), productName (≤200 chars), price + availableStock (KDV-inclusive), brand + categoryId (exact-match required), attributes, and images (minimum 1, recommended 5+).

The Critical MIN-Stock Dedup Case

Hepsiburada was the marketplace where the duplicate-listing oversell incident chain peaked, leading directly to the June 2026 Zunapro fix. When a seller's master SKU was listed twice on Hepsiburada (typically because of multi-warehouse setups or variant collisions), the old sync logic summed the duplicates, reporting 2× or 4× actual stock. Orders flooded in past real inventory, and seller-rating penalties followed. The MIN-stock dedup policy — take the minimum across duplicate listings rather than the sum — eliminated the issue.

Hepsiburada Commission Bands 2026

4. n11 — Doğuş Group's General Marketplace

From SK Group to Doğuş — A Strategic Reset

n11 was launched in 2013 as a JV between South Korea's SK Group and Doğuş Holding. After SK's exit, n11 became fully Doğuş-owned. The 2026 incarnation reports 9M+ customers and 60K+ sellers, with strength in fashion, tech and a loyal returning-buyer base built on long-running loyalty programs.

n11 Integration: SOAP + REST + XML

n11 has the most heterogeneous integration surface in Turkey: SOAP API (original path, still used for some category-attribute endpoints), REST API (modern path for stock/price/order operations), and bulk XML for catalog imports. Zunapro's n11 adapter wraps all three behind a single interface — sellers never see SOAP envelopes directly. Recommended 2026 configuration: REST for ongoing operations + bulk XML for migrations.

n11 Commission Bands 2026

5. Amazon Turkey — The Global Giant Locally

The 2018 Local Launch and the FBA Tuzla Hub

Amazon launched its Turkish storefront amazon.com.tr in September 2018, adding Turkish-language search, customer service, and a dedicated FBA Tuzla fulfillment center serving the Marmara region. By 2026 Amazon Turkey reports 7M+ Turkish customers, with category strength concentrated in premium electronics, books in English, kitchen appliances, and cross-border-eligible SKUs.

SP-API Flat Files vs Direct API

Amazon Turkey uses the standard Selling Partner API (SP-API). Stock and price updates can be pushed as flat-file feeds (TSV files with inventory and price columns — closest cousin to XML, used for high-volume bulk updates) or real-time SP-API calls (JSON-REST for individual SKU operations; used for repricer and event-driven push). Zunapro pushes flat-files at the 15-minute cron and switches to per-SKU SP-API calls for event-driven updates, keeping Amazon stock data within 30 seconds of master truth.

Buy Box and Repricing

The Buy Box is the entry point for the vast majority of sales — often above 80% of total volume on a given ASIN. Winning it depends on price competitiveness, FBA status, account health, and shipping speed. Zunapro's repricer integrates with SP-API to adjust prices every few minutes within seller-defined floors and ceilings.

Amazon Turkey Commission Bands 2026

On top of referral fees, Amazon Turkey Professional Sellers pay a monthly subscription of approximately ₺399 (currently set in TRY rather than USD), plus FBA fulfillment fees if you opt into FBA Tuzla.

6. Çiçeksepeti & Pazarama — Specialist High-Growth Channels

Çiçeksepeti — From Gifting Pure-Play to Diversified Marketplace

Çiçeksepeti launched in 2006 as a flowers-and-gifts pure-play and gradually pivoted toward a general marketplace. By 2026 it serves 11M+ customers with category strength in gifting, home decor, cosmetics and same-day-delivery categories. The same-day delivery network — built originally for floral fulfillment — is now a competitive differentiator.

Çiçeksepeti XML Integration

Çiçeksepeti accepts both REST API calls and an XML feed. Field mapping uses sellerStockCode as the primary match, plus a category attribute set that's particularly strict for gifting (occasion, recipient, color theme).

Pazarama — Yıldız Holding's Fast-Growing Newcomer

Pazarama launched in 2020 as Yıldız Holding's (parent of Ülker, Godiva) entry into marketplace e-commerce. By 2026 it serves 4M+ customers and is widely cited as Turkey's fastest-growing marketplace by relative volume. Yıldız's FMCG ownership translates into strong category presence in food, snacks, baby and home-care SKUs.

Pazarama XML Integration

Pazarama operates a clean REST + XML combination with field mapping closely modeled on Trendyol's schema. Sellers migrating from Trendyol typically need minimal remapping. Onboarding is unusually fast — most new sellers receive activation within 24 hours of application.

Specialist Channel Commission Bands 2026

7. IKAS Storefronts & Supplier XML Feeds (Topbas Toptan)

IKAS — Turkey's Native E-Commerce SaaS

IKAS was founded in 2017 in Istanbul as a Turkish-native answer to Shopify. By 2026 it powers 30,000+ merchant storefronts with deep local payment integrations (PayTR, iyzico, Param), shipping (Aras, MNG, Yurtiçi) and KDV handling baked in. For multi-marketplace sellers IKAS plays two roles: an owned storefront alongside the marketplaces, and a clean REST API + XML output that Zunapro mirrors outward to Trendyol, Hepsiburada, n11 and others.

IKAS as Master Catalog

Many Turkish sellers in 2026 use IKAS as their master catalog, with Zunapro reading the IKAS API as canonical source and pushing to marketplaces. This pattern is common for D2C brands that built on IKAS first and added marketplaces later. Integration takes about 10 minutes: paste IKAS API credentials, choose which collections to mirror, and Zunapro handles the rest.

Topbas Toptan — Reference Wholesaler XML

Topbas Toptan is one of Turkey's larger B2B wholesalers and a useful reference example. The Topbas XML feed contains price tiers (reseller pricing distinct from retail), stock fields in piece + carton units, image URLs as semicolon-separated lists, and a stable stok_kodu field mapping directly to the canonical SKU.

The 40+ Pre-Built Wholesaler Adapters

Zunapro ships pre-built XML adapters for over 40 Turkish wholesalers including Topbas Toptan, B2BORA, MOY, Modabu, Modasonsuz and Toptanbul. Adding a new wholesaler XML typically takes under 30 minutes: paste the feed URL, the parser auto-detects encoding (UTF-8 / ISO-8859-9), CDATA wrappers and record-level elements, you drag-and-drop source fields onto the canonical schema, save the mapping (reusable across all sellers using the same wholesaler), and the first sync runs immediately.

Commission & Sync Comparison Table 2026 — All Marketplaces

The single most useful artifact for choosing where to push your XML feed is a side-by-side commission view. The table below summarizes 2026 commission bands, integration paths, and sync characteristics.

Marketplace	Low Tier	Mid Tier	High Tier	Integration Path / Subscription
Trendyol	8% – 14%	14% – 19%	18% – 25%	REST API + bulk XML · free account · Trendyol Ads optional
Hepsiburada	7% – 13%	13% – 18%	17% – 24%	Listing API (JSON/XML) · free account · HepsiLojistik fees if FBA
n11	9% – 14%	14% – 18%	17% – 22%	SOAP + REST + bulk XML · free account
Amazon Turkey	8% – 13%	13% – 17%	15% – 20%	SP-API flat files + REST · ~₺399 / mo Pro Seller + FBA
Çiçeksepeti	10% – 15%	15% – 18%	18% – 22%	REST + XML · free account · same-day delivery option
Pazarama	8% – 12%	12% – 16%	16% – 18%	REST + XML · free account · fast 24h onboarding

Reading the table: Trendyol and Hepsiburada are roughly equivalent on commission, with Trendyol leading on reach and Hepsiburada on logistics. n11 sits slightly above on commission but compensates with loyalty-program reach. Amazon Turkey is the only platform with a monthly subscription fee. Çiçeksepeti is positioned for gifting / cosmetics premium categories; Pazarama is the cheapest entry point for new sellers, with FMCG strength.

Turkish Legal Framework 2026 — KDV, e-Fatura & GİB

KDV (Turkish VAT) — 20% Standard Rate

Turkey's Value Added Tax is called Katma Değer Vergisi (KDV), administered by the Gelir İdaresi Başkanlığı (GİB — Revenue Administration). The 2026 standard rate is 20%, with reduced rates of 10% (basic food, children's products, some healthcare) and 1% (essential staples, agricultural inputs) for specific categories. Marketplace sellers must price all SKUs KDV-inclusive in the marketplace interface — the gross price the shopper sees already contains the 20% (or applicable reduced) KDV. Zunapro applies the correct KDV per category when converting net supplier prices into KDV-inclusive marketplace prices.

e-Fatura & e-Arşiv via GİB

Turkey's e-Fatura (B2B) and e-Arşiv (B2C) systems are the most consequential compliance items for marketplace sellers in 2026. e-Fatura is mandatory above ₺5M annual turnover — every B2B invoice must be issued through GİB's e-Fatura system using a structured XML format signed with the seller's mali mühür. e-Arşiv is mandatory above ₺500K annual e-commerce turnover. Every successfully submitted invoice receives a UUID that must be stored alongside the order. Zunapro auto-issues e-Fatura / e-Arşiv invoices the moment a marketplace order is received, stores the UUID, and matches it against PayTR / iyzico / Param settlement reports for reconciliation.

GİB XML Schema Requirements

GİB-compliant XML invoices follow the UBL-TR 1.2 standard (Universal Business Language, Turkey profile) with seven mandatory namespaces and a strict ordering of XML elements. Validation is enforced at the GİB submission endpoint — a single misplaced element fails the entire batch. Zunapro's invoicing module is UBL-TR 1.2 compliant and ships a self-test harness that validates against the GİB sandbox.

Consumer Protection — Distance Sales & KVKK

• 14-day right of withdrawal on distance-purchased products (Mesafeli Sözleşmeler Yönetmeliği)
• 2-year statutory warranty on B2C sales, independent of any commercial guarantee
• KVKK — Turkey's GDPR-equivalent, enforced by KVKK Kurumu. Marketplaces handle shopper data, but sellers remain joint controllers for direct B2C contact data.

8. Stock & Price Sync: The 15-Minute Cron + MIN-Stock Policy

Why 15 Minutes Is the 2026 Standard

The default Zunapro sync cron runs every 15 minutes — a balance of three constraints: marketplace rate limits (Trendyol, Hepsiburada and n11 throttle stock/price endpoints; sub-15-min intervals on a 10K-SKU catalog hit throttles), stock-out exposure (longer intervals let average-velocity stores oversell during traffic spikes), and supplier feed cadence (most Turkish wholesalers refresh XML every 5–15 minutes; pulling more frequently is wasted).

Event-Driven Push for Order Decrements

The 15-minute cron is the safety net. The primary mechanism for stock-out prevention is event-driven push: every successful order on any marketplace fires an event that triggers an immediate stock decrement on every other marketplace where that SKU is listed. Average end-to-end latency is under 30 seconds, dominated by marketplace API round-trip times.

The MIN-Stock Dedup Policy (June 2026 Fix)

The single most important sync-correctness change of 2026 was moving from SUM-stock to MIN-stock across duplicate listings. The same supplier SKU is sometimes listed twice on one marketplace (multi-warehouse, variant collisions). Old logic summed duplicates and overstated inventory. New logic reports the minimum — a safe lower bound that occasionally understates by a few units but never oversells. Production impact since the June fix: oversell incidents dropped to near zero on Hepsiburada and Trendyol for affected sellers.

SKU + Barcode Matching with Fuzzy Fallback

Zunapro's matching engine uses a three-level fallback: (1) stock code — supplier's stok_kodu or seller SKU, matches ~92% of Turkish feeds; (2) GTIN / barcode — EAN-13 / UPC-A, covers the remaining ~7%; (3) fuzzy title + brand — last-resort fallback for legacy catalogs, flagged for manual review. Each match produces a confidence score — below 85% the match is queued for manual review rather than auto-published.

9. XML Schema, Field Mapping & Markup Rules

The Canonical Supplier XML Schema

Zunapro normalizes every supplier XML — Topbas Toptan, B2BORA, IKAS, custom ERP — into a single canonical schema with 17 fields:

• sku, gtin, title, description, brand, category
• price_net, price_gross, kdv_rate (20 / 10 / 1)
• stock, stock_unit (piece / carton / kg), weight_kg, dimensions
• color, size, images[], attributes{} — free-form key-value attributes

Markup Rules — From Net Supplier to Marketplace Gross

Between the supplier price and the marketplace gross price, Zunapro evaluates a cascade: (1) category percentage markup (e.g. +35% on apparel, +18% on electronics); (2) brand-specific overrides; (3) commission absorption (add Trendyol's commission % to maintain net margin); (4) KDV application (multiply by 1 + kdv_rate/100); (5) rounding rules (psychological .99 / .90 or whole-lira); (6) competitive repricing (optional) — ₺1 below lowest Buy Box competitor, within floor/ceiling.

Per-Marketplace Field Translation

The canonical schema is translated to each marketplace's specific payload format at push time:

Canonical Field	Trendyol	Hepsiburada	n11	Amazon TR
sku	stockCode	merchantSku	productSellerCode	sku (SP-API)
gtin	barcode	barcode	gtin	asin / external_id
price_gross	salePrice	price	price	standard-price
stock	quantity	availableStock	stockItems.quantity	quantity (inventory feed)
title	title	productName	title	item-name
category	categoryId	categoryId	categoryId	browse-node-id

10. How to Connect XML Feed in 2026 — Step-by-Step

1. Pick Your Source — Wholesaler XML, IKAS, or Own ERP

Decide which feed is your master:

• Wholesaler XML (Topbas Toptan, B2BORA, etc.) — fastest path; you're a reseller, not a stockholder
• IKAS storefront — your D2C platform is the source; marketplaces are mirrored downstream
• Own ERP / WMS — you hold stock; ERP is the master and marketplaces are downstream targets
• Hybrid — Zunapro can union multiple sources with priority rules per SKU

2. Choose Your Marketplaces (Decision Tree)

• Maximum reach, any category → Trendyol
• Electronics, white goods, big-box → Hepsiburada + Trendyol
• Fashion + cosmetics → Trendyol Mall + Çiçeksepeti + Pazarama
• Premium tech, cross-border ambition → Amazon Turkey + Trendyol
• FMCG, food, baby, home-care → Pazarama + Trendyol + Hepsiburada
• Loyalty-driven returning buyers → n11 + Trendyol

The typical winning 2026 configuration is Trendyol + 2–3 specialist marketplaces, all mirrored from one master XML.

3. Company Registration & e-Fatura Activation

You'll need a Turkish company entity (şahıs / Ltd. Şti. / A.Ş.), vergi levhası (tax registration from GİB), mali mühür (financial seal certificate for e-Fatura signing), e-Fatura activation via GİB portal (mandatory above ₺5M turnover), and e-Arşiv activation (mandatory above ₺500K e-commerce turnover).

4. Marketplace Seller Account Creation

Create a seller account in each portal: Trendyol Partner (partner.trendyol.com), Hepsiburada İş Ortağım, n11 Mağaza, Amazon Seller Central, Çiçeksepeti İş Ortağım, Pazarama Satıcı Paneli. Approval is typically 1–7 business days; Pazarama is fastest (often under 24h), Amazon is slowest (verification documents required).

5. Connect via Zunapro (10-Minute Integration)

1. Sign in to Zunapro and open the Turkey module
2. Paste your supplier XML URL — the parser auto-detects schema, encoding, record structure
3. Map fields — drag the supplier fields onto the canonical schema; Zunapro suggests mappings using ML
4. Connect each marketplace — paste API keys / OAuth credentials into the Trendyol, Hepsiburada, n11, Amazon, Çiçeksepeti and Pazarama tiles
5. Configure markup rules — category percentages, brand overrides, KDV rates
6. Enable e-Fatura / e-Arşiv — upload your mali mühür certificate; Zunapro handles the rest
7. Run dry-run validation — Zunapro previews the first 50 SKUs with their full target payloads, no actual marketplace pushes
8. Go live — first sync completes in roughly 10 minutes for a 1,000-SKU catalog; full 10K-SKU catalogs typically complete in under an hour

Marketplace XML Integration FAQ 2026