In short
- Writing documents to the ERP is best done through Comarch's official interfaces - then the system's logic applies (numbering, stock, settlements).
- File exchange (XML, CSV) is simple and fine for periodic exchange, but brings delays and needs error handling.
- Reading directly from the database can be fine for reports; writing directly is risky and may break after an update.
- Before you start, check the system version, your licences and access to a test environment.
- A good integration has a queue, an error log and a plan for when the ERP does not respond.
When you need an integration
You need an integration wherever someone retypes data between systems today: orders from a shop, documents from a mobile app, invoices after approval in a document workflow, stock levels for customers. Every retyping costs work time and leaves room for errors.
Three ways to integrate
Comarch develops several ERP systems - the ones most often found in companies are Comarch ERP Optima, Comarch ERP XL and Comarch ERP Altum. Whatever the version, integration comes down to one of three routes:
| Route | When it works | Advantages | Risks |
|---|---|---|---|
| Official Comarch interfaces (API) | Writing documents and master data, near real-time integrations | ERP logic applies: numbering, stock, settlements; supported by the vendor | Requires the right licences; depends on the system version |
| File exchange (XML, CSV, EDI) | Periodic exchange with a partner, price list imports, data exports | Simple, independent of the other side's technology | Delays; wrong and repeated files have to be handled |
| Directly in the database | Reading for reports and analysis | Fast access to data without extra licences | Writes bypass ERP logic; the database structure may change after an update |
The names and scope of the official interfaces differ between systems (for Optima this includes Sfera, for XL - XL API), and their availability depends on your licences. Confirm this with your Comarch partner before asking for an integration estimate.
How to choose
- The app creates documents in the ERP (orders, invoices, goods receipts) - official API.
- A partner sends a daily file with orders or you need a price list export - file exchange.
- You want a report or a dashboard with ERP data - reading from the database (ideally from prepared views) or the API.
- You do not know what your licence includes - check that before asking for an estimate.
What to watch out for
- Versions and updates: the integration has to survive an ERP update. Official interfaces are designed for that, direct database writes are not.
- Test environment: integrations are tested on a copy of the database, not in production.
- Master data mapping: customers, items, units, VAT rates and warehouses must match on both sides.
- ERP not responding: data should wait in a queue and reach the ERP once the connection is back, and someone should be notified of the error.
- Duplicates: sending the same document again must not create a second copy.
- Permissions: the integration runs on a separate operator account with access only to what it needs.
How 2Simple approaches integrations
We start with a review: system version, licences, available interfaces and the process the integration should cover. We build and test the integration on a copy of the database, with a queue, an error log and retries, and monitor it after deployment.