Nebim V3 Marketplace Integration: Orders Into Your ERP
Nebim V3 marketplace integration: stock flows from the ERP to Trendyol, Amazon and other channels, orders are written back with customer and line data.
For a business running Nebim V3, a widely used retail ERP in Türkiye, marketplace integration answers two questions: how does a Trendyol order get into Nebim, and how does Nebim stock get to Trendyol? The answer is a two-way flow. Stock and product identity are read from the ERP and written to the marketplaces; orders are read from the marketplaces and written to Nebim as order records with the customer, line items, carrier and payment details. Invoicing and shipping continue in the business's own process.
Why the ERP is the centre
At small scale, typing marketplace orders into the ERP by hand is possible. Ten orders a day take an hour. A hundred orders a day take one person's whole shift, and mistakes become unavoidable: wrong customer, missing line, skipped order. As manual entry grows, stock drifts too; the quantity in the ERP and the quantity on the marketplace move apart.
In businesses on Nebim V3, accounting, warehouse, stores and purchasing already run through the ERP. Leaving the marketplace channel outside that system means running the company on two versions of reality. Integration turns the marketplace into one more sales channel of the ERP: wherever an order comes from, it is written to the same place.
Bulutegra connects Nebim V3, Logo, Mikro and SAP as ERPs. The ERP is the source for product identity and stock, and the destination for orders. Catalog content, meaning titles, descriptions and images, can come from a separate source such as ikas, Ticimax, T-Soft, İdeasoft or an XML feed. For the fundamentals, see what marketplace integration is.
Stock code and barcode mapping
The first and most important step of any ERP integration is mapping. Every product variant in Nebim has a stock code and a barcode; every marketplace listing has its own seller stock code and barcode. Until these two worlds are linked, no stock is written and no order lands.
The logic looks simple, but three problems show up in practice:
- Variants without barcodes: an item with an empty barcode in the ERP does not match anything on the marketplace.
- Different coding conventions: the marketplace may hold "ABC-001-S" while the ERP holds "ABC001S". A mapping rule solves this, but someone has to notice it first.
- Duplicate barcodes: if the same barcode was given to two variants, stock is written to the wrong product.
Matching takes one to three days. Most of that time is spent not in the system but on cleaning codes and barcodes in the ERP. A clean ERP means a short setup.
The panel lists unmatched products separately; for each row you choose "link to this listing", "create as new product" or "skip". The method is covered in matching products by SKU and barcode.
Stock flow: from the ERP to the channels
Once mapping is done, stock starts flowing. The panel reads the sellable quantity from Nebim and writes it to every channel as one stock pool. A sale on any channel reduces the pool and updates the others. A goods receipt in the ERP raises the pool and updates the channels again.
If there are several warehouses, you decide during setup which ones feed the pool; the panel reads only the warehouses you select. The multi-warehouse logic is explained in multi-warehouse stock management.
Order flow: from the channel to the ERP
When a marketplace order reaches the panel, it is written to Nebim with the following:
- Customer: a customer account is created from the buyer's name, address and contact details, or the order is attached to an existing account.
- Line items: every order line is written with its mapped ERP stock code, quantity and price.
- Carrier: the carrier assigned by the marketplace, or the one you selected, is stored on the order.
- Payment details: the type and amount of the payment made through the marketplace are recorded on the order.
From this point the process continues in the business's own routine. When, in which series and by which method you issue the invoice depends on your Nebim practice. The same goes for shipping, picking and carrier labels. The integration delivers the order to the right place with the right data and stops there. For the invoicing side, see marketplace e-invoice integration.
Cancellations and returns follow the same path. An order cancelled on the marketplace is flagged in the panel; a return is accepted in the warehouse by barcode and the stock goes back into the pool. The customer return portal works with an e-mail address and order code.
Settlements deserve attention too. Differences between what the marketplace paid and the order amount in the ERP are listed on the settlement and reconciliation screen: missing payouts, returns where commission was not refunded, orders that went negative. Each record carries a status, a ticket and notes, and the Accounting role tracks the list.
Setup: four steps
Bulutegra setup follows the same four steps for Nebim V3:
- Connect (half a day): the Nebim V3 connection and marketplace accounts are registered in the panel.
- Match (1–3 days): products are matched to marketplace listings by stock code and barcode.
- Watch (1–2 weeks): shadow mode. The system reads the ERP and the channels, reports stock differences and order flow, and writes nowhere.
- Hand over: write access is enabled channel by channel. The ownership flag lets you leave a channel with an external system.
Shadow mode is especially valuable in ERP integration. A wrongly mapped stock code with live writes on drops a bad order record into the ERP, and reversing it is extra work for accounting. In shadow mode the same error is a report line: you fix it, then go live. Read more in shadow mode integration testing.
Pre-setup checklist
- Does every sellable variant in Nebim have a filled, unique barcode?
- Can the stock code convention be mapped to the seller stock codes on the marketplaces?
- Which warehouses will form the sellable stock?
- How will customer accounts be created for marketplace buyers: one per customer, or one per channel?
- Have the invoicing moment and series been agreed with the accounting team?
- Who works with which role? Admin, Content, Warehouse, Returns, Accounting and Reporting roles have separate permissions.
- Will two-factor authentication be switched on?
The customer account question is usually the longest discussion of the setup; decide it with the accounting team, once.
How it works with Bulutegra
Bulutegra connects Nebim V3 as the ERP and manages more than 24 marketplaces from one Integration Panel. Trendyol, Hepsiburada, Amazon, N11, Çiçeksepeti, Pazarama, PttAVM, Modanisa, Flo and İdefix, together with Amazon global, eBay, Etsy, Walmart, Ozon, Temu, SHEIN and Jumia, draw from the same stock pool. Orders are written to Nebim automatically with customer, line items, carrier and payment details; invoicing and shipping continue in your own process. Channels are checked continuously and a silent channel sends a push notification to your phone. The software was born in the founding company's own multichannel retail operation, where the order-to-ERP flow ran first.
To see how it connects to your Nebim V3 setup, fill in the demo form or review ERP and platform options under Solutions.
Frequently asked questions
How does Nebim V3 connect to Trendyol and other marketplaces?
Products in Nebim V3 are matched to marketplace listings by stock code and barcode; stock is read from Nebim and written to each channel. When a Trendyol or Amazon order arrives, it is recorded in Nebim as an order with the customer, line items, carrier and payment details. Invoicing and shipping continue in your existing Nebim process.
Does a marketplace order land in Nebim as an invoice?
No, it lands as an order. The integration writes the order with its customer and line items; when and how the invoice is issued depends on your accounting process. Your e-invoice, e-archive or batch invoicing habits stay as they are.
If Nebim has several warehouses, which stock goes to the marketplaces?
During setup you decide which warehouse or warehouses form the sellable stock. The panel reads the quantity from those warehouses and writes it to the channels as one stock pool. Store stock, damaged goods or reserved areas can be left out of the pool; the decision is yours.
