While you have 30 products, you can update prices and stock on Kaspi by hand. When there are 500 and sales also go through a website, Instagram and an offline point, manual work starts to cost money. An item runs out in the warehouse but stays listed on Kaspi. An order arrives and there is nothing to ship. The cancellation hits your seller quality metrics.
There is one solution: connect Kaspi to your accounting system so data flows both ways by itself. Below we cover what tools Kaspi gives you for this, how ready-made services differ from a custom integration and what changed in 2026.
Which integration tools Kaspi offers
Kaspi Magazin has two official automation channels, and people often confuse them.
The first is the XML price list. It carries products, prices and stock levels. Kaspi picks the file up itself from the link you specify in the seller's account.
The second is the API. It is a programming interface through which your system can add products, receive orders and manage them. Data is exchanged in JSON format.
In a proper integration both channels work together: the price list handles the storefront, the API handles orders.
Prices and stock: the XML price list
A price list can be uploaded manually in Excel, but automation requires XML. The file can be exported from the seller's account as a template, written by hand or generated automatically, for example in 1C. For each product the file specifies the SKU, name, brand, price and stock by warehouse, which are denoted by the codes PP1-PP5. If prices differ by city, a separate format with city codes is used.
Then the file is placed on your server and the link to it is entered in the account: Products, Upload price list, Automatic upload. Your system updates the file when prices or stock change, and Kaspi picks it up.
There are two details worth knowing in advance.
- Kaspi checks the XML file roughly once every 60 minutes, so a new price will not appear on the platform instantly.
- If a product is missing from the XML file, Kaspi may take it off sale.
So before enabling automatic upload, check that every product that should be on sale makes it into the export. Otherwise you can "lose" half the catalog in an hour.
Orders: the Kaspi Magazin API
To start working with the API, the company's director generates a token in the web version of the seller's account: Settings, API token, Generate (Kaspi Guide). Only the director can generate the token (SelSup). The token is then entered in your system and must be stored as carefully as a bank password.
Through the API you can receive new orders and their contents, change the status to "Issued", cancel an order, generate a waybill for Kaspi Delivery, find out the warehouse address and even specify the IMEI for phones. In practice this means a manager can work with Kaspi orders from their own CRM or 1C without switching between windows.
An important point from Kaspi's rules: processing orders outside the seller's account is prohibited, but processing through the API is a permitted exception (Kaspi Guide). So integration via the API is the official route, not a workaround.
Honestly about the difficulties. Kaspi has documentation, but the API does not always behave obviously. Developers who integrated the Haier online store with Kaspi described, for example, that a filter on a single order status also returns orders with other statuses. Such things only come out in testing, so budget time for it.
What changed in 2026
The National Product Catalog
Since 1 January 2026 Kaspi Kassa has been integrated with the National Product Catalog, and in the Kaspi Magazin account you can specify a GTIN or NTIN barcode for a product and the system will find it in the catalog. The catalog itself is growing fast: by July 2026 it held 29 million products, 16.2 million of them with a GTIN code.
For integration this means a simple thing: barcodes must be stored in your accounting system and sent to Kaspi together with the rest of the data. If barcodes live in a separate spreadsheet kept by a manager, it is time to move them.
Delivery rates
Since 1 January 2026 the delivery cost for sellers depends on the order amount, weight and dimensions, delivery type and product category. If you calculate margin per product, weight and dimensions should also be kept in the system rather than recalled for every order.
Ask a question or leave a request
Tell us where your records are kept now and how many products you have. We will say whether a ready-made module is enough or you need a custom integration.
By submitting the form, you agree to the processing of personal data.
Off-the-shelf service or a custom integration
The fastest route is a ready-made service. Kaspi has an official list of technology partners who handle integrations, and accounting systems such as MoySklad offer ready-made modules for Kaspi. If you are a small seller, work in one of these systems and simply need to sync prices, stock and orders, a ready-made module is almost always better value than development.
A custom integration is justified when your processes don't fit the standard:
- you have your own accounting system or a custom-built website;
- products are sold across several channels at once and stock has to be split between them by rules;
- prices must be recalculated automatically from purchase cost, exchange rate and delivery cost;
- you need Kaspi sales analytics in one dashboard with your other channels.
In such cases a ready-made module starts to get in the way: you pay for a subscription and still work half by hand.
How development works
Work starts with an audit. We look at where products, prices, stock and barcodes are stored now, who changes them and how, and where orders come from. Very often it turns out that the "main" spreadsheet exists in three versions held by three employees, and you first have to agree which one is correct.
Then we design the exchange: what data goes to Kaspi, what we pull from it, how often, and what to do on error. For example, what happens if a product runs out in the warehouse at the very moment an order comes in for it.
Next come development and tests on a small part of the catalog. Only when everything works on 20-30 products is the integration switched on for the whole range.
The last stage is monitoring: the system must report by itself if an export failed or Kaspi returned an error, rather than waiting for a customer to notice.
What's next
A Kaspi integration pays off when manual work starts causing cancellations, pricing errors and lost orders. For simple cases a ready-made module is enough; non-standard processes need a custom integration.
Sources
- Kaspi Guide - what the Magazin API is
- Kaspi Guide - how to start working with the API
- Kaspi Guide - working with orders via the API
- Kaspi Guide - seller terms and conditions
- Kaspi Guide - XML price list
- Kaspi Guide - Kaspi Kassa and the National Product Catalog
- SelSup - specifics of integrating with Kaspi
- Habr - experience integrating an online store with Kaspi
- Bizmedia - National Product Catalog, July 2026
- Digital Business - Kaspi delivery rates from 2026