Trendyol Integration Guide 2026: REST API, XML Connection & Centralized Store Management

1. Trendyol API Architecture 2026

Trendyol's Marketplace API is a RESTful, JSON-over-HTTPS interface published on a single production base URL — https://api.trendyol.com — with a separate stage environment at https://stageapi.trendyol.com. Every API call is authenticated using HTTP Basic Auth: the Authorization header carries a base64-encoded ApiKey:ApiSecret pair, and the Supplier ID is passed as a path parameter on every supplier-scoped endpoint. There is no separate access-token round-trip for first-party sellers — Basic Auth is checked on every request — which keeps the integration simple but means leaked credentials need to be rotated immediately via the Partner panel.

Base URL, Authentication, Headers

POST https://api.trendyol.com/sapigw/suppliers/{supplierId}/v2/products
Authorization: Basic BASE64(ApiKey:ApiSecret)
User-Agent: {supplierId} - SelfIntegration
Content-Type: application/json
Accept: application/json

The User-Agent header is non-cosmetic: Trendyol's traffic-shaping and rate-limit accounting key off it. Integrators (such as Zunapro) send {supplierId} - Zunapro; first-party sellers send {supplierId} - SelfIntegration. Mis-stamped User-Agent headers can trigger 401/403 responses even with valid credentials.

Rate Limits and Quotas

Trendyol enforces per-endpoint, per-supplier rate limits. The published 2026 ceilings are:

• Product endpoints — typically 60 requests/minute per Supplier ID, with burst tolerance up to 90/min for 30 seconds
• Order endpoints — typically 600 requests/minute (orders is a high-traffic, low-latency endpoint by design)
• Price & stock update endpoints — typically 100 requests/minute, with each request carrying up to 1,000 SKUs in a single batch
• Category & attribute lookups — typically 30 requests/minute (these are slow-changing, so aggressive caching is expected)

Every response includes X-RateLimit-Limit, X-RateLimit-Remaining and, on 429s, Retry-After headers. A well-built integration uses a token-bucket queue per Supplier ID and back-pressures on 429 with exponential back-off; Zunapro implements this by default so that even multi-thousand-SKU bulk pushes never trip the limits.

OAuth 2.0 for Independent Integrators

For independent middle-layer integrators (Zunapro and similar SaaS platforms acting on behalf of many suppliers), Trendyol offers an OAuth 2.0 authorization-code flow rather than direct Basic Auth. The integrator registers a client_id / client_secret with Trendyol's developer relations team, the supplier authorizes the integrator from the Partner panel, and the integrator receives a 1-hour access token plus a refresh token for re-issuance. This avoids ever handling the supplier's raw ApiKey / ApiSecret and is the audit-friendly path for enterprise customers managing many Trendyol stores.

Webhooks

Trendyol pushes order lifecycle events to your registered webhook URL: Created, Picking, Invoiced, Shipped, Delivered, Cancelled, Returned, UnDelivered. The webhook payload is a JSON envelope carrying the order ID and the new status; your endpoint must respond with HTTP 200 within 3 seconds. On failure Trendyol retries 5 times with exponential back-off, then parks the event — which is why a 5-minute reconciliation pull against /sapigw/suppliers/{id}/orders is a non-optional safety net.

2. Connecting via REST API — Step by Step

The official happy path for connecting to Trendyol's REST API in 2026 is short and well-documented — but the order of operations matters because some legal prerequisites are upstream of the API itself.

2.1 Open a Trendyol Seller Account

Visit partner.trendyol.com and submit an "Open a Trendyol Account" application. You will need:

• VKN (Vergi Kimlik Numarası) — Turkish tax number (or foreign-equivalent business registration for Trendyol International)
• Trade Registry Gazette (Ticaret Sicil Gazetesi) for limited liability or joint-stock companies
• Signature circular (imza sirküleri)
• ETBİS (Elektronik Ticaret Bilgi Sistemi) registration receipt — mandatory for any Turkish e-commerce operator since 2018
• Bank account (IBAN TR) in the legal entity's name for marketplace payouts

