ERP integration means sharing data from your accounting and resource planning system automatically and consistently with other software such as a field sales app, a B2B portal, an online store or reporting tools. Many small and mid-sized companies in Turkey run Logo, Mikro or Netsis, and there is more than one way to connect to them. This article compares the three main ERP integration methods, API, direct database access and middleware, and explains when to use each.
What data moves in an ERP integration?
| Data | Direction | Typical frequency |
|---|---|---|
| Products, units, barcodes | ERP → app | Daily or on change |
| Price lists and promotions | ERP → app | On change |
| Stock levels | ERP → app | Frequent or near real time |
| Customer accounts and balances | ERP → app | Frequent |
| Orders | App → ERP | Immediate |
| Payments and returns | App → ERP | Immediate or end of day |
Method 1: APIs and web services
You integrate through the services or object libraries the ERP vendor provides, such as Logo Objects and REST services for Logo or NetOpenX for Netsis. Availability depends on the product, version and licence, so check your own installation with your ERP partner.
- Pros: business rules such as tax, discounts and document numbering are applied by the ERP itself; integrations survive upgrades better; data integrity is protected.
- Cons: may need extra licences; bulk reads can be slow; some fields may not be exposed.
Method 2: Direct database access
Logo, Mikro and Netsis usually run on Microsoft SQL Server, so reading tables directly is technically possible and fast.
For reads such as products, stock, prices and balances, controlled access through a read-only user and views is reasonable. For writes such as orders or invoices, it is risky. The ERP updates several tables together and handles numbering and balances with its own logic; bypassing that can create inconsistent records, and schema changes in upgrades can silently break the integration.
The rule of thumb: read from the database, write through the ERP's own services.
Method 3: Middleware
Middleware is a service with its own database and logic that sits between your apps and the ERP. The app never talks to the ERP directly. Middleware can:
- Cache ERP data so the mobile app stays fast.
- Queue incoming orders and push them to the ERP in a controlled way.
- Hold and retry data when the ERP is unreachable.
- Flag failed records for review.
- Put several ERPs behind one consistent interface.
- Centralise authentication, permissions and audit logs.
It also removes the need to expose the ERP server to the internet: a connector on the local network talks to the middleware over an encrypted channel.
Real-time or scheduled sync?
Timing matters as much as method. Rarely changing data such as products and price lists can sync on a schedule, ideally as delta syncs that fetch only changed records. Orders and payments are best handled as events: queued when created, pushed to the ERP and retried if the connection fails. Critical values such as current stock or credit limit can be queried on demand before an important order. If the mobile app works offline, define conflict rules up front, for example whether an offline order keeps the price at entry time or at sync time. That is a commercial decision to agree with sales and finance, not just a technical one.
Comparing the three methods
| Criterion | API | Direct database | Middleware |
|---|---|---|---|
| Data integrity | High | Good for reads, risky for writes | High if writes use the API |
| Performance | Depends on service | High for reads | High thanks to caching |
| Fault tolerance | Low | Low | High |
| Upgrade resilience | Good | Weak | Good |
| Setup effort | Medium | Low | Higher |
In practice a hybrid usually works best: middleware in the centre, fast reads through views, writes through official ERP services.
Integration checklist
- Decide which system owns each piece of master data.
- Align product codes, customer codes and unit conversions.
- Prevent duplicate orders with a unique key per record.
- Make failed transfers visible on a dashboard.
- Never test on the live ERP; use a test company or a database copy.
For practical details on Logo and Mikro, see our article on Logo and Mikro ERP mobile integration.
BernSFA is set up to sync stock, products, customer accounts, price lists and promotions with Logo, Mikro, Netsis, SAP and systems exposing REST or SOAP services. Visit our SFA software page or contact BernSoftware to plan an integration that fits your ERP.
Frequently asked questions
Why shouldn't I write directly into the ERP database?
The ERP updates several tables together and applies its own numbering and balance logic when creating a record. Writing directly bypasses that logic and can produce inconsistent data or break after upgrades.
Do Logo, Mikro or Netsis APIs require an extra licence?
It depends on the product, version and your existing licence. Check which services are available with your ERP partner.
When do I need middleware for ERP integration?
Middleware is worth it when you need caching for mobile performance, queuing and retries when the ERP is unavailable, central security, or when several apps or ERPs must share one integration layer.
Planning a project like this?
Plan it in 10 steps