Short answer: three routes, one rule
There are three ways to connect a dealer portal to an ERP: the vendor's official API or service layer, file or staging-table transfer, and direct database access. The rule is this: when you write data into the ERP, use the layer that passes through the vendor's business rules, and do not write straight into the database. Fast methods (views, staging tables) are acceptable for reading, not for writing.
The official layers that appear in the public documentation of four ERPs are these:
| ERP | Official integration layer | Protocol | Clarify first |
|---|---|---|---|
| Logo Tiger | Logo Objects, Logo REST service | COM, REST (JSON) | Version (REST only on Tiger 3 and Wings series), Objects license |
| Logo Netsis | NetOpenX, Netsis REST API | COM, WCF, REST | NetOpenX license and product version |
| Mikro | Mikro Desktop API | REST (JSON) | API Key license, V16/V17 compatibility, server and port setup |
| Canias | TROIA Web Services 2.0 | SOAP (WSDL) | License for the web service module, no REST |
The information in this article is compiled from the public documentation of vendors and integration firms; confirm it with the vendor or an authorized partner for your product version before you start. We do not describe which projects we have done with which ERP; this is a selection and question guide.
What does a dealer portal need from the ERP?
Which data flows in which direction?
A dealer portal does not replace an ERP; it shows the price, stock and account data held in the ERP and writes orders back. We covered how a B2B dealer portal differs from ordinary e-commerce in what is a B2B dealer portal; the ERP connection was the seventh difference there. A typical flow:
| Data | Direction | Frequency (our suggestion) |
|---|---|---|
| Stock card, price list, discount | ERP → portal | Scheduled, and when prices change |
| Stock quantity | ERP → portal | Frequent (minutes), re-checked at order time |
| Account balance and limit | ERP → portal | Read at order time |
| Order | Portal → ERP | Immediately |
| Order status, delivery note, invoice | ERP → portal | When status changes |
Which system should be the single source of truth?
If price, stock and account data are kept in the ERP, the ERP is the source of truth; if the portal copies them into its own database, decide up front how old that copy may be. Updating the same information by hand in two places is the first thing that breaks a dealer's trust. This is an opinion, not a sourced fact.
Route 1: the official API or service layer
Logo Tiger: Objects and REST
Logo Objects, as defined in Logo's price list, is Tiger's data transfer and integration tool, the standard interface used to connect systems to Logo ERP. The Logo REST service is the REST interface of that Objects layer: according to Datasource it has no license of its own, it needs a valid Objects license, and it is supported only on the Tiger 3 and Wings series (Tiger 3, Tiger Wings, Tiger 3 Enterprise, Tiger Wings Enterprise); Logo Start, Go Plus, Go 3, Tiger Plus and Tiger Enterprise are among those listed as unsupported. So first establish which Logo product and version you run: on a version without REST, the route is the COM-based Objects.
Logo Netsis: NetOpenX and the REST API
Logo's Netsis 3 Enterprise product page lists NetOpenX and the Netsis REST API for integrating third-party applications. Logo's help page for Netsis customization tools also says the integration tools are WCF-, REST- and COM-based. According to Logo's customization tools price list, a NetOpenX license can be used with Netsis Wings Enterprise, Netsis Wings, Netsis 3 Enterprise and Netsis 3 Standard. The same list says Objects and NetOpenX licenses are single-user and that customization tools can only be ordered by ecosystem solution-development partners. The practical consequence: ask whether the firm that will write the integration is a partner that can obtain this license.
Mikro: the Mikro Desktop API
Mikro's API portal describes the Mikro Desktop API as REST- and JSON-based; its stated audience is Mikro customers, partners and third-party developers, and applications go through a form. Several items on the FAQ page bear directly on a dealer portal project:
- The API runs on a local server and does not support Active-Active use.
- The API is a Windows service; SSL and port forwarding are handled by system administrators.
- The API Key license is assigned automatically to users of vertical solutions; for in-house software it is granted manually.
- A demo setup allows testing with up to 100 records; a test database can be opened for licensed users.
The first of these affects the architecture: if the API runs on your own on-premises server, how the portal reaches it from the internet, and behind which security layer, is a separate design decision.
Canias: TROIA Web Services 2.0
The troia-webservice-connector example in IAS's own GitHub account, the company behind Canias, shows connecting to the TROIA platform through web service 2.0: you connect to a WSDL address, log in (login), call a service (callService) and log out. In other words the interface is a session-based SOAP service. According to Pexon's review there is no documented REST API, and the license terms of the web service module (WSR) are not public; for the license, ask IAS or your Canias partner. A dealer portal can talk to these SOAP services, but settle at quote stage who will write those services (price, stock, order) on the TROIA side.
Route 2: file or staging-table transfer
If the official API's license or version does not fit, a file the ERP exports (CSV, XML) or a staging table linked to the ERP can be used. The real cost of this route is delay: price and stock update when the file runs, and stay stale in between. On the order side, if the ERP's own import tool reads the file, the records are expected to pass through the ERP's own checks; ask the vendor to confirm that. Treat this route as an interim solution and check whether stock can still be verified at order time through an API or a query (our suggestion).
Route 3: direct database access
Why is writing straight to the database risky?
This warning is common in integration firms' own guides: i-Pazaryeri's guide says direct SQL access on Logo gives a performance advantage but risks bypassing Logo's business rules (VAT calculation, triggering stock movements), and that the official API should be preferred in production. In the same direction, on a Netsis integration page YK Yazılım says it uses direct SQL views only for read-only reports and always writes through NetOpenX. Both are vendor pages, not the ERP manufacturer's own documents, but the method is consistent. Views for reading and the official layer for writing is the balance we recommend too.
Errors, retries and concurrency
If a dealer places an order and the ERP is unreachable at that moment, the order must not be lost; it should wait in a queue and be transferred later. If the same order is sent twice, the ERP must not end up with duplicate records (the same order number is not processed a second time). These are not sourced facts but general integration design practice, and they are questions for the quote: what happens when the ERP is down, how does resending work, whose screen does an error land on?
License and cost items
The cost of the integration is not only the software fee: the integration license on the ERP side (Objects or NetOpenX for Logo, an API Key for Mikro), developer training, a test environment, server and security setup and later maintenance are separate items. To think about their total over five years, you can add an "integrations" row to the blank table in our ERP pricing: 5-year total cost article. If you are still at product selection, our 12 questions to ask when choosing an ERP vendor in Izmir article covers integration questions too.
10 questions before asking for a quote
| # | Question |
|---|---|
| 1 | What is your ERP product and version? Is the official API supported in that version? |
| 2 | What additional license does the integration need, and who sells it? |
| 3 | Which direction and how often will price, stock and account data be transferred? |
| 4 | Which document will the order become in the ERP (order, delivery note, invoice)? |
| 5 | How will the order queue work when the ERP is unreachable? |
| 6 | What happens if the same order is sent twice? |
| 7 | If the ERP server is on premises, how will the portal reach it securely? |
| 8 | Who will prepare the test environment and test data, and when? |
| 9 | Who is responsible for the integration when the ERP is upgraded? |
| 10 | Whose screen will the error log and monitoring land on? |
If you are considering building the integration as a custom software project, see our custom software development page, and for the e-commerce side our e-commerce service page.
Frequently asked questions
Which ERPs can a dealer portal work with?
If the ERP exposes an interface to the outside (an API, a web service, an import tool), a dealer portal can connect to it. In this article we listed the layers that appear in public documentation for Logo Tiger, Logo Netsis, Mikro and Canias; ask the vendor to confirm which one your version supports.
Is it safe to write directly into the ERP database?
Integration firms' guides advise against it: direct writing can bypass the ERP's business rules (tax calculation, stock movements). Database views can be used for reading; for writing, the vendor's official layer is preferred.
Does the integration need a separate license?
In most cases yes, depending on the product. In Logo's customization tools list, Objects and NetOpenX are separate licenses and the Logo REST service needs a valid Objects license; Mikro's API needs an API Key license; for Canias, the license terms of the web service module are not public. Ask for this as a separate line in the quote.
How many weeks does the integration take?
We could not find reliable published duration data for Turkey. Duration depends on the ERP version, the number of data flows, whether the test environment is ready and how fast you approve; ask for a phased plan and a pilot date in writing.
If you would like to talk through a dealer portal connected to your own ERP, get in touch.
Sources: Mikro Desktop API (Mikro Yazılımevi), Mikro API process, FAQ (Mikro Yazılımevi), Logo Netsis 3 Enterprise (Logo Yazılım), Logo customization tools recommended price list (Logo Yazılım; copy hosted on Destek Yazılım's site, accessed 12 November 2026), Logo REST Service installation and configuration (Datasource), troia-webservice-connector (IAS, GitHub), Canias ERP connector review (Pexon, as of 21 September 2026), ERP and accounting integration guide (i-Pazaryeri), Logo Netsis customization tools help and support (Logo Yazılım, Dijital Danışman), Netsis integration (YK Yazılım)
Cover photo: Rifki Kurniawan / Unsplash