Approval typically takes 2–5 business days. Once approved, the seller receives a Supplier ID and access to the Trendyol Partner panel.

2.2 Generate API Key and Secret

From the Partner panel, open Account Settings → Integration Information and click "Create API Key". Trendyol generates a 40-character API Key and a 40-character API Secret. Both values are shown once — they cannot be retrieved later. Save them in a password manager or, better, paste them directly into Zunapro's integration tile which stores them as AES-256-encrypted, masked secrets.

2.3 First Smoke-Test Request

Confirm credentials are live by hitting the supplier-info endpoint:

curl -X GET "https://api.trendyol.com/sapigw/suppliers/{supplierId}/addresses" \
  -H "Authorization: Basic $(echo -n 'API_KEY:API_SECRET' | base64)" \
  -H "User-Agent: {supplierId} - SelfIntegration" \
  -H "Accept: application/json"

A successful response returns the supplier's registered warehouse and return addresses in JSON. A 401 means the Basic Auth header is wrong; a 403 means the Supplier ID does not match the credentials; a 404 means the endpoint path is malformed.

2.4 OAuth Variant (for Multi-Supplier Integrators)

For independent integrators, the OAuth 2.0 flow looks like this:

1. Integrator redirects supplier to:
   https://partner.trendyol.com/oauth/authorize
     ?client_id={integratorClientId}
     &response_type=code
     &redirect_uri={integratorRedirectUri}

2. Supplier approves access; Trendyol redirects back with ?code={authCode}

3. Integrator exchanges code for tokens:
   POST https://api.trendyol.com/oauth/token
     grant_type=authorization_code
     code={authCode}
     client_id={integratorClientId}
     client_secret={integratorClientSecret}

4. Response: { access_token, refresh_token, expires_in: 3600 }

Access tokens are valid for 1 hour and refreshable for 30 days. Zunapro handles all four steps transparently so the supplier just sees a single "Connect to Trendyol" button.

2.5 Post Your First Product

Use POST /sapigw/suppliers/{supplierId}/v2/products with a JSON array of items. The minimal product object requires barcode, title, productMainId, brandId, categoryId, quantity, stockCode, dimensionalWeight, description, currencyType (typically TRY), listPrice, salePrice, vatRate, cargoCompanyId, an images array (1–8 URLs) and an attributes array of category-specific attribute IDs.

3. Product Synchronization at Scale

Bulk Upload — 1,000 SKUs per Batch

Trendyol's POST /v2/products endpoint accepts up to 1,000 SKUs per single JSON request. For sellers with 10,000+ SKU catalogs this is the difference between a one-hour onboarding and a multi-day one. The batch returns a batchRequestId per call; Trendyol processes each batch asynchronously and exposes per-SKU success / failure once processing completes (typically within 1–15 minutes depending on validation queue depth).

Category Mapping — the Single Hardest Step

Trendyol's category tree is deep and strict. As of 2026 there are roughly 12,000 leaf categories, each with its own required and optional attribute set. A jeans listed under "Men → Trousers → Casual" requires gender, size, color, material and fit-type attributes; a smartphone under "Electronics → Mobile → Phones" requires brand, model, memory, guaranteeType and warrantyPeriod. Posting a product to a wrong leaf category, or to the right category but missing a required attribute, produces a silent rejection in the batch result.

The supported approach is:

1. Pull the live category tree from GET /sapigw/product-categories (cache for 24h)
2. For each leaf category, pull required + optional attributes from GET /sapigw/product-categories/{categoryId}/attributes
3. Match your master-catalog SKUs to Trendyol leaf categories — Zunapro uses an ML mapper trained on millions of historical Trendyol listings to suggest categories from title + brand + your taxonomy with a 92%+ first-pass match rate
4. Validate every SKU against required attributes before hitting the POST endpoint to avoid rate-limit waste on doomed requests

