Integrations
Kaspi.kz and 1C integration
Kaspi orders reach 1C every minute, and stock and prices go back to Kaspi. No retyping and no duplicate buyers.
- stock update on Kaspi
- ~10 min
- order processing time
- −80%
- operator errors
- −50%
When you need a Kaspi.kz and 1C integration
If you sell on Kaspi.kz and run your accounting in 1C, you need it when:
- managers retype Kaspi orders into 1C;
- Kaspi stock lags behind the warehouse, and orders for items that are already gone get cancelled;
- the same buyer exists in 1C several times;
- you learn the exchange has stopped from a buyer who calls to ask where the order is.
What moves between Kaspi and 1C
- New orders from Kaspi to 1C every minute, with the Kaspi order number.
- Customers from Kaspi orders to 1C, with each order.
- Stock from 1C to Kaspi on a schedule and on change.
- Prices from 1C to Kaspi on a schedule.
How I build it
The exchange runs through a separate service, not a module inside 1C. The service keeps its state in PostgreSQL: which orders were already taken, the status of each exchange, the last error. Every exchange is logged, and if 1C is down, orders wait in a queue and go through once it is back.
Duplicates and wrong products are stopped before anything reaches 1C:
- before creating an order, the service checks that 1C has no order with the same Kaspi number;
- the buyer's phone number is normalized (+7, 8, spaces) before it is used to find the customer;
- items are matched by SKU, and an order with an unknown SKU goes to manual review instead of getting a guessed product.
A similar project
For a retail company in Kazakhstan I connected Kaspi.kz with an ERP and a CRM through the same kind of service. New orders reached the CRM in about a minute, stock reached Kaspi in about 10 minutes, and order processing time fell by 80%. With 1C the scheme is the same; only the way the accounting system is called changes.
More in the project write-up Kaspi, ERP and CRM in one flow. The exchange step by step, and where it usually breaks, is covered in How to connect Kaspi.kz with 1C.
Packages
Prices are fixed for the described scope. Larger scope gets its own estimate.
Basic
$250
- One-way exchange, for example Kaspi orders into 1C
- Log of every exchange
- Instructions and handover
Standard
$600
- Orders into 1C and stock from 1C to Kaspi
- Retries on failure
- Duplicate buyers merged by phone
Premium
$1,200
- Everything in Standard
- Scheduled reconciliation of orders and stock
- Alert when orders stop arriving
How we work
From a short message to a working version
- 01
Describe the process
A few paragraphs: which systems, what goes wrong, what the result should be.
- 02
Get the approach and a price
Within 24 hours: how I would build it, the first risk to settle and a fixed estimate.
- 03
See a first working version
On your real data, early, so we correct course before the budget is spent.
- 04
Take it over
Tests, a README and a handover call. Support after launch if you need it.
Questions
Can the exchange be a module inside 1C?
It can, but such a module silently stops while 1C is busy closing a period or updating. A lost response turns into a second order, and when something fails it is hard to tell what failed and when.
What should we keep in mind about cancellations on Kaspi?
An order cancelled on Kaspi must release its reservation in 1C. Otherwise the goods stay reserved for an order that no longer exists.
How do we know the exchange has stopped?
An exchange can stop without a single error on screen. The Premium package adds an alert when orders have not arrived for longer than usual and a scheduled reconciliation of orders and stock.
What do you need from us to start?
Access to the Kaspi merchant account, the name of your 1C configuration and its custom changes, the warehouses whose stock should appear on Kaspi, SKU exports from both systems, and the person who will review orders that did not go through automatically.