Skip to content
Besh Bilişim Technology Services
bilgi@beshbilisim.com
İsmet Kaptan, 1372 Sk. No:15, İzmir
Besh Bilişim Besh Bilişim Besh Bilişim
  • Home
  • Services
    • Izmir Software and Web Services

      Izmir-based Besh Bilişim: website design, custom software, mobile apps, e-commerce and automation services under one roof.

    • Website Design

      We design fast, secure, mobile-friendly and SEO-ready corporate websites so your brand looks professional on every screen.

    • Besh CMS

      Manage your pages, blog and media from a single panel with minimal coding knowledge and update your site whenever you like.

    • Mobile Applications

      We build fast, user-focused mobile apps for both iOS and Android from a single React Native codebase. Get a quote for your mobile project.

    • Automation Software

      We build software that automates processes such as invoicing, delivery notes and stock tracking, and saves you time.

    • Accounting Software

      Track and manage invoices, accounts, stock, cash and bank transactions easily from a single program. Explore Besh Bilişim accounting software.

    • E-Commerce

      Sell your products online and track orders in one place; we build tailor-made, SEO-friendly e-commerce platforms.

    • SEO Services

      We help your website become more visible on Google and win more visitors and potential customers. Get in touch for our SEO services.

    • Web Software

      We build fast, scalable corporate web applications and portals with Next.js, React, TypeScript and .NET. Get a quote for your project.

    • Support and Maintenance

      Installation, training, maintenance and 24/7 technical support keep your systems running without interruption.

    • Custom Software Development

      Where off-the-shelf programs fall short, we build custom software designed around your business. Tell us what you need and get a quote.

  • Designs
  • Blog
  • About
  • Contact
EN
EN
Contact Us
November 19, 2026 Besh Bilişim Web Development

Marketplace Integration: Managing Trendyol, Hepsiburada and n11 from One Stock Pool

Short answer: to run three marketplaces, decide who owns the stock and send each channel only what you can actually sell

If you sell the same product on Trendyol, Hepsiburada and n11, the most common problem is this: the last unit of a product sells on two channels at once, one order gets cancelled, and your seller score and customer trust take the hit. The fix is not three separate stock counts. It is one stock pool, with each marketplace receiving a "sellable" figure derived from it. This article covers how to think about that pool, what to watch for in the three marketplaces' official documentation, and what to ask an integration vendor or your development team.

We listed the general mistakes in our 8 common ERP and e-commerce integration mistakes; here we stay on what is specific to marketplaces. Marketplace rules and limits change: the details below come from official documentation read in November 2026, so check the current documents before you build.

How to build a single stock pool

In most businesses the pool's owner is the ERP (or a single stock system if there is no ERP). The marketplaces and your own online store are channels that read from the pool. The calculation we suggest:

Concept Meaning
Physical stock The quantity you can count in the warehouse
Reserved Ordered but not yet shipped
Safety buffer A cushion set aside per channel (for example higher on fast sellers)
Sellable stock Physical − reserved − safety buffer. This is what you send to the marketplace

The buffer is insurance against the lag in a channel's stock figure. How many units it should be depends on the product's sales speed and how often the integration runs, so we cannot give a general number. You also do not have to send the same quantity to all three marketplaces: some companies hold a larger share for the channel that earns more. That is a business decision; software can only apply it.

With several warehouses, which warehouse feeds which channel should also be written down; we covered that in our wholesaler ERP article.

Stock and price updates: the Trendyol example

Trendyol's official stock and price update document spells out the rules you need to know when writing an integration:

  • A single request can update at most 1,000 products (SKUs).
  • If you resend the same request without changing the body, you get an error: "You cannot send the same request repeatedly for 15 minutes!" The document tells you to send only the stock and prices that changed.
  • The quantity field is the sellable stock; according to the document it is updated when an order is received or when you send stock again. In other words, Trendyol decrements stock on its side when an order arrives. If the figure your ERP sends does not account for the orders that arrived in between, it can overwrite Trendyol's correct number with a stale one.
  • At most 20 thousand units of stock can be added for a product.
  • The operation does not complete instantly: the request returns a batchRequestId, and you must check the outcome with getBatchRequestResult.

