Trendyol, Hepsiburada, and N11 Integration
A step-by-step guide to connecting Trendyol, Hepsiburada, and N11 in one panel, mapping products to categories, syncing stock and price, and pulling in marketplace orders.
For a store owner selling on Trendyol, Hepsiburada, and N11 at the same time, the biggest risk is that stock and price data drift out of sync while each marketplace is tracked separately. A properly set up integration lets you manage four things from one panel: connecting the channel, mapping products to categories, pushing stock and price automatically, and pulling orders back in. This article walks through those four steps in order, showing exactly which screen handles what.
What should you prepare before connecting a marketplace channel?
Each marketplace gives you an API key / store ID through its own seller panel. Pull these credentials from the Trendyol, Hepsiburada, and N11 seller centers ahead of time — the integration screen will ask for them. It also helps a lot to have your products' SKUs and barcodes (where they exist) filled in completely before you start, since that seriously speeds up the mapping step — a product without a barcode usually needs an extra manual step to map on the marketplace side.
Once the connection is set up, the channel is listed side by side with your store's other sales channels (your own storefront, B2B, a multi-vendor marketplace if you run one); you can deactivate, manage, or remove each channel independently. Connecting a channel doesn't automatically publish it — the connection only opens the communication channel; you decide which products go live and when.
Why manage all three marketplaces from one panel?
Each marketplace has its own seller panel, and it's entirely possible to open all three separately and track them that way — but that approach carries two concrete costs. The first is time: updating the same product's stock across three separate screens stops being sustainable as your store grows. The second is a consistency risk: if you update the price on one screen and forget the others, the same product ends up selling at different prices on different marketplaces, which usually comes back as a customer complaint or a competitiveness penalty on the marketplace side. Managing everything from one panel removes both risks by updating the source data — stock, price, product information — once and pushing it out to every channel at the same time.
How does product mapping work?
Before you can sell a product on a marketplace, you have to map it to that marketplace's category tree — this step can't be skipped, because the marketplace won't publish a product without knowing which category it belongs to. The process works like this:
- You use "Sync categories" to pull the marketplace's current category list.
- You select your product and map it to the marketplace category.
- Once mapped, you publish the product with a single click.
If you try to publish a product before it's mapped, the panel blocks the action and opens the mapping screen directly — so the risk of a product slipping into the wrong category by accident is closed off from the start.
How does category mapping enable bulk publishing?
Mapping products one at a time doesn't scale for a store with hundreds of SKUs. Instead, you map your store category (say, "Women's Shoes") to the corresponding marketplace category once; after that mapping is saved, you can send every active product in that category to the marketplace in a single "Bulk send" action. The panel shows, with badges tied to that mapping, how many products are live, how many are still processing, and how many have a problem (rejected/errored) — so after a bulk send you can see at a glance which products still need manual attention.
How do you push stock and price to a marketplace?
Once a product is live, the real ongoing work is keeping stock and price current — a product that's out of stock but still shows as available on the marketplace leads to both customer complaints and a penalty score on the marketplace side. From the panel, each product row has a "Send stock and price" option that pushes the current stock and price to the relevant marketplace with a single click; the send is tracked with a batch code, so you can confirm whether the marketplace has actually processed it.
You don't have to enter stock manually per channel — a single inventory record in your store can push the same stock figure out to every connected marketplace. That's the single most important habit for avoiding a sync gap like "Trendyol shows 5 left, but there are actually 0."
How often you need to trigger a stock/price push depends on how fast your products move: on a fast-selling product, a delayed push means a product that's actually sold out still shows as available on the marketplace, which leads to cancelled orders. For your high-velocity products, it's worth turning the push into a regular habit, and always re-triggering it after any one-off large stock movement, such as a bulk purchase or a post-count correction.
How do you pull orders in from a marketplace?
An order placed on a marketplace doesn't land in your panel automatically — you use "Pull orders" to import new orders from that marketplace. Imported orders show up in the same order list as orders from your own storefront — meaning you print shipping labels, update statuses, and process returns from a single order screen, without needing to log into the marketplace's own panel at all.
What do the listing statuses mean?
| Status | Meaning |
|---|---|
| Live | The product is on sale on the marketplace |
| Processing | The submission hasn't been processed by the marketplace yet |
| Problem | The marketplace rejected the product or returned an error — usually missing/incorrect category information, a brand mismatch, or a missing required field |
| Draft | The product is mapped but hasn't been published yet |
If a product drops into "Problem" status, check the category mapping and required fields (brand, GTIN/barcode, and so on) first — most rejections come from one of those two.
Frequently asked questions about managing Trendyol, Hepsiburada, and N11 from one panel
Can I send the same product to all three marketplaces at once? Yes — the product is mapped and published separately on each channel, but you trigger the stock/price update from a single inventory record. Channels work independently of each other; deactivating a product on one doesn't affect the others.
If I pause a marketplace temporarily, are my products deleted? No. Deactivating a channel doesn't delete live products or past orders — it just stops new submissions and syncing. When you reactivate the channel, it picks up where it left off.
Can a product be published without category mapping? No. Marketplaces won't accept a product without category information; the panel doesn't let you skip this step and routes you directly to the mapping screen.
An order shows up on the marketplace but not in the panel — what should I do? Trigger "Pull orders" manually. Even if the order already exists on the marketplace's side, the import step has to run for it to land in your panel.
How do I send a product that doesn't have a barcode? Some marketplaces require the GTIN/barcode field, while others make an exception for unbranded or barcode-less products. If your product has no barcode, check the relevant marketplace's policy on barcode-less products first; in most cases, a missing barcode is the most common reason a product drops into "Problem" status.
I changed the price on one marketplace — does it automatically apply to the others? No — each channel keeps its own listing record. You need to update the source price (the actual product price in your store) and trigger the stock/price push separately for each connected channel; that's exactly why working from a single source of data needs to be a disciplined habit.
What to watch for in the first week
For a newly connected marketplace, the first-week checklist looks like this:
- Check your category mapping — a product that lands in the wrong category either gets rejected or shows up in the wrong search results.
- Review products that drop into "Problem" status after the first submission one by one; it's usually the same handful of missing fields — brand, barcode, a required attribute — repeating.
- Manually confirm the stock/price push at least once a day, to make sure the automatic sync is behaving as expected.
- After importing your first orders with "Pull orders," confirm that the shipping/label flow works the same way it does for orders from your own storefront.
Where do you start in Daras?
In Daras, you connect a marketplace channel from the Channels page; product mapping, category mapping, and stock/price pushing are handled from the Marketplace channels page. Since the whole flow works without writing code — selecting and mapping categories, then publishing in bulk with one click — you can finish the initial setup in a single session.
Related posts
Setting Up a Multi-Vendor Marketplace
Explains how vendor approval, commission structure, order splitting, and vendor payouts work together so store owners can set up a multi-vendor marketplace correctly.
Marketplace Commission and Net Profit Calculation
Shows how to calculate true net profit after marketplace commission, shipping, and VAT, and lists the hidden deductions sellers most often forget when pricing.
Try it in your trial store, go live when you are ready.
The migration team moves your products, customers, orders and theme; a 301 redirect map keeps your SEO intact.