Brand Whitelist and brandId

Every product must reference a brandId that exists in Trendyol's brand registry. New brands cannot be created on the fly — they go through a manual brand-approval process via the Partner panel (typically 1–3 business days). Use GET /sapigw/brands?name={brandName} to look up an existing brandId before creating products.

Image Upload Rules

• 1–8 images per product
• Public, HTTPS URLs (Trendyol crawls and re-hosts the images on its CDN)
• Minimum 1200×1800 px, white background for fashion categories
• JPG or PNG, max ~10 MB per image
• First image becomes the search-result thumbnail — invest in it

Batch Status Polling

GET https://api.trendyol.com/sapigw/suppliers/{supplierId}/products/batch-requests/{batchRequestId}

Response:
{
  "batchRequestId": "abc-def-...",
  "status": "COMPLETED",
  "itemCount": 1000,
  "items": [
    { "requestItem": {...}, "status": "SUCCESS" },
    { "requestItem": {...}, "status": "INVALID", "failureReasons": ["INVALID_BARCODE"] }
  ]
}

4. Order Management — Webhooks and the Status Flow

The 2026 Order Lifecycle

A Trendyol order moves through a fixed status flow:

Created → Picking → Invoiced → Shipped → Delivered

Branch flows:
  Cancelled (any time before Shipped)
  Returned (after Delivered, within 14-day window)
  UnDelivered (carrier exception)

Each transition fires both a webhook event (push) and is reflected in the next GET /orders pull (poll). The seller is responsible for transitioning Picking → Invoiced → Shipped; Trendyol's logistics partners control Shipped → Delivered.

Webhook Receipt and Idempotency

Every webhook carries a unique shipmentPackageId. Process it idempotently — Trendyol does retry events on a non-200 response, and duplicate processing on your side (double invoicing, double picking) is a real risk. The pragmatic pattern is:

POST /webhook/trendyol
{
  "supplierId": 123456,
  "shipmentPackageId": 987654321,
  "status": "Picking",
  "timestamp": 1717930000000
}

Handler:
1. Acquire lock on shipmentPackageId
2. Check stored status; if already >= "Picking", return 200 (no-op)
3. Persist new status, schedule downstream actions (e-invoice, picking task)
4. Return HTTP 200 within 3 seconds

Cancel and Refund Flow

Buyer-initiated cancels arrive as Cancelled webhooks; seller-initiated cancels are pushed via POST /sapigw/suppliers/{id}/orders/{orderId}/cancel with a cancellation reason code (OUT_OF_STOCK, OTHER etc.). Refunds for delivered + returned items are handled by Trendyol automatically; the seller's only obligation is to confirm receipt of the returned goods within 48 hours of the carrier scan.

Trendyol Express Shipping Label

Once a package is moved to Picking status, request the shipping label via GET /sapigw/suppliers/{id}/orders/{orderId}/labels — Trendyol returns a PDF (and optionally ZPL for thermal printers) containing the Trendyol Express barcode, the buyer's address and the cargo-tracking number. The barcode is the single carrier-routing artifact — print, attach, scan into your WMS, drop at a Trendyol Express pickup point (or schedule courier pickup for high-volume sellers).

5. Stock & Price Updates in Real Time

The Stock-Price Push Pattern

Trendyol exposes a dedicated endpoint for stock and price updates: POST /sapigw/suppliers/{id}/products/price-and-inventory. Each call accepts up to 1,000 items, with barcode, quantity, salePrice and optional listPrice per item. Updates apply within seconds for stock, within 2–5 minutes for price (Trendyol caches price for shopping-feed consistency).

POST /sapigw/suppliers/{id}/products/price-and-inventory
{
  "items": [
    { "barcode": "8690123456789", "quantity": 42, "salePrice": 549.90, "listPrice": 699.90 },
    { "barcode": "8690987654321", "quantity": 0, "salePrice": 199.00 }
  ]
}

The Master → Local → Targets Sync Architecture

