Why connect to the ERP?
At many companies, product cards, stock, price lists and current accounts already live in an ERP or accounting system. If the dealer portal keeps its own copy of this data, the two sources drift apart over time: the portal shows an item in stock that is not in the warehouse, a dealer sees an old price, the account balance does not match accounting. The goal of the connection is to keep the ERP as the single source of truth and turn the portal into an up-to-date window onto it.
Which data flows which way?
| Data | Direction | Update frequency |
|---|---|---|
| Product card, code, unit | ERP to portal | Whenever it changes |
| Price lists and discounts | ERP to portal | Whenever they change |
| Stock quantity | ERP to portal | At short intervals |
| Account balance and open invoices | ERP to portal | At short intervals |
| Dealer order | Portal to ERP | When the order is placed |
| Collection (card payment) | Portal to ERP | When the payment is made |
This table is a typical example. Some companies prefer to manage pricing rules in the portal instead of the ERP; that works too. What matters is that every piece of data has exactly one owner.
Connection methods
There are several ways to connect to an ERP: the ERP's own web services, controlled reads and writes through the database, or file exchange. Which one we use depends on your ERP version, how it is installed and your security preferences. We review your existing system first and recommend the safest path with the least intervention. Company-specific connections are covered by our integration service.
What if the connection drops?
A good integration is built on the assumption that the connection will sometimes drop. The portal records orders on its own side and passes them along in sequence once the connection is back; the same order is never transferred twice. If the connection stays down for a set period, an alert goes to the person responsible. From the dealer's point of view, ordering carries on without interruption.
The reporting side
Once dealer orders land in the ERP, management's questions change: which dealer is buying how much, how are collections going, which product group is growing? Our ERP reporting service and READERP report on this data in common ERPs, led by Netsis and Logo, the ERP systems widely used in Türkiye, with read-only access and without writing a single line to your ERP.
Checklist
- Are product codes exactly the same in the ERP and the portal?
- Has the owning system been decided for each piece of data?
- Has a buffer quantity been set for the stock shown to dealers?
- Which document type will portal orders open as in the ERP?
- Who gets the alert when the connection fails?
Frequently asked questions
Which ERPs do you work with?
We work with the common ERP and accounting systems on the market, led by Netsis and Logo. If you use a different system, we review it first and assess the options.
Will the connection slow down my ERP?
Queries are kept light and scheduled around your busy hours; we set it up so it does not affect the day-to-day use of your ERP.
For the full service, head back to the B2B dealer portal page, or get in touch to talk about your ERP setup.