Logo, Mikro and SAP ERP Marketplace Integration

For a business running Logo, Mikro or SAP, the job of marketplace integration is clear: product identity and stock are read from the ERP and written to Trendyol, Hepsiburada, Amazon and the other channels, while marketplace orders are written into the ERP as order records with customer, line items, carrier and payment details. Invoicing and shipping continue in the business's own process. This article covers the concepts, setup steps and decision points that are common to all three ERPs.

Three different ERPs, the same four concepts

Logo, Mikro and SAP serve businesses of very different sizes. One keeps the books of a small wholesaler; another runs every process of a multi-branch retailer. For marketplace integration, however, all three share the same four concepts:

• Stock code and barcode: the product's identity in the ERP and the basis of marketplace mapping.
• Customer account: the buyer's record in the ERP.
• Order record: the ERP counterpart of the order with its lines, amount and carrier.
• Warehouse: where sellable stock is read from.

Integration works on these four concepts. Module names and screens differ from ERP to ERP, but the flow is the same: the ERP is source and destination, the marketplace is a channel. Bulutegra connects Logo, Mikro, SAP and Nebim V3 on this basis. For the fundamentals, start with what marketplace integration is.

Who owns which data

The first decision in ERP integration is data ownership. Editing the same information in two places is the main source of inconsistency. The usual arrangement is:

• ERP: stock code, barcode, sellable quantity, cost, customer accounts and order records.
• Catalog source (ikas, Ticimax, T-Soft, İdeasoft, XML feed): title, description, images, category and attribute fields.
• Integration panel: per-channel price rules, campaigns, mapping and the ownership flag.

Some businesses keep catalog content in the ERP as well. It is possible, but the rich content marketplaces want, such as multiple images, long descriptions and category-specific attributes, is awkward to manage in most ERPs. Keeping a separate catalog source is healthier: the ERP owns identity and stock, the catalog source owns content.

Rule: a piece of data is edited in one place only. Write ownership down at the start; most "why is stock different" arguments come from breaking this rule.

Stock code and barcode mapping

Mapping is the longest step of the setup. The stock code and barcode of every sellable variant in the ERP are matched to the seller stock code and barcode of the marketplace listing. Three problems are common in practice:

1. Variants with empty barcodes. They do not match.
2. Different code spelling in the ERP and on the marketplace: hyphens, spaces, upper and lower case. A mapping rule solves it, but it has to be noticed first.
3. Duplicate barcodes. Stock is written to the wrong product; this is the most dangerous case.

The panel lists unmatched products separately; for each row you decide "link", "create new" or "skip". The method is detailed in matching products by SKU and barcode. After mapping, stock starts flowing: the quantity read from the ERP is written to the channels as one stock pool, falls with every sale and rises with every goods receipt.

If there are several warehouses, you decide during setup which ones feed the pool. The decision depends on business preference, not on the ERP's internals: central warehouse only, or branches too? See multi-warehouse stock management.

How an order is written into the ERP

When a marketplace order reaches the panel, these steps run automatically:

1. Customer account: an account is created from the buyer's name, address and contact details, or the order is attached to an existing one. Some businesses use a single account per channel; that is the accounting team's call.
2. Order record: each line is written as an order line with its mapped stock code, quantity and price.
3. Carrier: the carrier assigned by the marketplace, or chosen by you, is stored on the order.
4. Payment details: the type and amount of the payment made through the marketplace are recorded.

From here on it is the business's own routine. When, in which series and by which method the invoice is issued, and how shipping is planned, depend on your ERP practice. The integration does not interfere. 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 stock goes back into the pool. On the settlement and reconciliation screen, the amount the marketplace paid is compared with the order amount; missing payouts, returns without a commission refund and orders that went negative are listed separately, each with a status, a ticket and notes.

Setup steps and shadow mode

Bulutegra setup follows the same four steps for all three ERPs:

1. Connect (half a day): the ERP connection and marketplace accounts are registered in the panel.
2. Match (1–3 days): products are matched to channels by stock code and barcode.
3. Watch (1–2 weeks): shadow mode. The system reads the ERP and the channels, reports differences and writes nowhere.
4. Hand over: write access is enabled channel by channel, with your approval.

Shadow mode is particularly important with an ERP. A wrongly mapped stock code with live writes on drops a bad order record into the ERP, and accounting has to reverse it. In shadow mode the same error is a report line. Why this step should never be skipped is explained in shadow mode integration testing.

The ownership flag is used at hand-over. At product × channel level, the setting "is the integration managing this channel or an external system?" is stored. A channel you are not ready to hand over is flagged as external.

Pre-setup checklist

• Does every sellable variant in the ERP 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?
• Customer account arrangement: one per buyer or one per channel?
• Have the invoicing moment and series been agreed with accounting?
• Are user roles (Admin, Content, Warehouse, Returns, Accounting, Reporting) and two-factor authentication planned?
• Which source will supply catalog content?

Fill in this list with the accounting and warehouse teams before setup; these decisions are made once.

How it works with Bulutegra

Bulutegra connects Logo, Mikro, SAP and Nebim V3 as ERPs and manages more than 24 marketplaces from one Integration Panel. Trendyol, Hepsiburada, Amazon, N11, Çiçeksepeti, Pazarama, PttAVM, Modanisa, Flo and İdefix, along with Amazon global, eBay, Etsy, Walmart, Ozon, Temu, SHEIN and Jumia, draw from the same stock pool. Orders are written to the ERP automatically with customer, line items, carrier and payment details; invoicing and shipping continue in your own process. Channels are checked continuously, and settlement tracking is visible to the Accounting role. The software was born in the founding company's own multichannel retail operation and ran there first.

To see how it connects to your ERP, fill in the demo form or review the options under Solutions.