For sellers running multiple sales channels (Trendyol + Hepsiburada + Çiçeksepeti + own shop), the only sane architecture is a master inventory in Zunapro that pushes to every target marketplace. The 2026 Zunapro production stack runs a 15-minute cron plus event-driven push: any stock change in the master fires an immediate price-and-inventory push to Trendyol, while the cron ensures eventual consistency for any push that fell through the cracks. SKUs are matched by barcode (primary) or stockCode (fallback) — never by Trendyol's internal product ID, which can change on category re-mappings.

VAT and Price Display Rules

Trendyol prices are VAT-inclusive. Turkey's 2026 VAT (KDV) regime is 20% standard, 10% reduced (food, books, medicines, basic goods) and 1% special (essential foodstuffs, certain agricultural products). The seller specifies vatRate per product and is responsible for picking the correct rate; mistakes are surfaced as e-invoice rejection by GİB after the fact, which is expensive to remediate.

Trendyol Fast Sale and Campaign Sync

Trendyol's flagship campaigns — Trendyol Fast Sale (Hızlı Satış), Trendyol Week, Çarşamba Pazarı (Wednesday Market) — are mandatory-eligibility campaigns that boost listing visibility but carry an additional 1–3% campaign commission. Sellers opt SKUs into campaigns via POST /sapigw/suppliers/{id}/products/campaigns with discounted price overrides; Zunapro automatically validates campaign price floors against your master margin rules to prevent below-cost commitments.

6. XML / CSV Alternative — When (and When Not) to Use It

The XML Pull Model

Trendyol supports an XML feed model as an alternative to the REST POST flow. The seller hosts an XML file at a public HTTPS URL describing the catalog; Trendyol pulls it on a configurable cadence (typically every 1–4 hours). The XML schema is published in the Partner panel and mirrors the product object shape of the REST endpoint — barcode, title, brandId, categoryId, attributes, images, price, stock.

The same pattern is supported via CSV (one row per SKU) for sellers whose ERP exports CSV more naturally than XML.

Comparison: REST API vs XML / CSV

When XML / CSV Is Actually the Right Call

• Legacy ERP without HTTP-client capability that already exports XML / CSV nightly
• Slow-moving catalogs (under 500 SKUs, weekly price changes, monthly catalog adds)
• Initial migration from another marketplace where a one-shot CSV export accelerates the first sync

For everything else — order webhooks, real-time stock, campaign opt-ins, multi-channel sync — REST is the only viable path in 2026. Zunapro supports both modes but defaults to REST and uses XML / CSV strictly as an ETL ingestion source from legacy ERPs.

7. Trendyol Express & FBA Trendyol

Trendyol Express — The Logistics Layer

Trendyol Express is Trendyol's wholly-owned logistics arm — launched in 2018 and now operating Turkey's densest e-commerce-native parcel network. By 2026 it covers 50,000+ self-service lockers and pick-up points alongside its own courier fleet, hitting 81 provinces with same-day delivery in Istanbul, Ankara, Izmir, Bursa and Antalya, and next-day delivery to the rest of mainland Turkey. Buyers see "Hızlı Teslimat" (fast delivery) badges on eligible listings, and Trendyol's search ranking weights them aggressively.

FBA Trendyol — Trendyol Logistics Warehouse

FBA Trendyol (sometimes called "Trendyol Lojistik Deposu" or "Trendyol Mağaza Plus") is the Amazon-FBA equivalent: sellers ship inventory to Trendyol's fulfillment centers in Çorlu (the flagship facility, 250,000 m² near Istanbul), Sancaktepe and Ankara, and Trendyol handles storage, picking, packing, last-mile delivery via Trendyol Express, and returns. FBA listings carry a distinct "Trendyol'dan Gönderim" badge and receive priority visibility weighting in search.

FBA Trendyol Fees and Eligibility

