- Client
- Retail company, Kazakhstan
- Industry
- Retail and e-commerce
Kaspi, ERP and CRM in one flow
Orders, stock and customers synced between a marketplace, an ERP and a CRM through a middleware layer with its own state.
- order processing time
- −80%
- stock update on Kaspi
- ~10 min
- operator errors
- −50%
- manual operator work
- −50%
The problem
Orders from Kaspi.kz were retyped into the ERP and the CRM by hand. Stock on the marketplace lagged behind the warehouse, so customers bought items that were already gone and orders were cancelled. The same customer existed three times in three systems.
What I built
A middleware service with its own PostgreSQL state between the marketplace, the ERP and the CRM:
- order import from the marketplace with SKU and article mapping;
- two-way stock sync on a schedule and on change;
- customer deduplication by phone and business keys;
- retries with backoff, a log of every exchange and discrepancy monitoring.
The result
New marketplace orders reached the CRM in about a minute, and stock updates reached Kaspi in about ten minutes. Order processing time fell by 80%, operator errors and manual work by up to half, and cancellations caused by stale stock halved.
How such an exchange is built with 1C, where it usually breaks and what it costs is covered in How to connect Kaspi.kz with 1C.
Solution behind it
Integrations
CRM, ERP and marketplace integration
Two-way sync between 1C, Odoo, Bitrix24, amoCRM, Kaspi and your internal services, with retries, deduplication and a discrepancy report.
- Python
- Go
- PostgreSQL
- RabbitMQ
from$250