1C and Kaspi: Synchronization of Products and Orders
In the first quarter of 2026, Kaspi marketplace's turnover increased by 41 percent year-on-year, with online sales reaching approximately 1.3 trillion tenge. By the end of 2024, around 737,000 active sellers were operating on the platform — more than a third of all active small and medium-sized businesses in the country. For thousands of Kazakhstani companies, the marketplace has ceased to be an additional channel and has become the main source of orders. And almost immediately after the sales growth, the same problem arises: stocks, prices, and orders exist in two places simultaneously — in the seller's cabinet and in the 1C accounting system — and it is no longer possible to reconcile them manually without errors.
At West Star Ltd, we regularly encounter this task among clients who trade on the platform and simultaneously maintain records in 1C. Experience shows that properly configured synchronization saves not only managers' time but also money — it eliminates overstocking, duplicate orders, and sales of out-of-stock items. In this article, we'll explore what exactly can be synchronized between 1C and the marketplace, how it works technically, where the real boundaries of automation lie, and what to consider before implementing integration.
WHAT IS SYNCHRONIZED
Integration between 1C and the seller's cabinet covers four data streams, and it's useful to separate them because they are configured differently.
The first stream is products and characteristics. The nomenclature is uploaded from 1C to the platform: names, categories, descriptions, attributes. This is a one-time or rare operation performed when setting up the assortment and adding new items.
The second stream is prices and stocks. This is the most frequent and critical synchronization. The price on the platform must match your accounting price, and the stock must reflect the actual availability in the warehouse. If an item runs out in 1C, the platform should know about it in minutes, not hours, otherwise, an order will appear that cannot be fulfilled.
The third stream is orders. A new order placed by a customer automatically enters 1C as a document. The manager does not need to manually transfer the order composition, address, and delivery method — everything is created programmatically.
The fourth stream is statuses. When an order is assembled, handed over for delivery, or completed, the status is synchronized in both directions. This allows all work with orders to be conducted within the familiar 1C interface without switching between windows.
HOW IT WORKS TECHNICALLY
The marketplace has its own programmatic interface — Shop API, current version v2. It operates over the HTTP protocol and provides data in JSON format. The seller generates an access token in the cabinet, in the settings section, and this token is included in each request as an authorization key.
Almost all exchanges revolve around several types of requests. The list of new orders is retrieved by a request to the orders endpoint with a filter by status and date. By the specific order code, you can get its composition — a list of items, quantity, price. Separate requests form an invoice for transferring the order for delivery. Products are added and updated either through the API or by uploading a price list as a structured file.
Order statuses are a finite set of values: new, requiring signature, pickup, delivery by the seller, delivery by the platform, archive. The integration logic boils down to regularly polling the API, finding orders in the desired status, creating documents for them in 1C, and returning updated statuses back.
On the 1C side, the exchange is usually implemented in one of two ways. The first is an external processing or extension that periodically accesses the API and parses the response. The second is an intermediate layer on the server side, which accesses the 1C database through its own web interface and the platform through its API, acting as a mediator between the two systems. We usually prefer the second approach: it does not interfere with typical configuration objects, does not hinder 1C updates, and is easier to maintain.
WHY MANUAL MODE STOPS WORKING
As long as the seller has fifty items and three orders a day, all this can be managed manually. Problems begin at scale. With a thousand items, the purchase price changes constantly with suppliers, and there is physically no one to synchronize it manually. The stock in the general warehouse is spent on several channels at once — retail, website, marketplace — and without a single source of truth, the seller either sells what is not available or plays it safe and keeps artificially low stocks, losing sales.
There is also a financial side. From January 5, 2026, the platform shows the commission excluding tax, and 16 percent VAT is charged separately. The commission itself depends on the category and in 2026 ranges from about 5 to 20 percent: for most categories, it's around 11 percent, for products — lower, for electronics and jewelry — higher. To understand the real margin for each item, you need to reconcile the selling price, commission, VAT, and cost from 1C in one table. Such a calculation is done manually with errors and delays — which means pricing decisions are made blindly.
SINGLE WAREHOUSE AND MULTIPLE CHANNELS
A separate task arises when the seller trades not only on one platform. A retail outlet, own website, second and third marketplaces — all claim the same physical stock. If each channel is synchronized with 1C by its own rules and at different times, desynchronization is inevitable: the same phone can be simultaneously sold in retail and reserved for an online order.
The solution here is one — 1C becomes the single source of truth for stocks, and all channels receive data from it, not from each other. Then after any sale, the stock is recalculated in the accounting system and only then distributed across all platforms. In our practice, it is the transition to a single warehouse, rather than the connection with a specific platform itself, that gives the main effect: overstocking disappears, losses from cancellations decrease, and customer trust grows because the declared availability matches the real one.
It is important to agree on priorities in advance. What happens when two sales claim the last unit of an item? Who reserves the stock first? These rules are embedded in the exchange logic at the design stage, and the more honestly they are described, the fewer conflicts arise in work.
LIMITATIONS AND WEAK POINTS
Integration is a tool, not magic. Let's honestly list where it falters.
-
Data quality in 1C. If the nomenclature is maintained carelessly — duplicate cards, empty categories, different units of measurement — integration will simply transfer this mess to the platform. Automation amplifies both order and chaos. Before implementation, cleaning up directories is almost always needed, and this is a separate task that is underestimated.
-
Exchange delays. Synchronization goes on schedule — once every few minutes, not instantly. During sales peaks, when stock depletes in seconds, even a five-minute window sometimes leads to an order for an out-of-stock item. This risk cannot be completely eliminated; it can only be narrowed and a buffer for stocks provided.
-
Changes on the platform side. The API and marketplace conditions change without your participation — as happened with the commission calculation in January 2026. Any change in formats or rules requires integration adjustments. This is not a one-time project set up and forgotten, but a system that needs maintenance.
-
Matching categories and attributes. The platform's category structure does not match the nomenclature structure in 1C. The initial matching of products with categories and mandatory characteristics is a manual and painstaking task that cannot be fully automated.
-
Not everything is available through the API. Some operations — for example, participation in promotions, separate storefront settings, working with disputes and returns — are still done manually in the cabinet. Integration covers the routine exchange of products and orders but does not replace the seller's cabinet entirely.
-
Dependence on a single data provider. When all accounting is tied to one sales channel, any failure or blocking hits the entire business. Integration does not reduce this dependence — on the contrary, it makes the connection tighter, and this should be consciously factored into risks.
WHERE TO START IMPLEMENTATION
Before ordering integration, it is worth tidying up the accounting. Ensure that in 1C, one item is one card with correct stock and understandable cost. Determine which warehouse is considered the source of stocks for the platform. Decide who and how often updates purchase prices. These organizational issues are more important than choosing a specific technical solution: without them, any automation will replicate problems rather than solve them.
Next, choose the integration method. Ready-made standard modules on the market cost from several tens of thousands of tenge and cover standard exchange scenarios. Custom development is more expensive but justified when the seller has a non-standard 1C configuration, several warehouses, its own pricing logic, or a connection with several sales channels at once.
PRACTICAL CONCLUSION
For a specialist who maintains records in 1C: start by organizing the nomenclature and stocks. Clean directories and a single source of stocks are the foundation without which integration will not be effective. Understand how the exchange via API is arranged to know where exactly errors are possible and how to catch them.
For the head of the sales or operations department: treat integration as an ongoing process, not a one-time project. Allocate resources for maintenance and response to changes on the platform side. Set up regular reconciliation of stocks and orders between systems so discrepancies are quickly found.
For the business owner: calculate the real margin taking into account the commission and VAT, not the selling price. Synchronization with the accounting system gives you a reliable picture of profitability for each item — and this is the basis for decisions about assortment and prices. And realistically assess the dependence on a single channel: the tighter the integration, the more important it is to have backup scenarios.
FREQUENTLY ASKED QUESTIONS
Can you completely abandon the seller's cabinet after integration?
No. The exchange of products, prices, stocks, and orders goes into automatic mode, but some operations — promotions, disputes, returns, separate storefront settings — are still performed manually in the cabinet. Integration removes routine but does not replace the cabinet entirely.
How quickly does the stock on the platform update after a retail sale?
This depends on the exchange schedule. Usually, synchronization occurs every few minutes. Instant second-by-second updates should not be expected, so during peak periods, it is reasonable to keep a small buffer for stocks.
Will integration break when updating 1C?
If the exchange is implemented through an external layer that does not change typical configuration objects, updates go smoothly. Solutions that deeply rewrite the typical configuration require more attention and rechecking when updating.
Does integration take into account the commission and VAT when calculating profit?
The exchange itself transfers orders and amounts, and the margin calculation is set up separately. It is important to reconcile in 1C the selling price, category commission, VAT charged on top, and cost — only then will you see the real profit for each item, not the revenue.