ERP, Customer Relationship Management, and e-commerce integrations
Lead from a form in Customer Relationship Management. E-commerce order in ERP. Invoice in accounting. Stock in the online store. We make conneCTOrs to order for Polish ERP systems (Comarch, Optima, Asseco) and standard for SaaS (Pipedrive, HubSpot, Salesforce, Allegro, IdoSell).
If you recognize at least two of these, it makes sense to talk about integration.
01
The form on the website sends an email with the customer's information. An assistant enters this data into the Customer Relationship Management two days later. The lead waits, and the sales department calls five days later. In the meantime, the customer has called a competitor. Without carmatic routing, this pattern repeats itself every week.
02
A customer buys a product from an online store that’s out of stock. Returns, complaints, frustration. Or the opposite: the product is in stock, but the store shows “out of stock” because the inventory was last updated yesterday. Every time you move inventory, you have to click through two systems.
03
The sales department issues an invoice in System X. The accountant opens Symfonia / Optima / KPiR and enters the line items manually. Misyeses in the tax ID number, date discrepancies, and monthly corrections. KSeF requires integration, but only for invoicing, not for internal company workflows.
04
Status in Customer Relationship Management (when submitted), in ERP (whether in production), in the courier system (whether shipped). The sales rep clicks through three tabs; the customer calls again on Friday. No single view = no response within 30 seconds.
A clickable prototype in a test environment before we write a single line of production code. Payment in four installments.
Week 1
Audit of systems (what are you using today, where are the APIs, where is CSV export only). Data map: which field in Customer Relationship Management corresponds to which in ERP, where the name conflicts, who is the source of truth. Deposit: 30%.
Weeks 2–3
Decision: point-to-point integration (system A ↔ system B directly) or intermediate layer (n8n / Make / own ESB). Live or batch (e.g. once a day at night). Conflicts: which system wins at the crossover.
End of Week 3
You approve the prototype. We won't start building the MVPithout your approval. Upon approval: another 30%.
Weeks 4–7
ConneCTOrs (dedicated to Polish ERPs, ready for REST/SOAP standards). Tests in a test environment with your real data (anonymized). Each week a demonstration of working synchronization. After the MVP release: another 30%.
Week 8
Switching from the test environment to production, synchronization monitoring (alerts when ERP does not respond, when there is a data conflict). IT team training: how to diagnose errors, how to modify mappings, where to look for logs. After implementation: last 10%.
Customer in Customer Relationship Management = customer in ERP = customer in accounting. Name, NIP, address, history: one record, several views. Change in one place is propagated wherever necessary. No more "you are registered with us at a different address" situation.
Stock status between ERP and store: every 30 seconds. Lead from form to Customer Relationship Management: 5 seconds. Monthly report to BI: once a day, at night. The live or batch decision is made with each integration separately, based on what is actually needed.
Reality: two systems, two different names of the Same company. Conflict rules established in advance: who wins (ERP or Customer Relationship Management), how data is merged, when an alert is sent to a human. Without it, integration falls apart after 6 months.
Each synchronization with timestamp and change history. „Why did the price drop in the store yesterday?" Reply in 30 seconds. Logs compliant with GDPR, API access for the auditor without rigid export.
Every integration with us ends with the Same thing: one view instead of five. Examples from three clients.
KG Electronics · Boiler Manufacturer
12 000
Three layers synchronized live: the controller sends telemetry every 30 seconds, the backend aggregates it, the client's mobile application and the service panel read from the Same source. 12,000 devices, no data conflicts, has been operating for 18 months.
View the full case studyAkpil · Manufacturer of agricultural machinery
3 hours → 4 minutes
The customer selects a machine in the configurator; the data is synced with the manufacturer’s ERP system; the lead is carmatically forwarded to the regional dealer; and the generator compiles a company PDF with a price list and sends it via email. The four systems communicate with each other, and the sales representative receives a ready-made quote instead of having to enter the information manually.
View the full case studyAutomation · Related Services
8 weeks
Once the systems are talking, it's time to carmate processes: follow-up contact after a lead, generating reports, alerts about order status. Integration is the foundation, carmation is the superstructure.
See carmationsTwo architectural approaches; the decision is based on the system map.
Point-to-point (P2P)
Middle layer (n8n / ESB / iPaaS)
P2P is enough when the system is small and stable. The intermediate layer is done when there are 5+ systems or you plan to replace one of them within 2-3 years.
What happens after implementation, and who we are.
After implementation
Optional packages. We will discuss the details during a meeting after implementation.
See also
30 seconds on JSON Crew
A software company specializing in digital transformation for B2B sales. Product configurators, dashboards, and sales process carmation. Three key case studies (Akpil, Forest, and the internal JSON Hub platform) and portfolio implementations (KG Electronics, Metal Roofing, a heat recovery center, and modular homes).
Individual valuation after a system audit. Fixed price after defining the scope, schedule 30 / 30 / 30 / 10. Each additional system is a separate valuation of the conneCTOr. The cost depends on the API documentation and the level of standards (REST/SOAP vs. custom ERP without API).
Polish ERP systems: Comarch ERP XL, Optima, Asseco, Symfonia, Subiekt GT/Nexo, enova365. International: SAP, MS Dynamics, NetSuite. Customer Relationship Management: Pipedrive, HubSpot, Salesforce, Monday, ClickUp. E-commerce: Shopify, Shoper, WooCommerce, IdoSell, Allegro, BaseLinker. All come with standard API documentation; we provide pricing for non-standard ERPs following an audit.
Three options: (1) integration via the database (we read directly from the ERP database, if the supplier allows), (2) integration via a file (CSV / XML dumped into a folder, e.g. at night), (3) reading from the screen (last resort, slow and fragile). We start by talking to your ERP provider. Often the API is there, you just don't know.
Decision for each integration separately. ERP stock ↔ store: live (every 30 seconds). Lead from the form ↔ Customer Relationship Management: live (5 seconds). Accounting synchronization: batch once a day, overnight. Live synchronization costs more to maintain, so only where the business requires it.
Middle layer on your own server, on your infrastructure = data never leaves your server. Data entrustment agreement with SaaS providers (if we use Make/Zapier for some processes). Logs with time stamps, possibility of exercising the right to delete in accordance with GDPR. For regulated industries (medicine, finance), we recommend a fully dedicated Python on your own server.
Architecture with an intermediate layer (recommended for 5+ systems) resistant to such replacement: you change the conneCTOr of one system, the rest of the integration remains unchanged. Point-to-point architecture requires rewriting all connections to this system. Architectural decision in the first stage of discovery: we ask about 2-3 year plans before we choose an approach.
Please list the systems you currently use (ERP / Customer Relationship Management / e-commerce / accounting) and describe the data you want to exchange between them. We will respond within one business day.
