N11 Integration: Order Acceptance, Stock Codes and Shipping

An N11 integration connects the product, order, shipping, return and payout work in the N11 store panel to your own e-commerce platform and ERP over the N11 API. An order is accepted and written to the ERP when it lands, a stock change updates N11, and payout lines are matched to orders. What most distinguishes N11 from other Turkish marketplaces is that every order must be explicitly accepted by the seller, and product identity rests on a merchant stock code that you define. For sellers entering the Turkish market, N11 is often the third or fourth channel after Trendyol and Hepsiburada, and it rewards a disciplined setup. This guide explains how N11 works and how an integration adapts to it.

The merchant stock code: product identity on N11

On N11, the identity of a product and its variants is the merchant stock code you assign. Barcodes matter, but orders, stock and price updates all run on the stock code. This differs from Trendyol and Amazon, which anchor identity on the barcode or their own catalogue number: on N11 the control is yours, and so is the responsibility.

That is exactly where problems begin. Products created by hand over the years develop inconsistent codes: the same item under two codes, two variants under one, or a code with a trailing space. When the integration first connects, it puts those inconsistencies in front of you; the matching step on N11 usually takes longer than on other marketplaces because cleanup is required. Enabling write access before your own SKU and the N11 stock code are bound one-to-one ends with stock written to the wrong item. The method is covered in matching products by SKU and barcode.

Variants on N11 are defined as stock attributes: options such as size and colour sit under the product, each with its own stock code and quantity. The category tree brings its own mandatory attributes, and a missing one stalls the product in review. New products and major edits are reviewed by N11's catalogue team; approval time varies by category. Stock and price for a product awaiting approval can still be updated while the review runs.

The acceptance step and status flow

When an N11 order arrives it is in the "new" state and waits for the seller to accept it. An order not accepted within the defined window is cancelled automatically and recorded against your store rating. Acceptance is per line: you can accept two of three lines and reject one for lack of stock. In practice the flow runs like this:

1. The order lands as "new". The integration checks each line against stock.
2. Lines with stock are accepted; lines without are rejected with a reason. This can be automatic or gated by warehouse confirmation.
3. The accepted order is written to the ERP with customer, lines, carrier and payment details.
4. The warehouse picks, the invoice is issued, the shipping label is printed.
5. The tracking number is reported to N11; the order becomes "shipped".
6. On delivery it shows "delivered" and the payout period begins.

Taking the shortcut of "accept everything automatically" is tempting, but if stock is wrong you will cancel an order you already accepted — and that hurts the rating more than not accepting at all. Tying acceptance to stock is the single most important rule of an N11 integration.

This flow has to sit in the same list as orders from Trendyol, Hepsiburada and your own store; choosing the N11 tab should bring orders awaiting acceptance to the top. Single-list order handling is covered in multi-channel order management.

Shipping model: contracted carrier or your own

Shipping on N11 goes one of two ways. The first is N11's contracted-carrier model: the option is ticked on the product card, the shipping charge follows N11's tariff, and the label is printed with details N11 supplies. The second is your own shipping: you send with your own contracted carrier and enter the tracking number on N11. The choice is made per product; some sellers use the contracted model for light items and their own carrier for bulky ones.

The integration separates the two models according to the preference on the product card. Under the contracted model, label details are read from N11; under your own model, the integration talks to the carrier, obtains the tracking number and writes it back to N11. How carrier integrations work is in carrier integration: Aras, Yurtiçi, MNG, PTT. Shipping charges, delivery windows and free-shipping thresholds change; check your N11 seller agreement for the current tariff.

Pricing, discounts and campaign logic

N11 keeps the product price and the discounted price as separate fields; the customer sees the gap as a discount. On top of that, N11 may fund extra discounts and coupons itself, in which case what the customer pays and what you receive diverge. Part of the "customer paid this, I received that" gap in reconciliation comes from this campaign structure.

The price matrix places your N11 list, sale and floor price next to every other channel. When joining a campaign, the campaign calculator shows what remains after commission, VAT and return risk. Stock pressure during campaign periods is covered in stock and price management during campaign seasons. Store rating affects visibility on N11; cancellation rate, dispatch time and customer reviews all feed into it.

Q&A, returns and payouts

Questions on the product page land with the seller and wait for a reply; an unanswered question is a lost sale. Bulutegra's CRM module gathers N11 questions, other marketplace questions, WhatsApp Business API messages and email in one inbox; a user in the content role sees only that inbox.

Returns are initiated by the customer on N11; the item comes back to you, you inspect it in the warehouse and approve or reject with a reason. On an approved return the amount and commission are deducted from your payout. Lines rejected at the acceptance step are recorded as cancellations, not returns; keeping the two apart makes reconciliation easier.

Payouts are periodic; sales, commission, shipping and return deductions arrive as separate lines. Bulutegra's payout and reconciliation tracking matches those lines to orders; anything unmatched is tracked as a missing payout, a return without commission credit or a negative-net order, with status, ticket and note fields. A user in the accounting role closes the month from this screen without logging into the N11 panel.

How it works with Bulutegra

Bulutegra connects to N11 over the N11 API and setup follows four steps: Connect (store details entered, products and stock codes read; half a day), Match (N11 stock code and barcode bound one-to-one to your SKU, inconsistent codes cleaned; one to three days), Watch (shadow mode: the system only reads for one to two weeks while you compare orders awaiting acceptance and stock movements with your current routine), and Hand over (write access for acceptance, stock, price and shipment confirmation). Binding acceptance to stock was tested on N11 in the founding company's own retail operation, where the software was used first.

After handover, N11 orders are written automatically to Nebim V3, Logo, Mikro or SAP; invoicing and shipping continue in your own routine. The critical-stock alert prevents an unacceptable N11 order before it is placed, and the ownership flag shows per product whether Bulutegra manages the N11 side. Every module is listed in the solutions section.

To connect your N11 store to your own systems, request a demo and we will build the setup plan with you, stock-code cleanup included.