Trendyol Integration: Orders, Stock and Payouts in One Panel

A Trendyol integration takes the work you would otherwise do by hand in the Trendyol Seller Panel — pulling orders, updating stock and prices, printing shipping labels, approving returns, checking payouts — and connects it to your own systems over the Trendyol API. An order lands in your ERP the moment it is placed, a unit leaving your warehouse reduces Trendyol stock automatically, and month-end reconciliation stops being a tour of screens. If you are selling into Turkey from abroad or scaling a Turkish operation, this guide explains how Trendyol actually behaves and what an integration has to do to keep up.

Why Trendyol behaves differently

Every marketplace has a personality. Trendyol's is built on speed and scale. There are a great many sellers, customer expectations are high, and the platform measures sellers constantly. Before designing an integration, accept four facts:

• Packages, not orders. Trendyol hands you orders as packages. If a customer buys three items and they ship on different days, Trendyol splits the package. Labels, invoices and status all live at package level.
• Barcode-first catalogue. A product's identity is its barcode. If another seller already lists the same barcode, you attach to the same product card and BuyBox competition begins.
• Dispatch deadlines. Each package carries a ship-by window. Late packages hurt your seller score and your visibility.
• Contracted carriers. The carrier and the shipping barcode are assigned by Trendyol; you print the label and hand over the parcel.

These four points shape the whole design. A setup that tracks order numbers and treats barcodes as an afterthought will eventually stall on Trendyol.

Order statuses and the flow

A Trendyol package passes through a handful of states: created, picking, invoiced, shipped, delivered. Alongside these are exception states such as undelivered, cancelled, returned and unsupplied. The integration has to read all of them and write some of them. In practice the flow looks like this:

1. A new package arrives as "created". The integration pulls it and writes the customer, line items, carrier and payment details into your ERP.
2. When the warehouse starts picking, the package is moved to "picking". This tells Trendyol you have seen the order.
3. The invoice is issued in your ERP and its link is pushed to Trendyol; the package becomes "invoiced".
4. The shipping label is printed with the barcode Trendyol supplied. When the carrier scans it, the status moves to "shipped" on its own.
5. On delivery the package shows "delivered"; the payout period is calculated from that date.
6. If the item is unavailable, the package is closed as "unsupplied". This is the most expensive state for your seller score.

The only way to never reach step six is accurate stock. Selling on another channel a unit that Trendyol has already sold is the leading cause of "unsupplied" flags. We cover this in detail in stock synchronisation and double selling.

Product cards, variants and category attributes

Creating products is where most sellers lose the most time on Trendyol. Variants of a product (sizes, colours) are grouped under a shared model code; each variant has its own barcode. Choosing a category pulls in that category's mandatory attributes: colour, size and gender in apparel; warranty and origin fields in electronics, for example. Products submitted with missing attributes get stuck in approval or never go live.

The integration does two jobs here. First, it translates the product data in your master catalogue (ikas, Ticimax, T-Soft, İdeasoft, Shopify, WooCommerce or an XML feed) into Trendyol's category tree and attribute lists. Second, it polls the result of each batch submission and surfaces the reason for every rejected row. Bulutegra's quality tab exists for exactly this: missing colours, short titles and empty categories are gathered into one list and fixed with one click. Brand approval is the one step no integration can shortcut; if your brand is not registered on Trendyol, you open a brand request in the Seller Panel first.

On the mapping side the golden rule is simple: bind your own SKU to the Trendyol barcode one-to-one. The step-by-step method is in matching products by SKU and barcode.

Stock, pricing and the BuyBox

Trendyol has two price fields: list price and sale price. Customers see the discount as the gap between them. Stock and price updates are sent as batches; Trendyol processes each batch in turn and returns the outcome through a separate query. "Sent" and "live" are not the same thing, so the integration must follow up on the batch result and show you the rejected rows.

The BuyBox decides which seller of a shared barcode gets the "add to basket" button. Price is not the only factor; delivery performance and seller score count too. Bulutegra's repricing module produces a BuyBox suggestion for Trendyol: a sale price that stays above your floor and protects margin, with the decision left to you. The price matrix shows list, sale and floor price per channel in one grid, so your Trendyol price never drifts away from your own store or other marketplaces. More on this in price sync, repricing and BuyBox.

During campaign seasons Trendyol invites sellers into specific promotions; coupons, flash discounts and basket campaigns each follow their own rules. Running the campaign price through a calculator that accounts for commission, VAT and return risk before you commit avoids the classic "we sold a lot and kept nothing" outcome.

Q&A, returns and payouts

Customer questions on Trendyol expect an answer within a set window; replies pass marketplace review before publishing. Questions forgotten in a separate screen hurt both your response-time score and your sales, which is why pulling them into the same inbox as orders and messages pays off.

Returns are initiated on Trendyol's side. The customer opens a request, the parcel comes back to you, and you inspect it in the warehouse and approve or reject with a reason. When a return is approved, the commission should be refunded and netted against your payout — a frequent leak. Payouts themselves are periodic; each statement lists commission, shipping charges and return deductions line by line. Missing payouts, returns whose commission was never refunded, and orders that net to a negative figure are the three items sellers hunt for every month. Rather than finding them by hand, they can be caught by automatic matching as described in payout and commission reconciliation.

How it works with Bulutegra

Bulutegra connects to Trendyol over the Trendyol API and setup runs in four steps. First you connect: seller details go in and products are read, which takes about half a day. Then you match: SKUs and barcodes are bound one-to-one, typically one to three days. Next comes the watch phase: in shadow mode the system only reads for one to two weeks and writes nothing, so you see orders and stock movements side by side with your current routine. Finally you hand over write access channel by channel. The approach was proven in the founding company's own multi-channel retail operation before it was offered to anyone else.

After handover, Trendyol orders are written automatically into Nebim V3, Logo, Mikro or SAP; invoicing and shipping continue in your own routine. Channel monitoring runs continuously; if Trendyol goes quiet, an alert reaches your phone. We explain why the shadow phase matters in shadow-mode integration testing, and you can see every supported channel in the channels section.

To connect your Trendyol store to your own systems, request a demo and our team will map out a setup plan around your current operation.