• Onboarding — apply through the Partner panel; Trendyol's commercial team reviews monthly volume, SKU dimensions and category fit
• Storage fee — billed monthly per cubic meter of warehouse space occupied; varies by season (Q4 storage costs more)
• Pick-and-pack fee — per-order flat rate, varies by package weight band (under 500g, 500g–2kg, 2–5kg, 5–10kg, 10kg+)
• Returns handling — included in the pick-and-pack fee for standard returns; flagged conditions billed separately

When FBA Trendyol Makes Sense

The break-even point for FBA Trendyol against self-fulfillment is roughly 800–1,200 units per month per warehouse SKU for fast-moving consumables, electronics or fashion in size-runs. Below that, self-fulfillment via Trendyol Express drop-off plus your own Aras / Yurtiçi / MNG contract is usually cheaper. Above it, the conversion lift from the "Trendyol'dan Gönderim" badge plus the same-day-delivery promise almost always outweighs the unit-fulfillment cost.

8. GİB e-Invoice Integration (e-Fatura / e-Arşiv)

The GİB Mandate

Turkey's Gelir İdaresi Başkanlığı (GİB — Revenue Administration) has made e-Fatura mandatory for any business with annual turnover above the GİB-published threshold (revised annually; ~TRY 3M as of 2026) and e-Arşiv Fatura mandatory for all B2C invoices above ~TRY 30,000 (revised annually). For active Trendyol sellers in 2026, e-Fatura / e-Arşiv coverage is effectively universal — virtually every marketplace order must produce a GİB-stamped electronic invoice within the order-status window or face penalties.

The Five GİB-Certified Integrators

Sellers can either use GİB's portal directly (impractical at marketplace volumes) or contract with a GİB-certified Özel Entegratör (Special Integrator). The five dominant players in 2026 are:

• Logo Yazılım — the largest Turkish ERP vendor; e-Logo for invoice issuance
• Mikro Yazılım — mid-market ERP and e-invoice provider, strong in SME segment
• Uyumsoft — independent integrator with a robust REST API and the largest marketplace seller base
• Foriba — enterprise-tier provider (acquired by Sovos in 2019), strong in regulated industries
• Veriban — fast-growing alternative with competitive pricing and a developer-friendly API

The Marketplace e-Invoice Flow

1. Trendyol webhook: order status -> "Picking"
2. Zunapro pulls order detail (buyer name, VKN/TCKN, address, items)
3. Zunapro POSTs invoice draft to integrator (Logo/Mikro/Uyumsoft/Foriba/Veriban)
4. Integrator signs with e-Signature certificate, submits to GİB
5. GİB returns ETTN (Electronic Document Unique Number)
6. Zunapro stores ETTN, attaches PDF to Trendyol order
7. Zunapro transitions Trendyol order Picking -> Invoiced via API

Practical 2026 Choice

For new sellers, Uyumsoft and Veriban are the easiest to onboard (web signup, REST API, no on-prem dependency). Sellers already running Logo or Mikro ERP should stay on the same vendor's e-invoice product for accounting reconciliation. Foriba is the choice for large enterprises with complex tax workflows. Zunapro ships with all five integrations behind a single configuration screen — pick the integrator, paste the API credentials, and every Trendyol order auto-invoices.

9. Common Errors and How to Design Around Them

Category Mismatch

Symptom: batch result shows INVALID_CATEGORY or CATEGORY_NOT_LEAF. Cause: posting to a non-leaf category, or to a leaf category whose attribute set the SKU does not match. Fix: always post to leaf categories only (the API rejects non-leaf), and pre-validate attributes against the category's required: true set before POST.

Missing Required Attributes

Symptom: MANDATORY_ATTRIBUTE_MISSING on otherwise-valid SKUs. Cause: Trendyol marks ~30% of attributes mandatory on a per-category basis (gender for fashion, warranty for electronics, etc.). Fix: cache the per-category attribute-requirement map and gate POSTs on completeness; Zunapro auto-fills from your master taxonomy where possible.

Stock Sync Delays

