Integrating Kaspi Marketplace with 1C: price list, stock and orders without manual work
How the exchange between Kaspi Marketplace and 1C works: an XML price list with prices and stock, the order API, SKUs, warehouses, common failures and rollout.

Foreign companies selling in Kazakhstan often ask whether they can list on Kaspi.kz at all. Kaspi's own guide answers yes: a non-resident company can join the Kaspi.kz marketplace on the same terms as a local one, that is, it has to be a Kaspi Pay partner and have accepted Kaspi Pay payments on at least 20 days within the last two months (connection terms). Once the store is live, the next problem is operational. Orders arrive in the Kaspi seller cabinet, while the books, stock and invoices of your Kazakh entity are often kept in 1C, in one of its configurations for Kazakhstan.
Without an integration, someone copies new orders from the cabinet into 1C every morning, updates prices in Excel at noon and realises in the evening that the last unit sold in the shop is still "in stock" on Kaspi. One mistake turns into a cancelled order, and Kaspi counts cancellations caused by the seller in its quality metrics.
An integration removes the copying. But "integration" covers two different things, and mixing them up costs money. Below is how the exchange between Kaspi Marketplace and 1C actually works: what goes through the price list, what goes through the API, where it usually breaks and in what order to launch it. The Kaspi facts come from the Kaspi partner guide and were checked on 16 November 2026.
Two exchange channels, not one
The Kaspi.kz marketplace has two independent ways to talk to your accounting system, and they run in opposite directions.
| What moves | Channel | Direction |
|---|---|---|
| Prices, stock, availability per warehouse, pre-order | XML price list at a URL | From 1C to Kaspi |
| New orders, items, warehouse, statuses | Seller API | From Kaspi to 1C, statuses back |
| New product cards, barcodes | Products API | From your system to Kaspi |
Kaspi's guide recommends sending stock from an accounting system through the price list: the system exports an XML file to your server, and you enter its URL in the cabinet (stock section). Orders and their statuses go through the seller API. Among the systems a store can be integrated with, Kaspi names 1C explicitly (API basics).
Hence the first rule: connecting 1C to Kaspi is not one button but two jobs. Publish the catalogue and take in the orders.
The price list: how prices and stock get from 1C to Kaspi
The price list comes in two formats. Excel is for manual uploads: the file is processed and the catalogue updates within 15 minutes. But Excel is not available if your prices or pre-order periods differ by city, you have more than five warehouses, or your warehouses are not named PP1 to PP5. For data that updates by itself you need XML.
Automatic upload works like this:
- 1C generates an XML file with products, prices and stock on a schedule. Kaspi states that the file can be generated in 1C.
- The file sits on your server and opens at an http or https URL.
- In the web version of the seller cabinet, the URL goes into the automatic price list upload setting of the goods section.
- Kaspi fetches the file every 60 minutes if it has changed.
What the file holds for each product:
- SKU (sku): digits and Latin letters only, up to 20 characters, unique within the price list;
- name (model) and brand (brand);
- availability per warehouse: the warehouse code (storeId) from the warehouses and shops section of the cabinet, whether the item is available, the quantity in stock (stockCount) and a pre-order period in days, 30 at most;
- a price (price) for all cities, or prices per city (cityprices) with a city code.
Per-city prices and different pre-order periods per warehouse can only be set in XML, and only if the warehouses are in different cities. Warehouses in the same city get a single price and pre-order period.
Two details people tend to discover too late. If a product was added manually before, it has to be included in the price list, otherwise it is taken off sale. And products in the file that are not on sale yet land in the list of unrecognised, unlinked goods, where you have to put them on sale yourself. Details are in the price list section.
SKUs and warehouses: matching decides everything
Technically, generating XML from 1C is easy. The hard part is agreeing which item in 1C corresponds to which card on Kaspi. This is where most home-made exports stumble.
- A 1C item code is not always a valid Kaspi SKU. 1C codes may contain Cyrillic letters, hyphens or long strings. A Kaspi SKU is Latin letters and digits, 20 characters at most, so we often add a separate attribute or a mapping table.
- Sizes and colours. If 1C holds one item with variants and Kaspi has separate listings, each variant needs its own SKU.
- Warehouses. Each 1C warehouse you sell from on Kaspi is matched to a point code from the cabinet. A warehouse missing from the mapping is invisible on Kaspi.
- Price type. Decide which 1C price type goes to Kaspi, and separately whether you need per-city prices.
It pays to agree the mapping table once with whoever maintains the item catalogue in 1C, rather than investigate later why half the range is "unrecognised".
Orders: what the seller API gives you
The seller API works with a token. Only the head of the company can get it: in the web version of the seller cabinet, in the API token section of the settings, they generate and copy it. The token does not change, and anyone who holds it can see the orders and products in your cabinet. So it belongs in the integration settings, not in a messenger chat (how to get the token).
Through the API the integration can:
- fetch the order list, filtered by state (new, documents to sign, pickup, your own delivery, Kaspi Delivery, archive) and by creation date, up to 100 orders per page;
- accept an order: move it from APPROVED_BY_BANK ("the seller must accept") to ACCEPTED_BY_MERCHANT;
- read the order contents and the warehouse the buyer ordered from;
- generate a waybill to hand the order over to Kaspi Delivery;
- cancel an order with a reason;
- complete an order: the COMPLETED status is set with a code the buyer receives in the Kaspi.kz app.
On the 1C side it looks like this: a new Kaspi order appears as an order document with the buyer, items and warehouse, a manager picks it in the familiar interface, and the status goes back to Kaspi. Note that Kaspi's rules prohibit processing orders outside the seller cabinet, except through the API (seller rules). In other words, an API integration is the normal, permitted route, while retyping orders from the cabinet into Excel and then into 1C is not.
There is also a products API: it adds new products for sale (SKU, name, brand, category code, description, photo links, attributes), checks the upload result and attaches barcodes. It is useful for a large, fast-changing range. If new listings are rare, creating cards in the cabinet is simpler.
Stock: where it usually breaks
The gap between a sale and an update. Kaspi fetches the price list once every 60 minutes if the file has changed. If the same item also sells in a shop or on your website, the last unit can go twice within that hour. The cure is a buffer: export fewer of the last units than you hold, or take the listing down early.
Cancellations. What happens to stock after a cancellation depends on the delivery method (stock section). With your own delivery or pickup the quantity updates automatically. With Kaspi Delivery, stock is restored automatically while the order is new, awaiting signature, on pre-order or being packed. If the order is already being handed over or has been handed to Kaspi Delivery, you collect the item from the drop-off point and update the stock yourself. The integration has to mirror this in 1C, or the books and the storefront drift apart.
Stock counts are mandatory for many sellers. Sellers who joined the Kaspi.kz marketplace after 21 October 2025, or whose quality metrics sit at "Poor" or below, must state quantities. Others may skip them, but then they have to take an item off sale themselves when it runs out.
Rating. Kaspi sets quality requirements for sellers: a rating of 4 stars or more, seller-caused cancellations below 3%, delays in handing orders to Kaspi Delivery below 10%, and quality returns below 2%. Breaches can lead to restrictions up to termination of the partnership (why sellers get disconnected). Wrong stock hits cancellations first, so an accurate export is not a convenience but protection for the store.
A ready-made module or an integration built for your 1C
1C partners sell ready-made Kaspi exchange modules, and for a standard configuration with one warehouse they are often enough. A custom integration makes sense when:
- your 1C configuration has been modified and the module does not install without changes;
- you have several warehouses, prices differ by city, or you need pre-orders;
- you have your own website besides Kaspi and stock has to be shared (we cover linking 1C to a website in the article on 1C and website integration);
- not everything lives in 1C, for example the warehouse runs in MoySklad and customers in a CRM;
- after a sale you need closing documents, for example an electronic invoice in the ESF system.
If you are still choosing where to sell, start with the channels: Kaspi or your own online store and how to open an online store in Kazakhstan. How 1C works as the hub for every storefront is described on the 1C integration page.
How we launch the integration
- Review. We look at the 1C configuration, warehouses, cities, price types and how Kaspi orders are handled today.
- Mapping table. 1C SKUs, warehouses and cities against Kaspi codes, agreed with whoever maintains the catalogue.
- Price list. We set up scheduled XML generation and publication at a URL, then check the upload in the cabinet: what was recognised and what was not.
- Orders. We connect the API with your token and test on a copy of your database, then on real orders under supervision.
- Exchange log. You can see which order or product failed and why, and the person in charge gets a notification.
A standard link between two systems, for example Kaspi and 1C, starts at 270 000 ₸. With more warehouses and storefronts, or a heavily modified 1C, we quote after the review and fix the price in the contract. More on the cost of a 1C and Kaspi integration. Our work comes with a 6-month warranty, and the code and access stay with you. We also work with older 1C versions: in the Hotu-As project we connected a loyalty app to 1C 7.7.
What we do on this topic
Short and to the point.
How often does Kaspi update prices and stock from 1C?
With automatic upload, Kaspi fetches the XML price list from your URL every 60 minutes if the file has changed. An Excel file uploaded by hand is processed within 15 minutes. That is why it is worth keeping a buffer on the last units of an item.
Can stock be sent to Kaspi through the API?
For automatic stock updates from an accounting system, the Kaspi guide recommends an XML price list at a URL. The seller API handles orders and their statuses, and the products API adds new cards.
Who can get the Kaspi API token?
Only the head of the company, in the API token section of the settings in the web version of the seller cabinet. The token does not change and gives access to the orders and products of the cabinet, so share it only with your technical specialist.
How much does a Kaspi and 1C integration cost?
A standard link between two systems starts at 270 000 ₸. With more warehouses, cities or storefronts, we quote after reviewing your 1C configuration and fix the price in the contract.
Will a ready-made module do instead of a custom integration?
For a standard 1C configuration and one warehouse, often yes. A custom integration is needed if 1C has been modified, there are several warehouses and cities, or a website and CRM share stock with Kaspi.
Read also
Automation12 min readIntegrating 1C with your website: how products, prices, stock and orders are exchangedHow to connect 1C with a website in Kazakhstan: standard CommerceML exchange, OData and HTTP services, what to sync and how often, and where the exchange breaks.
Automation8 min readScattered services hold back growth: how to bring a business into a single systemThe CRM does not know about the warehouse, the warehouse about the website, the website about Kaspi. What scattered systems cost and how to connect them.
Automation10 min readBusiness process automation: what to automate first and how to count the payoffWhich processes to automate first, when CRM robots are enough and when you need a 1C and Kaspi integration, how to count the payoff and avoid common mistakes.Shall we discuss your project?
We will tell you what it costs and how long it takes. The price is fixed in the contract.