What does ERP integration do?
The ERP is the source of truth for customer/supplier accounts, stock, prices and invoices. Your e-commerce site, your B2B dealer portal and your marketplace stores all need this information, and orders and customer records eventually have to go back into the ERP. Without integration, your team handles this back-and-forth by hand. With integration, the information flows on its own and stays consistent.
We work with the common ERPs, above all Netsis and Logo, the ERP systems widely used in Türkiye. The connection can be built through the ERP's own services, through controlled read access at the database level or through an intermediate table. Which one fits depends on your ERP version and your infrastructure.
Decisions to make up front
| Data | Typical source of truth | Flow direction |
|---|---|---|
| Product record, price list | ERP | From ERP to site |
| Stock quantity | ERP | From ERP to site, at set intervals |
| Product description, images | E-commerce site | On the site only |
| Order | E-commerce site | From site to ERP |
| New customer record | Site or portal | To ERP as a customer account |
| Balance, credit limit | ERP | From ERP to portal |
We rewrite this table for every project based on how you work. The rule is simple: each piece of data has one source of truth. Data that can be changed in two places will sooner or later conflict.
Points to watch
- Account matching: If a customer coming from the site already exists in the ERP, no new account should be opened; records are matched by tax number or email.
- Units and variants: If the ERP tracks an item by the case but the site sells it by the piece, a conversion rule is written.
- Tax and discounts: It is made clear whether prices are transferred with or without VAT, and where dealer discounts are calculated.
- Fiscal period changes: The new fiscal-period database opened in the ERP at year end changes the integration's target; this switch is planned in advance.
- Write permissions: The integration user is given only the permissions it needs, and only on the tables it needs.
Example flow
Take a wholesaler: a dealer places an order through the portal. The order drops into the ERP as a sales order, the warehouse ships it, and the ERP creates the delivery note and invoice. The invoice number and shipment tracking details flow back to the portal, and the dealer can see the order status on their own screen. In this flow, nobody types the same information twice.
Checklist
- ERP name, version and where the server is located
- Contact details of the person or reseller who manages the ERP
- Data topics to transfer and the source of truth for each
- Daily number of orders and products (this sets the flow frequency)
- An ERP period or copy that can be used for testing
Frequently asked questions
Can ERP integration harm our ERP?
We test the integration in a test environment first and limit write permissions to the fields that are actually needed. Every transfer is logged and can be traced back when necessary.
We only want reports. Do we still need integration?
No. An ERP reporting solution that works read-only and never writes to the ERP is a better fit for that need.
For our overall approach, go back to the integration services page, or get in touch to talk about your ERP.