Your ERP, couriers and accounting exchange data on their own.
We connect the ERP, SAP, courier companies and invoicing software with the panels and the store your team uses. We start by finding where someone retypes data by hand today.
How we connect your company's systems
Every system exchanges data with the bus in both directions, not directly with the others. When you replace one of them, the rest keeps working.
In the middle
Data bus
One place every exchange goes through
ERP
Comarch XL, Optima, SAP
Orders, stock, prices
Payments
PayU, Przelewy24, Stripe
Payment statuses and refunds
Invoices
KSeF, accounting software
Invoices built from order data
Couriers
InPost, DPD, DHL
Labels and parcel statuses
Store and panels
Magento, Shopify, applications
Customers and staff see the same data
From a data map to a working exchange
-
01 A map of the data flow
We write down which system creates prices, stock and statuses, who retypes them and where they drift apart. We agree which system is the source of truth for each of them.
-
02 An agreement between systems
We describe what data flows each way and what happens when one of the systems doesn't respond. With a heavy ERP we plan an intermediate layer so its database stays unloaded.
-
03 Built in stages
We build the integration one flow at a time and test it in a staging environment. Every exchange is logged, so you can see what went through and what is waiting for a retry.
-
04 Launch and watching the queues
We switch the integration on in production and watch the queues. An alert about a stalled exchange reaches us before the warehouse notices.
- Developer Talks with departmentsData sources
- Developer ArchitectureError handling
- Developer Stage planChange review
- Developer LaunchMonitoring
- Agents API analysisERP table map
- Agents API documentationContract drafts
- Agents CodeTestsDocumentation
- Agents Regression tests
From our blog
We write about business systems, integrations, servers, AI and online stores, based on our work with clients.
