1C Integration with Kaspi and Marketplaces
Export from 1C to Kaspi: prices and stock update on their own, while Kaspi orders and sales arrive in 1C as documents. Ozon, Wildberries and other marketplaces where you sell connect the same way.
- Kaspi stock matches 1C, no more selling items you do not have
- Kaspi orders land in 1C as documents, with commission and delivery
- One 1C database for every marketplace and your own website
- Exchange log and an alert on failure
1C Kaspi integration starts at 600,000 tenge and takes three to four weeks. Each additional marketplace, such as Ozon or Wildberries, connects in one to two weeks.
Why you need 1C Kaspi integration
As long as Kaspi stock is edited by hand, selling an out-of-stock item is only a matter of time.
For many companies in Kazakhstan, Kaspi.kz has become the main sales channel. Yet accounting lives in 1C, and between the two sits an employee who exports the price list, edits stock in the seller account and copies orders back. With dozens of orders a day that is a full-time position, and every mistake costs store rating.
1C Kaspi integration removes the manual layer. Prices and stock go from 1C to the marketplace automatically, orders arrive in 1C as documents, and Kaspi sales are recorded in accounting together with the marketplace commission. Staff handle exceptions instead of retyping data.
A separate pain of manual work is promotions and price changes. When a supplier raises the purchase price, the price in 1C changes immediately, but on Kaspi it changes whenever someone gets to it. A few hours of sales at the old price on a best-seller can easily wipe out a whole week's margin. Automatic export closes this gap too.
The main result for the business: the stock a buyer sees on Kaspi matches what is actually in the warehouse. Cancellations for "out of stock" go away, and with them the penalties and the drop in seller rating.
What is exchanged between 1C and Kaspi
Two-way exchange, each direction can be switched on separately.
| Data | Direction | Frequency |
|---|---|---|
| Products and links to Kaspi listings | from 1C | on change |
| Prices, including by city | from 1C | from every 5 minutes |
| Stock by warehouse and pickup point | from 1C | from every 5 minutes |
| New orders | into 1C | on a schedule or instantly |
| Order statuses and cancellations | both ways | on change |
| Sales and marketplace commission | into 1C | daily |
All changes go through 1C. If an employee changes a price directly in the seller account, the next exchange returns it to the 1C value. This is a deliberate rule: otherwise, a month later nobody can say which price is correct.
The setup fits your process. Some companies only need automatic export of prices and stock; others need the full cycle: order, warehouse reservation, shipment, closing documents. You can start small and add directions in stages.
Export from 1C to Kaspi: prices and stock
The first and fastest effect of the integration.
Export from 1C to Kaspi is built around product matching. Every item in 1C has to be linked to its marketplace listing by the seller SKU. If SKUs in 1C are kept carelessly, matching becomes the first and most labor-intensive stage, and we include it honestly in the estimate.
For new products not yet on the marketplace, we prepare the data for creating listings: name, attributes, barcode, brand. Listing moderation stays on Kaspi's side, but with correct data from 1C it goes faster and with fewer rejections.
Then 1C builds an up-to-date price list with prices and stock, and the marketplace picks it up on a schedule. We configure which warehouses count as available for Kaspi, which price type to use, and whether a safety stock is needed so you do not sell the last unit already promised to a wholesale client.
For products that must not be sold on the marketplace, such as dealer-exclusive items, we add a flag in 1C and they simply stay out of the export. You can switch a product off on Kaspi with a checkbox in the product card, without opening the seller account.
For companies with locations in several cities, we set up prices and stock by city: a buyer in Astana sees availability at the Astana warehouse, not the total stock across the country.
Kaspi sales in 1C: orders, commissions, returns
The second half of the integration, without which accounting drifts away from the money.
A new Kaspi order arrives in 1C as a sales order with its contents, price, delivery method and pickup point. The item is reserved in the warehouse right away and stops showing up in stock on other marketplaces and the website.
Kaspi sales are recorded in 1C together with the marketplace commission, so margin in reports is real, not gross. Cancellations and returns put the item back into stock and close the reservation with no staff involvement.
For accounting it matters that Kaspi revenue matches what lands in the bank account. So we record sales in a way that can be reconciled with marketplace payouts, with discrepancies shown in a separate report rather than hunted down by hand at month end. The banking side is covered by 1C bank integration.
A step-by-step connection guide is in how to connect 1C to Kaspi step by step (in Russian). If you also need a Telegram bot for Kaspi buyers, it is built by our team at Applications.kz.
1C integration with marketplaces: Ozon, Wildberries and others
One 1C database, several marketplaces, no stock conflicts.
With several marketplaces, the main risk is shared stock. An item sells on Kaspi but still shows as available on Ozon. 1C marketplace integration solves this with one rule: only 1C counts stock, and each marketplace gets its share.
Stock is allocated by rules you set. For example, best-sellers go to every marketplace in full, while expensive and rare items go only to Kaspi and your own website. Or part of the stock is reserved for wholesale clients and marketplaces see the rest. Rules are changed in 1C without a developer.
We connect Ozon, Wildberries and other marketplaces that offer a seller API. Each marketplace after Kaspi costs less, because product matching and stock logic are already in place: 1-2 weeks per connection.
Every marketplace has its own request rate limits. We account for them in the exchange schedule, otherwise the marketplace starts rejecting updates at the worst possible moment, usually during a sale. The Applications.kz team covers these limits in detail in its article on marketplace API restrictions.
How the connection works
The usual path from the first call to a working exchange.
- Review. Your 1C configuration, number of products, warehouses, price types, which marketplaces you sell on and how you move data today.
- Product matching. We compare SKUs in 1C with Kaspi listings, find mismatches and duplicates, and decide together how to fix them.
- Development. Export and order import in an extension on a copy of the database. The standard configuration stays on vendor support.
- Trial period. The exchange runs while an employee checks the results in parallel. Usually one week.
- Launch. We switch on the schedule and manual copying stops.
- Handover. Documentation, a guide to the error log and a contact in case of failure.
During the trial period we show a discrepancy report: how many items were exported, how many the marketplace accepted, which were rejected and why. It shows that the exchange is ready to run on its own, rather than asking you to take our word for it.
The whole path for one marketplace usually fits into 3-4 weeks. It takes longer only if the product catalog needs serious cleanup.
Work on the live database begins only after you have accepted the result on the copy.
How much 1C Kaspi integration costs
The price depends on the number of products, warehouses and how tidy your SKUs are.
| Task | Timeline | Price |
|---|---|---|
| Export of prices and stock to Kaspi | 3-4 weeks | from 600,000 ₸ |
| Full cycle: orders, statuses, sales | 4-6 weeks | by estimate |
| Each additional marketplace | 1-2 weeks | by estimate |
| SKU and duplicate cleanup before launch | from 1 week | from 350,000 ₸ |
| Exchange support and monitoring | monthly | from 80,000 ₸/month |
Payment is by stage: product matching, export of prices and stock, order import, sales and commissions. You accept each stage on a copy of the database and only then pay for the next. Any prepayment is credited toward the first stage.
The number of 1C users does not affect the price. The state of your catalogs does: if half the products have no SKU and some are entered twice, we tidy up first. More on the 1C data migration and cleanup page.
Common mistakes with do-it-yourself connections
What we see when we come in after an off-the-shelf module or a freelancer.
- Total stock across all warehouses. Kaspi gets items that are physically in another city or already being shipped to a wholesaler.
- No safety stock. The last unit sells in two channels at once and one of the sales is cancelled.
- Exchange without a log. The export stopped a few days ago and you learned about it from customer complaints.
- Commission ignored. Revenue looks good in reports, but the real Kaspi margin turns out several times lower.
- Edits to the standard configuration. The module is built directly into the standard configuration, and after a 1C update the exchange stops working.
Another frequent finding: duplicate products in 1C, so one Kaspi listing gets stock from only one of the copies. From the outside it looks like an item that is "there one minute, gone the next". The cause only shows up when the catalog is reconciled.
We close each of these gaps at the design stage, not after the complaints.
Who this integration is for
The sign is simple: someone copies Kaspi orders and stock by hand.
Stores with a hundred or more items that sell on Kaspi and in their own shop. Without integration, stock in the two channels drifts apart every day.
Fast-turnover sellers whose best-sellers run out within a day. Update frequency is decisive here: with a once-a-day exchange, by evening Kaspi shows items you no longer have.
Distributors and wholesalers who added Kaspi as an extra channel. The key is not to sell stock reserved for wholesale orders.
Companies with warehouses in several cities that need prices and stock by city. For complex warehouse logic there is a separate service, warehouse automation in 1C (in Russian).
If you also run your own online store, we connect it in the same setup so 1C distributes stock to every channel by one rule. More on the 1C website integration page.
Why work with us
We own the whole exchange and leave you the source code.
We program 1C and also build websites and apps, so we see the exchange from both sides. When something fails, there is no need to figure out whether 1C or the marketplace is to blame: we check the log and fix it.
We work remotely with all of Kazakhstan: Almaty, Astana, Shymkent, Karaganda and other cities. We connect to a copy of the database through access you control.
We do not sell a boxed module that you have to adapt yourself. The exchange is built around your warehouses, price types and reservation rules, and then extends easily when you join a new marketplace or open a warehouse in another city.
The customization is an extension, so 1C updates normally. Source code and documentation are handed over to you. Price and timeline in writing before we start, payment by stage, any prepayment credited toward the first stage. For exchanges that sales depend on, we offer support with daily log checks.
FAQ about 1C Kaspi integration
Timelines, prices and how the exchange works.
How much does 1C Kaspi integration cost?
Export of prices and stock from 600,000 ₸ and 3-4 weeks. The full cycle with orders, statuses and sales is estimated after reviewing the database.
How often is Kaspi stock updated?
On a schedule from every 5 minutes. We choose the frequency based on sales speed and marketplace limits.
Will Kaspi sales reach 1C with the commission?
Yes. Sales are recorded together with the marketplace commission, so margin reports show the channel's real profit.
Can Ozon and Wildberries connect to the same 1C?
Yes. After Kaspi, each additional marketplace takes 1-2 weeks because product matching and stock logic are already in place.
Our products have no SKUs. Is that a problem?
It is solvable. First we match and clean the catalog, a separate stage of a week or more. Without it the exchange will make mistakes.
Which 1C configurations do you support?
Trade Management, UNF, Integrated Automation, Retail and ERP for Kazakhstan. Industry solutions after a review.
What happens when 1C is updated?
The exchange is built as an extension, so the standard configuration updates normally. Under a support plan we check the exchange after every update.
Can we start with stock export only?
Yes, that is a common first stage. Orders, statuses and sales are added later as separate stages, with no rework.
More 1C services
Related tasks that usually go together.
1C integration
Exchange with your website, CRM, app and bank.
Data migration and cleanup
SKUs, duplicates and barcodes before the exchange goes live.
Warehouse automation
Bin locations, scanners and stocktaking (in Russian).
1C API
HTTP services and OData for external systems.
1C developer
Custom 1C development priced per task.
1C support
Exchange monitoring and fixes on a subscription.
Send a request
Describe the task: we reply within one business day and quote before any work starts.