On the service limits page, product services are split into limit groups for the period after 14 September 2026; the stock and price update services share an "Inventory & Price Write" group, and the limit ranges from 350 to 2,000 requests per minute depending on the seller's tier (ask Trendyol which tier names in the table apply to you). Because limits can change, your integration should not hard-code these numbers.

In practice:

  • Send in batches. Single requests hit the limit and are slow. Send groups of up to 1,000.
  • Send only what changed. Keep the last value you sent and do not resend unchanged values.
  • Query the result. Store the batchRequestId and add a step that checks the outcome later, so failed rows do not disappear silently.
  • Back off at the limit. Instead of resending the same request immediately, retry at increasing intervals. An integration firm's Trendyol guide gives the same advice.

Pulling orders: packages and statuses

Trendyol delivers orders as "packages". The order package document lists the package statuses (Created, Picking, Invoiced, Shipped, Cancelled, Delivered and others) and says that for orders in Awaiting and Verified status, which are waiting for payment approval, you should take no action until they become Created; you can use those statuses only for stock updates. Sorting by last modification uses the PackageLastModifiedDate field.

What this means on the ERP side:

  • Our recommendation: let an order enter the ERP in Created status, and issue no sales document while payment approval is pending.
  • Even if the same package is pulled twice, the ERP must not create two orders: store the marketplace package number as a unique key. This is the safeguard against the duplicate-order mistake in our 8 mistakes article.
  • Cancellations, partial cancellations and returns should trigger stock going back; otherwise the sellable figure stays artificially low.

Hepsiburada and n11: same idea, different keys

Each marketplace has its own API, so each needs its own connector layer. The way to manage three is to put a shared layer between the ERP and the marketplaces: the ERP side stays single, and adding a marketplace just means writing one more connector. The integration guide mentioned above recommends the same approach.

  • Hepsiburada: its developer portal offers catalog, listing, order and accounting integrations as separate areas. The documentation states that pagination is mandatory when you pull all of a seller's listing information, so the assumption "let's fetch all products in one request" does not hold.
  • n11: the price and stock update service works with a POST request and authenticates with appKey and appSecret headers. In the order listing service, each line carries both the n11 product code (productId) and the seller's own product code (stockCode); variant attributes are in variantAttributes.

