Nebim V3 Hepsiburada Integration
For businesses running Nebim V3 and selling on Hepsiburada: orders are written into Nebim V3 along with the packaging step, and stock and prices flow from Nebim V3 out to Hepsiburada. Nothing is written until you have seen the numbers agree.
What is the Nebim V3 Hepsiburada integration?
The Nebim V3 Hepsiburada integration carries stock and prices held in Nebim out to Hepsiburada, and Hepsiburada orders back into Nebim. What decides this pairing is Hepsiburada's own catalogue structure: a listing binds to your product through the catalogue, and stock and price updates go out by merchant SKU. The first job is to build that link with the SKU and barcode held in Nebim.
The second difference is packaging. On Hepsiburada an order does not move on until the packaging step is complete, and partial packaging and split lines are tracked separately. Packaging is completed in the panel, the order is written into Nebim V3, and once dispatch is marked the Hepsiburada side is updated. The parcel travels with HepsiJet or a contracted carrier, and carrier and tracking number arrive with the order.
If Nebim holds several stores and warehouses, you decide which stock is exposed to Hepsiburada; you do not have to expose all of it. Listing status — live, awaiting approval or closed — is visible in the panel, and missing attribute, image and category findings are collected in the quality tab.
What flows in which direction
Orders and packages from Hepsiburada into Nebim V3
A Hepsiburada order arrives with its line items, customer details and delivery address; the packaging step is completed in the panel and the order is written into Nebim V3. Partial packaging and split lines are tracked separately, and invoicing and shipping continue in your own routine inside Nebim.
Stock from Nebim V3 out to Hepsiburada
Stock in Nebim is the source of a single pool, and Hepsiburada listings are updated by merchant SKU. You decide during setup which store and warehouse stock is exposed to the channel; when a sale happens at one of those locations, the quantity on Hepsiburada drops without waiting.
Prices from Nebim V3 out to Hepsiburada
Pricing starts from the list price in Nebim; a separate selling and floor price is defined for Hepsiburada, and the floor-price rule prevents selling at a loss. The commission model, VAT and return risk appear on the profitability page as contribution per channel.
Returns and settlements from Hepsiburada into Nebim V3
Return requests appear attached to the order record; goods reaching the warehouse are received by barcode, an exchange order can be opened, and the result is reflected into Nebim. Settlement records are matched to orders, and returns whose commission is not refunded are flagged separately in reconciliation.
How the Nebim V3 Hepsiburada integration is set up
Connect
The access needed on the Nebim V3 side is prepared with your Nebim consultant. You then enter the merchant ID and the API user credentials defined for integration in the Hepsiburada seller panel. You test the connection from the same screen.
Match
Your Hepsiburada listings bind to products in Nebim through merchant SKU and barcode. You link colour and size variants in bulk from a matrix view and fix items with missing barcodes from the quality tab.
Watch
In shadow mode nothing is written: the system only reads Nebim and Hepsiburada. You confirm that orders, package states and listing statuses are read correctly by comparing them against your Nebim screens.
Hand over
Write access opens in sequence: orders and packaging first, then stock, and prices last. The ownership flag decides which product Bulutegra manages on Hepsiburada, and every step is reversible.
Technical summary
| Systems connected | Nebim V3 and Hepsiburada |
|---|---|
| Order direction | From Hepsiburada into Nebim V3, with the packaging step completed in the panel |
| Stock and price direction | From Nebim V3 out to Hepsiburada |
| Matching key | Merchant SKU and barcode; variants bind at colour and size level |
| Shipping | HepsiJet or a contracted carrier; carrier and tracking number arrive with the order |
| Update timing | The moment a sale happens on Hepsiburada; no fixed polling hour |
| Warehouse selection | You decide during setup which store and warehouse stock is exposed to the channel |
| On the Nebim V3 side | Access prepared with your Nebim consultant; no extra module on the Hepsiburada side |
| Invoicing and shipping | Continue exactly as they do today inside Nebim |
| Onboarding | Starts in shadow mode; access opens for orders and packaging, then stock, then prices |
Frequently asked questions about the Nebim V3 Hepsiburada integration
How do my Nebim products match the Hepsiburada catalogue?
A listing binds to your product through the Hepsiburada catalogue, and matching is built on the SKU and barcode held in Nebim at colour and size variant level. Stock and price updates then go out by merchant SKU. Anything that does not seat is listed rather than guessed at.
Does the packaging step change how I work inside Nebim?
No. Packaging is completed in the panel and the order is written into Nebim V3; invoicing and shipping carry on in the Nebim screens your team knows. Once dispatch is marked, the Hepsiburada side is updated.
If Nebim holds several warehouses, which one is exposed to Hepsiburada?
You decide during setup which store and warehouse stock is exposed to the channel. You do not have to expose all of it, and you can expose only a defined portion of shop stock.
How quickly is a Hepsiburada order written into Nebim?
The order is picked up the moment it lands on the channel and written once packaging is done, with no waiting. There is no fixed polling hour.
Can I see listings that are closed or awaiting approval?
Yes. Which listing is live, which is awaiting approval and which is closed is visible in the panel, and missing attribute, image and category findings are collected in the quality tab.
Can I run Hepsiburada and Trendyol through the same Nebim?
Yes. Both channels share the same stock pool held in Nebim, so a unit sold on one drops on the other without waiting. Use the price matrix for channel-specific prices, and open channels one at a time, taking each over separately.