Case study: Kaspi, 1C and CRM integration
Client background
- E-commerce retailer in Almaty, 700+ SKUs.
- Orders arrived from Kaspi Store, CRM and Instagram; managers retyped everything into 1C manually.
Objectives
- Sync orders/payments from Kaspi → 1C → CRM.
- Real-time stock updates.
- Automated customer notifications (WhatsApp/email).
Architecture
Kaspi API → Integration Layer (Nest.js + Supabase) → 1C + Bitrix24 CRM
- The integration layer listens to Kaspi webhooks (orders, payments).
- 1C consumes the data via OData REST.
- Bitrix24 is updated through its REST API.
Implementation highlights
- Queue/retry logic built on Supabase Edge Functions + scheduled cron.
- Security: signed webhooks, VPN tunnel with on-prem 1C.
- SLA: < 2 minutes from purchase to synced state.
Results
- Eliminated manual copying (30 hours saved weekly).
- CRM errors decreased by 92%.
- Order processing time dropped from 15 to 3 minutes.
Lessons learned
- Kaspi and 1C expect different encodings — normalize early.
- Respect Kaspi rate limits (5 req/sec) and plan batching.
- Observability matters: structured logs + Supabase dashboards.
More resources
- Tender checklist for Kazakhstan — procurement criteria and risk mitigation.
- Technical spec template — ready-to-use structure with KZT budget.
Wrap-up
TL;DR: middleware works when you control latency, encoding and monitoring from day one.
- agree on SLA (<2 minutes) for every integration path;
- normalize data formats between Kaspi, 1C and CRM;
- instrument the pipeline with logs + dashboards so ops can react instantly.
Want a similar middleware? Let’s discuss your stack.
➡️ Need a similar middleware? Fill out the brief and I’ll send architecture + quote within 24 hours.