Home → Integrations → Kaspi and 1C integration
Integration
Kaspi and 1C integration
Kaspi Shop orders create documents in 1C: invoices, returns and stock. Stock and prices from 1C update the Kaspi storefront automatically, with no manual work.
Leave a request or message us on WhatsApp — we will review your Kaspi cabinet and 1C configuration and show which data can be connected.
In short
BizDNAi connects the Kaspi Shop with your 1C: an order from Kaspi becomes a document in accounting, while stock and prices from 1C update the storefront.
The invoice for an order is created in 1C automatically, the PDF is attached to the deal, and returns are issued as separate documents.
Storefront stock matches accounting, so you do not sell on Kaspi what the warehouse does not have.
With the ready-made Kaspi connector, setup usually takes 1–3 days after access and API credentials are provided, unless there are non-standard constraints.
What data is synchronised
- Kaspi Shop orders
- products and matching by SKU
- storefront prices
- stock by warehouse
- order statuses
- returns
- 1C invoices created from an order
How it works
The platform collects Kaspi orders through the Shop API and passes them to 1C: an invoice is created for the order, and the document PDF returns to the processing chain.
The other direction is the price feed: stock and prices from 1C go to the Kaspi storefront so the buyer sees current data.
Returns and cancellations are processed as separate documents, so accounting does not diverge from actual movements.
What the business gets
Kaspi orders are not entered into 1C by hand — documents appear automatically.
Storefront stock does not diverge from accounting, which means fewer cancellations and customer complaints.
Returns and cancellations are reflected in accounting instead of staying only in the Kaspi cabinet.
Setup time
With the ready-made connector — usually 1–3 days after access and API credentials are provided, unless there are non-standard constraints.
If your 1C configuration has non-standard documents or warehouses, we first review the schema and agree on the timeline separately.
What you do not have to change
The company keeps working in its own 1C and in the Kaspi cabinet. BizDNAi does not replace the accounting system and does not move data into new software.
Product and warehouse matching rules are configured on the platform side.
What the connection covers
| Direction | What is transferred |
|---|---|
| Kaspi → 1C | Orders, invoices, returns |
| 1C → Kaspi | Stock, prices, product publishing |
| Both sides | Order statuses and product matching by SKU |
Frequently asked questions
Do we need to install anything in 1C?+
No, no separate installation in 1C is required. The platform reaches 1C through the OData interface and creates documents in the ways your configuration supports.
How are Kaspi and 1C products matched?+
Products are matched by SKU. If SKUs do not match, the mapping is configured separately to avoid duplicates and mixed-up goods.
What happens if an order is cancelled on Kaspi?+
A cancellation or return is processed as a separate document so accounting reflects the actual movement of goods.
Does it work with Kaspi Pay?+
The connection is built around the Kaspi Shop and its Shop API. We will clarify Kaspi Pay during the review — the available methods depend on your cabinet.
Can we connect only stock, without invoices?+
Yes. You can start with the price feed — stock and prices from 1C to the storefront — and add invoice creation later.
Free · no obligation
Free digital audit
We will review your data and show where the discrepancies, risks and losses are. You get a report with specifics — even if you decide to work with another contractor.
The price depends on your situation, after the free audit.