ERP integration means a record created in another system (a web order, a delivery entered in the field, a customer card) reaches the ERP without being typed in again, or that ERP data (stock, prices, account balances) reaches other systems automatically. The goal is to stop writing the same data twice and having it drift apart in two places. In Türkiye, systems such as Logo, Mikro and SAP are common; whichever you use, a sound integration starts with clear answers to the same few questions.
1. How does the ERP expose its data?
This is the first and most decisive question. Typical routes are:
- The vendor's official API or web service: the healthiest route. Authorisation, version compatibility and business rules stay under the vendor's control.
- An integration module or middleware product offered by the vendor or a partner: check whether it is included in your licence.
- File exchange (for example files imported/exported at intervals): simple but delayed, and fragile if errors are tracked by hand.
- Writing directly to the database: usually not recommended. It can bypass the ERP's own business rules (tax calculation, stock movements, approval steps) and break silently after a version update.
Which route is available depends on the product, the version and the modules in your licence. Before deciding, check the vendor's current documentation and your authorised partner; do not assume that a method that works at another company will work for you.
2. Which data flows in which direction?
Each record type should have a single "source of truth". If the ERP is the source for stock and prices, the website only reads them; if orders are created on the website, they flow one way into the ERP. Two-way sync, where a record can be changed in both systems, is possible, but without a rule written up front about which change wins, data conflicts are inevitable.
- Orders: website/app → ERP
- Stock and prices: ERP → website/app
- Customer accounts: agree explicitly where they are created and updated
- Invoices and dispatch notes: usually created in the ERP; e-document processes are assessed separately
3. How often, and with how much delay?
Not everything needs to be "real time", and real-time integration costs more. A few minutes' delay on stock is acceptable for most online stores, while a payment confirmation at the till may need to appear within seconds. Write down the acceptable delay for each flow; the architecture follows from that answer.
4. Permissions and security
The integration should use a dedicated user or service account in the ERP with permission only for the operations it needs; an integration running on a manager's password stops the day that person leaves or changes it. Access keys belong in the server environment, not in the code, and every operation should be logged against the account that performed it.
5. What happens when a record cannot be transferred?
Most integrations do not break on day one but in month three: a product code was deleted in the ERP, a tax rate changed, the server was unreachable for an hour. In a sound setup, a record that fails is not lost; it waits in a queue, is retried automatically and, if it fails again, the responsible person is notified. At quote stage, always ask: "who will see a failed record, and where?"
6. Before going live
- Test with real scenarios in the ERP's test company or test environment.
- In the first days, compare a sample of transferred records by hand.
- Write into the maintenance scope that the integration is retested before each ERP version update.
Once these six answers are in writing, the cost and risk of the integration become visible. Every question left unanswered comes back later in the project as a surprise.