Symptom: a sold-out SKU still shows in-stock on Trendyol for several minutes, causing oversells. Cause: price-and-inventory pushes are eventually consistent at ~5–8 second median latency, and during traffic spikes (Black Friday, Trendyol Week) the queue can stretch to 30–60 seconds. Fix: implement a local safety buffer (reserve last 1–2 units as out-of-stock buffer per high-velocity SKU) and push stock changes synchronously on the order-confirmation event, not just on cron.

Webhook Misses

Symptom: order webhook never arrives or arrives hours late. Cause: usually a firewall change on the seller side, a TLS cert renewal that broke the webhook URL, or a brief outage that exceeded Trendyol's 5-retry budget. Fix: always run a parallel 5-minute reconciliation pull against /sapigw/suppliers/{id}/orders?status=Created&startDate=...; Zunapro does this by default and idempotently merges any pulled order that the webhook also delivered.

Multiple Listings, Same Barcode (Mükerrer Listing)

Symptom: a single SKU appears as multiple Trendyol listings, and stock decrements differently on each. Cause: historical merges, duplicate barcode entries, or multi-store same-product fan-out. Fix: Zunapro's MIN-stock deduplication policy (introduced in our 2026-06-06 production update) collapses all duplicate listings under one barcode and tracks the minimum stock value across them, preventing the classic "sold twice on two listings, one delivery promised" disaster.

10. Trendyol Commission and Vendor Fees 2026

Trendyol's 2026 commission schedule is tiered by category, with three broad bands and no fixed per-item fee. Campaign participation (Trendyol Fast Sale, Trendyol Week, Çarşamba Pazarı) adds an additional 1–3% on top of the category rate.

Vendor / Subscription Fees

Trendyol does not charge a monthly subscription. There is no Amazon-style "Professional Seller" tier. Sellers pay:

• Category commission on every sale (8–22%)
• Campaign commission when participating in Trendyol Fast Sale / Week (+1–3%)
• Trendyol Express per-shipment fee (paid by buyer, but flows through seller P&L)
• FBA Trendyol storage + pick-and-pack (only if enrolled)
• Trendyol Ads CPC (optional, controlled by the seller)

Payout Cycle

Standard sellers are paid on a T+14 cycle (14 days after order delivery), reduced to T+7 for sellers with a top-tier seller score. Disputed orders, returns within the 14-day window and chargebacks are held against the payout. Payouts land in the registered TR IBAN.

Turkish Legal Framework 2026 — What Marketplace Sellers Must Know

KDV (VAT) and KDV Rate Bands

Turkey's VAT — KDV (Katma Değer Vergisi) — runs three rates in 2026: 20% standard, 10% reduced (food, books, medicines, hospitality), 1% special (basic foodstuffs, agricultural). Marketplace sellers domiciled in Turkey register for KDV through their local tax office; cross-border sellers above the digital-services threshold use the KDV non-resident regime. The vatRate field on every Trendyol product POST must match the legally correct rate — mistakes propagate to e-invoices and can require correction filings.

e-Fatura / e-Arşiv (GİB Mandatory)

Already covered in detail in section 8. Bottom line for 2026: every marketplace order produces a GİB-stamped electronic invoice (e-Fatura for B2B / registered e-Fatura recipients, e-Arşiv for B2C). The seller is liable for issuance within the order-status window. Manual issuance is impractical at marketplace volumes — pick one of the five GİB integrators and automate.

KVKK — Turkish GDPR

KVKK (Kişisel Verilerin Korunması Kanunu — Law No. 6698) is Turkey's data-protection regime, structurally similar to GDPR and enforced by KVKK Kurumu. Marketplaces handle buyer-side consent and processing, but sellers remain joint controllers for any direct CS contact, marketing or post-purchase communication. Penalties for non-compliance run from TRY 60K to TRY 3M+ depending on infraction class.

ETBİS — Mandatory e-Commerce Registry

