1C Integration with Marketplaces Kaspi, Halyk Market, Wildberries, Ozon
We connect 1C to the platforms where you sell: stock and prices leave your books automatically, orders come back into the database, and if the exchange stops, you find out before your customers do.
- Stock and prices from 1C on a schedule
- Marketplace orders straight into 1C
- Several platforms from one database
- Exchange log and error notifications
1C integration with a marketplace starts at 600,000 tenge for the first platform, with a timeline of three to four weeks. Each additional platform is connected in one to two weeks.
Why connect 1C to marketplaces
Uploading stock by hand works while you have few products and one platform.
A seller with one platform and a hundred products can update stock by hand. When there are more products and two or three platforms, manual work turns into errors: you sell what you do not have, the price on the platform is outdated, an order gets lost between the seller account and 1C. Each such error means a cancellation, a fine or a lower rating.
Integration makes 1C the single source of truth. Stock and prices go to the platforms automatically, orders arrive in the database, and the warehouse handles them like any other order.
There is a second reason: money. Platform commissions, delivery, returns and fines eat into the margin, and without data in 1C it is hard to see how much each platform really earns. When orders arrive in the books automatically, these calculations happen on their own.
The third reason is scale. Connecting a new platform or a new warehouse is much easier when the exchange is already built on 1C. There is no need to hire a separate person for each seller account.
Integration helps small sellers too. Even with a hundred products, one stock error on Kaspi can cost a cancelled order and a lower store rating, and restoring a rating takes longer than setting up the exchange once.
Platforms we work with
Marketplaces where companies from Kazakhstan sell.
- Kaspi.kz. Export of products, stock by warehouse and prices, import of orders and their statuses. Details on the 1C to Kaspi export page.
- Halyk Market. Stock, prices, orders.
- Wildberries and Ozon. For sellers working on the Kazakhstan and Russian storefronts of these platforms.
- Other platforms and your own website. If a platform has an API or a feed format, we connect it the same way.
The list of platforms keeps changing: new storefronts appear, old ones change their APIs. We track the changes and update the exchange if a platform changes its format, as part of support.
What goes from 1C and back
Two-way exchange without intermediate tables.
From 1C to the platform: stock net of reservations and by warehouse, prices of the chosen price type and, if needed, product cards. You can set rules: do not export an item if stock is below a threshold, keep a separate price for each platform.
From the platform to 1C: orders with items, prices and delivery details, status changes, cancellations and returns. The order arrives in 1C as a regular customer order, and the warehouse picks it by its usual rules.
We set up reservations separately. When a marketplace order arrives in 1C, the goods are reserved and stock on the other platforms drops immediately. This protects against the last unit being sold on two storefronts at once.
For returns we import return documents and record them in the warehouse, so stock becomes available for sale again after a return.
Product matching
The most labor-intensive part of any connection.
The platform has its own product identifiers, and 1C has its own. Before launch we match them by article number, barcode or code and show what was not found. New products are then linked automatically by a set rule, and disputed cases go into a list for review.
If the item catalog has many duplicates, we advise cleaning it before connecting, otherwise stock on the platform will differ from real stock.
If product cards on the platform are created from 1C, matching happens by itself. But often cards were already created by hand in the seller account, with different names and article numbers. Then we prepare a mapping table, check it with the sales manager and load it, after which the exchange runs without manual work.
When there are thousands of products, matching is semi-automatic: the system suggests pairs by article number, barcode and similar name, and the manager confirms the disputed ones. This is faster than manual work and more reliable than fully automatic linking.
Exchange monitoring
An exchange that quietly stops is worse than manual uploads.
Every exchange session is written to a log: what was sent, what was received, where the error is. If a platform did not respond or rejected data, the person responsible gets a notification in Telegram or by email. The problem is solved in minutes instead of being discovered a day later from a customer complaint.
We take platform API limits into account: request frequency and batch sizes. The exchange is built so it does not hit the limits.
The log is stored in 1C and can be opened at any time to see when and what data went to the platform. This helps resolve disputes with the platform, for example when an item was sold while its stock was zero.
How the integration works technically
Standard 1C stays on vendor support.
We place the exchange logic in a configuration extension: scheduled jobs, export rules, the log and product matching. For platforms that need an always-available address, we set up a small exchange service between 1C and the platform API. The 1C database itself is not exposed to the internet directly.
More about our approach to integrations on the 1C integration and API for 1C pages.
If the company has several 1C databases, for example one per legal entity, we build the exchange so each platform gets stock from the right database. If there is one database and several platforms, the logic and log are shared, while export rules are set per platform.
All platform API keys are kept in protected settings, not in code, and can be changed without a developer.
How the connection works
The first platform takes three to four weeks, the next ones go faster.
- Review. Configuration, warehouses, price types, platform seller accounts.
- Product matching. A list of mismatches and linking rules.
- Development on a database copy. Export, order import, log.
- Test period. The exchange runs while the manager checks the results.
- Launch and notifications. We switch on the schedule and alerts.
During the test period the exchange runs at full capacity, but the manager compares data on the platform with the books and notes differences. Usually all the quirks surface within a week, after which the exchange runs without human involvement.
After launch we hand over a short guide: where to see the log, what to do in case of an error and how to add a new product to the platform.
Price and timeline
We give an exact price after reviewing the database and the platforms.
| Work | Timeline | Price |
|---|---|---|
| First platform: stock, prices, orders | 3-4 weeks | from 600,000 ₸ |
| Each additional platform | 1-2 weeks | per estimate |
| Stock and price export only | 1-2 weeks | from 350,000 ₸ |
| Exchange support | monthly | from 80,000 ₸/month |
The price depends on the platform, the number of warehouses and products, and whether order import is needed or only stock and price export. You can start with one platform and a simple export, then add orders and new storefronts.
Configurations we work with
Standard 1C:Enterprise 8.3 configurations.
1C:Trade Management, 1C:Small Business Management (UNF), 1C:Integrated Automation, ERP and 1C:Retail. If you have an industry-specific or heavily customized configuration, we look at the database first. 1C customizations for trading are described on the UNF customization and Trade Management customization pages.
If you do not have 1C and keep your books in another system or in spreadsheets, we first help you move to 1C and then connect the platforms. More on the 1C implementation page.
Specifics of Kaspi and other Kazakhstan platforms
Each platform has its own rules, and the integration must respect them.
Kaspi.kz works with stock by points of sale, and for a seller with several warehouses it is important to distribute goods among them correctly. We set which 1C warehouses correspond to which points and how reservations for already accepted orders are counted. We also handle order statuses so the sales manager sees in 1C that an order is accepted, picked, handed to delivery or cancelled.
Halyk Market and other platforms have their own formats and limits. For some, a feed with stock and prices is enough; others need a full API exchange with order import. We look at what each platform supports and propose a scheme that needs no manual work.
For sellers entering Wildberries and Ozon, it is important to separate warehouses, prices and commissions by platform. We set up separate price types and export rules so the price on each platform accounts for its commission and logistics.
Sales analytics by platform
When orders arrive in 1C, you can see which platform really makes money.
After connection, all marketplace orders sit in one database together with website and offline sales. We build reports showing revenue and margin for each platform including commissions, delivery and returns, product turnover on each storefront and items that often run out.
Such reports help decide which products to list on which platform, where to keep a separate price and where to buy more. Reports are built on the data composition system (SKD) and can be sent to management on a schedule. More on the 1C reports page.
With high sales volume it helps to set up notifications: about an item that is out of stock in the warehouse but still listed on a platform, about orders that take too long to pick, about a sharp drop in sales of an item. All of this is done in the same database, without separate analytics services.
We also help with typical exchange errors sellers run into: stock is exported without reservations and the platform sells goods that are already reserved; the wrong price type is exported; orders are duplicated on repeated import. We close each of these with exchange rules and checks in the log.
Frequently asked questions about 1C integration with marketplaces
About platforms, price and exchange reliability.
How much does 1C integration with a marketplace cost?
The first platform with stock, prices and orders starts at 600,000 ₸ for 3-4 weeks. Stock and price export only starts at 350,000 ₸.
Can Kaspi and Halyk Market be connected to one database?
Yes. Several platforms work from one database, and each can have its own prices and export rules.
How often is stock updated?
On a schedule, usually every few minutes, within the platform's API limits.
What happens if the exchange stops?
The person responsible gets a notification in Telegram or by email, and the log shows the cause of the error.
Does 1C need to be taken off vendor support?
No. The exchange logic sits in an extension, and the standard configuration updates normally.
Will marketplace orders reach 1C automatically?
Yes, as regular customer orders, with statuses, cancellations and returns.
Can we set different prices on different platforms?
Yes. Each platform gets its own price type in 1C that accounts for commission and logistics.
What if we have several warehouses?
We set which 1C warehouses correspond to which points or warehouses on the platform and take reservations into account.
Send a request
Describe the task: we reply within one business day and quote before any work starts.