The shared rule is a product mapping table: for every ERP product, keep its counterpart on each marketplace (the barcode on Trendyol, stockCode and productId on n11, and Hepsiburada's own listing key) in a separate table. Do not assume one "product code" column will work on all three. This mapping is the least maintained part of most integrations; decide who updates it when a new product is created.

Price rules: one list, a rule per channel

The same product does not have to sell at the same price on every marketplace; commission, shipping and campaign participation vary by channel. Our suggestion: keep one base price in the ERP and define a separate rule per channel (percentage or fixed amount, rounding, VAT included or excluded). When a price goes to Trendyol it travels as two fields, salePrice and listPrice, so your rule must know how to produce each. We do not give commission rates here: they depend on category and agreement, so check the current rate in your own seller panel.

Questions for an integration vendor

  • How does it detect "changed products" for stock updates? Does it send the whole catalog?
  • What does it do when a marketplace limit is exceeded? Does it wait and retry, or skip the update?
  • Does it query the batch result and show you the failed rows?
  • How does it prevent the same order from being pulled twice?
  • How do cancellations and returns flow back into stock?
  • What does adding a new marketplace cost, and how long does it take?
  • When a marketplace API changes, who updates the integration and how fast, and is that in the contract?

Ready-made package or custom integration?

Many ERP and e-commerce packages ship marketplace connectors. If your processes are standard (one warehouse, the same price on every channel, simple variants), a ready-made connector may be enough. With several warehouses, channel-specific price rules, complex variants or a flow specific to your ERP, a custom integration comes into play; we described the decision framework in our off-the-shelf vs custom software decision matrix. To assess your e-commerce setup as a whole, see our 10 questions before changing platform.

Go-live checklist

  • ☐ Change a product's stock in the ERP: how long until it updates on all three marketplaces?
  • ☐ Drop stock to 1 and place an order from two channels at the same time: what happens?
  • ☐ Resend an unchanged stock request: does the integration prevent it?
  • ☐ Send a batch with a deliberate error: does the error reach you?
  • ☐ Cancel an order: does the stock return?
  • ☐ Create a new product: who does the mapping on the three marketplaces, and when?
  • ☐ Simulate a marketplace API outage: does the integration wait and retry?

Frequently asked questions

Should I keep separate stock for each of the three marketplaces?

No. Keep physical stock in one place and send each channel the sellable quantity derived from it; that stops the last unit from selling on two channels. Define only a buffer per channel and, if needed, an upper cap.

How often should stock be updated?

As often as your stock changes, but send only the changed products each time. Trendyol's document treats repeating an identical request within 15 minutes as an error and limits exist, so "the whole catalog every minute" is both unnecessary and risky.

Can marketplace integration be done without an ERP?

Yes; in that case the stock pool lives in an integration tool or your e-commerce panel. If you have an ERP, keeping the pool there is sturdier because invoicing, warehouse and accounting are already there. We described how to move from Excel to an ERP in our 90-day plan.

What happens when a marketplace API changes?

Marketplaces change fields, limits and rules; Trendyol's limits page giving a separate table for the period after 14 September 2026 is one example. Entrust the integration to a team with a maintenance agreement and put in writing who follows change announcements. See our support and maintenance service.

If you want to assess your marketplace and e-commerce integrations together, see our e-commerce service or get in touch.

Sources: Stock and Price Update, updatePriceAndInventory (Trendyol Integration Documentation), Service Limits (Trendyol Integration Documentation), Fetching Order Packages, getShipmentPackages (Trendyol Integration Documentation), Hepsiburada Developer Portal, Product Price and Stock Update (n11 Developer), Order Listing Service (n11 Developer), Trendyol API Integration Guide (MountainTech+)

Cover photo: Bench Accounting / Unsplash

IntegrationMarketplaceHepsiburadaE-CommerceStock SynchronizationTrendyolAPI IntegrationERP Integration
All posts
Latest posts
  • CRM Software Selection: Ready-Made, ERP-Linked or Custom CRM?
    November 19, 2026
  • ERP for Building Materials Wholesalers and Manufacturers: Variants, Price Lists and Dealers
    November 19, 2026
  • Manufacturing ERP: BOM, Work Orders and Stock Costing Features to Look For
    November 19, 2026
  • Moving Dealer Orders Off WhatsApp and Excel: A B2B Portal Transition Roadmap
    November 16, 2026
  • ERP for Wholesalers: Features to Look for in Multi-Warehouse Stock, Due Dates and Accounts
    November 16, 2026
Categories
  • Software Development 16
  • Web Development 9
  • AI and Security 3
  • SEO and Digital Marketing 2
  • E-Commerce 1
Tags
ERPSMEsE-CommerceDealer PortalIntegrationCustom SoftwareTotal Cost of OwnershipB2BSoftware SelectionWholesaleAIChecklistDeveloper ToolsERP IntegrationIzmirKVKKOff-the-Shelf SoftwareAI AgentsAPI IntegrationAstro
Besh Bilişim
  • Fb.
  • Ig.
  • In.

Besh Bilişim - Izmir Office İsmet Kaptan, 1372 Sk. No:15, İzmir

Email

bilgi@beshbilisim.com

Phone

+90 553 443 30 00
Newsletter

© 2026 Created by Besh Bilişim Teknolojileri

BESH

We use cookies to offer you a better experience and to analyze site traffic. Analytics cookies only work with your consent. Cookie and privacy information