ETBİS (Elektronik Ticaret Bilgi Sistemi) is the Ministry of Trade's mandatory registry for any e-commerce operator in Turkey, in force since 2018. Sellers must register before listing on Trendyol and report annual transaction volumes. ETBİS data feeds into consumer-protection enforcement, anti-fraud screening and competition analytics.

Consumer Protection — 14-Day Withdrawal, 2-Year Warranty

• 14-day right of withdrawal — Turkish consumers may return any distance-purchased product within 14 days, no reason required (Tüketicinin Korunması Hakkında Kanun, Law No. 6502)
• 2-year statutory warranty — mandatory on B2C sales, independent of any manufacturer guarantee
• Mandatory Turkish-language product information — title, description, warranty, returns policy all in Turkish

Logistics & Shipping in Turkey — Trendyol Express First

Trendyol Express — The Dominant Layer

Trendyol Express is the default carrier on roughly 70%+ of Trendyol orders in 2026. The buyer sees free or low-cost shipping with same-day or next-day delivery in major metros, plus 50,000+ self-service lockers (Trendyol Hızlı Teslimat Noktaları) where shoppers pick up parcels 24/7. Sellers either drop packages at a Trendyol Express collection point or schedule a courier pickup; the routing slip carries the Trendyol Express barcode obtained from the order-label API.

The Other Integrated Carriers

• Yurtiçi Kargo — long-established Turkish courier, strong B2C and B2B network, integrated for Trendyol orders
• Aras Kargo — competitor with strong Anatolian coverage, often used for self-fulfilled Trendyol orders
• MNG Kargo — third major Turkish courier, common fallback for high-volume sellers
• PTT Kargo — state postal operator, widest rural reach, slower SLAs
• Sürat Kargo — regional player, competitive in Marmara and Aegean regions

Practical 2026 Shipping Stack

The pragmatic 2026 stack for a Trendyol seller: Trendyol Express as the default (it is what buyers expect), Yurtiçi or Aras as the seller-side fallback for self-fulfilled orders that miss the Trendyol Express pickup window, PTT Kargo for rural-only ZIP codes where no other carrier is economical, and FBA Trendyol for fast-moving SKUs once volume justifies the storage commitment.

How to Start Selling on Trendyol — 5-Step Onboarding

1. Trendyol Seller Account

Apply at partner.trendyol.com. Provide VKN, Trade Registry Gazette, signature circular, ETBİS registration receipt and TR IBAN. Approval in 2–5 business days.

2. ETBİS + Tax Registration

Register the legal entity in ETBİS via the Ministry of Trade portal (etbis.gtb.gov.tr) and confirm KDV registration with the local tax office. Foreign sellers operating via Trendyol International either appoint a Turkish representative or use Trendyol's import-of-record program.

3. Generate API Key + Secret

From the Partner panel → Account Settings → Integration Information, click "Create API Key". Copy the API Key (40 chars) and API Secret (40 chars) immediately — they are shown only once. Paste them into Zunapro's Trendyol tile where they are stored AES-256-encrypted and masked.

4. Connect via the Zunapro Panel

1. Sign in to Zunapro and open the Turkey module
2. Paste Supplier ID + API Key + API Secret into the Trendyol integration tile
3. Run the auto health-check (credentials, addresses endpoint, supplier info)
4. Confirm the ML-suggested category mappings for your top 100 SKUs
5. Pick your e-invoice integrator (Logo, Mikro, Uyumsoft, Foriba or Veriban) and paste those credentials
6. Toggle "Trendyol Express" + "FBA Trendyol" (if enrolled)

5. Run a Test Order

Place 3–5 stage orders against stageapi.trendyol.com to exercise the pick-pack, label-print, status-transition and refund flows end-to-end. Once green, flip the integration to production with a single toggle. First production sync of a 5,000-SKU catalog completes in roughly 30–60 minutes given Trendyol's rate limits.

The Three Trendyol Integration Paths — Compared

Before committing to an integration architecture, it helps to compare the three legitimate paths side by side.

Trendyol Integration FAQ 2026