Marketplaces integration
N11
What it does
- Pushes products to N11 over its REST API after strict category and attribute validation.
- Syncs stock and price both ways from Kambloo's single stock pool.
- Pulls N11 orders into your normal order flow with the N11 channel tag.
Provider based in Turkey
N11 is part of Kambloo's marketplace catalog. It uses N11's REST API; the older SOAP service is no longer available and is not part of the design. The connector implements the shared MarketplaceConnector contract and is an Internal Module. N11's seller commission is charged by N11.
How it works with Kambloo
The notable feature of N11 is strict category attribute enforcement. A product with a missing or invalid attribute is rejected at the marketplace. Kambloo moves that check forward. The mapping screen loads N11's category tree, cached for 24 hours, and the required attributes for each mapped category. Your product and variant fields are mapped to those attributes, and a validation pass runs before any push. Missing required values are shown as a list next to the product. Only fully mapped products enter the push batch, and each listing records N11's approval or rejection with the reason.
Stock and price sync follows the platform model. Kambloo is the default source, and delta jobs send only rows that changed since the last watermark. Requests carry idempotency keys and are rate-limited per provider. A price set on N11's side, such as a campaign price, is stored on the listing and does not overwrite your product. A price rule per listing or category compensates for commission with a percentage, a fixed amount, and a rounding strategy.
All channels draw from one stock pool. A reservation on the storefront or another marketplace reduces sellable stock, and the new quantity is pushed to N11 on a high-priority queue. A per-channel buffer is available if you prefer to under-report.
Orders are pulled on a schedule and enter Kambloo with the N11 channel tag. They then follow the same steps as any other order: stock reservation, carrier label, invoice through your e-document integrator, and customer notification. The tracking number is written back to N11.
Requirements
- An N11 seller account with REST API credentials.
- Complete attribute mapping per category; N11 rejects incomplete products.
- A price rule that reflects your N11 commission.
Setup steps
The short version. The screens in your store admin follow the same order.
- Install the N11 module from the Market. It is free.
- Enter your N11 API credentials under Settings > Marketplaces > N11.
- Map categories and complete every required attribute for each N11 category.
- Set a price rule and buffer stock, then list products.
- Enable order pull once listings are approved.
Questions about N11
Why does N11 reject products that Trendyol accepts?
N11 enforces category attribute requirements strictly. Kambloo validates the mapped attributes before pushing and lists what is missing, so you fix it before N11 sees the product.
Does the connector use N11's SOAP API?
No. N11 retired the old SOAP API. The connector is built on the REST API.
Does N11 use the same screens as Trendyol?
Yes. The mapping screen, price rule, stock pool, and order pipeline are shared by every marketplace connector. Only the API layer and the attribute validation differ.