Integrating 1C with your website: how products, prices, stock and orders are exchanged
How 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.

If your Kazakh entity keeps its books in 1C, the catalog, prices and stock live there, while sales happen on the website. With a handful of orders, someone copies them by hand: reads the order on the site, creates a document in 1C, updates the stock on the site. Then volume grows, a second warehouse and Kaspi appear, and manual copying becomes the main source of errors: the site sells items that are gone, prices drift apart, and orders get lost between the inbox and 1C.
Integrating 1C with the website removes that manual layer. This article explains how the exchange works: which data goes in which direction, what integration mechanisms the 1C:Enterprise 8 platform offers, how to choose between them and where the exchange usually breaks. We also cover what is specific to Kazakhstan: the Kazakhstan editions of 1C, electronic invoices (ESF) and Kaspi as a second sales channel. If you want an estimate for your own database straight away, see the page on integrating 1C with websites and marketplaces.
First decide which system owns each type of data
The most common reason an exchange breaks is not technology but two systems fighting over the same field. A price is changed on the site, the nightly export from 1C arrives and restores the old one. A manager corrects a customer's phone number in 1C, and the site overwrites it with whatever the buyer typed. So before choosing a mechanism, write a simple table: each type of data has exactly one owner, and only the owner changes it.
| Data | Owner | Direction | When to send |
|---|---|---|---|
| Products: name, SKU, unit | 1C | 1C → site | On change |
| Variants: size, color, volume | 1C | 1C → site | On change |
| Prices by price type | 1C | 1C → site | On change |
| Stock by warehouse | 1C | 1C → site | Often, on a schedule |
| Photos and descriptions for buyers | Usually the site | Site, or 1C → site | On change |
| Orders | Site | Site → 1C | Immediately or every few minutes |
| Order statuses | 1C | 1C → site | When the status changes |
| Payments | Bank or cash register | To 1C and the site | When the payment arrives |
| Customers | Created on the site, maintained in 1C | Both ways | With the order |
Photos and descriptions are often easier to manage on the site: a product card in 1C is built for accounting, while buyers need copy, several photos and SEO. If you have thousands of products and the photos already sit in 1C, you can export them from there. What matters is that the decision is made once and written down.
Ways to connect 1C and a website
The 1C:Enterprise 8 platform has several integration mechanisms. Below are the ones that show up in website projects, from the most ready-made to the most flexible.
Standard exchange over the CommerceML protocol
1C and 1C-Bitrix publish an open website exchange protocol. Documents travel in CommerceML 2, an XML standard for commercial data. 1C always starts the exchange: it calls the site over HTTP, uploads the catalog, offers, prices and stock by warehouse, then collects new orders from the site and syncs their statuses. Files can be sent whole or in parts, and zipped if the site supports it.
On its online store exchange page, 1C names the products where this exchange is built in: UNF (company management), Integrated Automation and Trade Management. The same page says the exchange is set up with a wizard, runs on a schedule or on demand and sends only what changed since the previous run, and that the catalog can be exported with filters and images. On the website side the protocol is supported by 1C-Bitrix, WooCommerce, Shop-Script and a number of other CMSs.
When it fits: a standard configuration and one site on a CMS with a ready module. When it gets in the way: the configuration has been customized, the order logic is unusual, or there are several channels. The format is rigid, and anything that does not fit has to be written on top.
Automatic REST interface (OData)
The platform can generate a REST interface for the whole application on its own. It uses OData version 3.0, returns Atom/XML or JSON and exposes almost all main objects: catalogs, documents, registers, constants. The interface is published to a web server from the Designer. Among its use cases 1C explicitly lists integration with websites and online stores.
The upside is a fast start: products, prices and stock can be read with almost no changes to 1C. The downside is that the site becomes dependent on the internal structure of your database. Rename a field or update the configuration, and the site's queries stop working. That is why we mostly use OData for reading, and write orders through a separate method where 1C itself validates and posts the document.
HTTP services: your own API inside 1C
HTTP services are an API the developer defines inside the configuration: URL templates, methods and handlers written in the 1C language. According to 1C, they are simpler for clients to work with than SOAP web services and can carry less data. For the website this means a clear contract: "give me changed stock", "accept this order", "return the status". Inside 1C anything can change as long as the contract holds. An HTTP service can be added as an extension without touching the main configuration, which keeps updates simpler.
When it fits: a customized 1C, several storefronts, high reliability requirements. The cost: you need a 1C developer and tests on a copy of the database.
Web services (SOAP)
The platform can both publish and call web services. They are chosen for websites less often, usually when the other side already speaks SOAP: a bank, a parent company's ERP, an industry system.
Files and Excel
The simplest route: 1C drops a file into a folder or onto a server on a schedule, and the site picks it up. It works for a small catalog with rare changes, but carrying orders back this way is awkward and errors surface late. The Kaspi price list works on the same principle: the XML file can be generated in 1C and given to Kaspi as a link. More in our article on Kaspi Marketplace and 1C.
An intermediate service
When there is more than one channel (the site, Kaspi, a CRM, a warehouse in MoySklad), a dedicated integration service sits between 1C and the storefronts. It pulls data from 1C, converts it to each platform's format, keeps an order queue, retries failed sends and keeps a log. 1C then talks to one predictable client instead of five. This is how our API integration projects are built.
How to choose
| Situation | What we usually choose |
|---|---|
| Standard 1C, site on a CMS with an exchange module, one channel | Standard CommerceML exchange |
| Prices and stock need to appear on the site quickly | OData for reading |
| Customized 1C, several storefronts, orders must not be lost | HTTP service plus an intermediate service |
| Small catalog, prices rarely change | A file on a schedule |
| The other system only works over SOAP | Web service |
The mechanisms above belong to the 1C:Enterprise 8 platform. If the books are still kept in 1C 7.7, the method is chosen separately. For example, in the Hotu-As project we connected a loyalty app to ATOL cash registers and 1C 7.7, and accounting sees every point earned and spent.
How often to exchange
Frequency depends on what an error costs. Send orders immediately or every few minutes: the customer is waiting for confirmation and the warehouse for a picking list. Update stock more often the faster an item sells and the fewer units are on the shelf. Prices and the catalog only need to go out when they change.
Do not push the whole catalog every time. Send only what changed since the last exchange: that is how the standard 1C exchange works and how a well-built API should work too. A full export of thousands of products every few minutes loads both 1C and the site and sooner or later runs into timeouts.
Keep a buffer on fast-moving items: show stock on the site minus one or two units, especially if the same item sells on Kaspi. Kaspi fetches the price list by link once every 60 minutes if the file has changed, so the last unit can sell in two places at once.
Where the exchange breaks
- Duplicate products. The site matches products by name, a manager fixes a typo, and a second product appears. Match on a permanent identifier from 1C, not on the name.
- SKUs that don't match. The site uses the supplier's SKU, 1C has its own code. Marketplaces have their own rules too: for example, a SKU in the Kaspi price list is made of digits and Latin letters, is at most 20 characters long and must be unique.
- Units and packs. 1C counts boxes, the site counts pieces. Without a conversion factor, stock and prices will be off many times over.
- Variants. Size and color are stored as characteristics in 1C and as product variants on the site. Plan the mapping before the first export.
- Deleted and archived items. An item is marked for deletion in 1C but still shows on the site with stock. Agree on what the site does with such items.
- Reserves and warehouses. Which warehouses to show buyers, whether to subtract stock reserved for other orders, what to do with goods in transit.
- 1C updates. After a configuration update fields change and the exchange quietly stops. Test updates on a copy of the database together with the exchange.
There is one defence against all of this: an exchange log. It shows what went through, what failed and why, and the person in charge is notified if an order gets stuck. Without a log you hear about the failure from a customer.
What is specific to Kazakhstan
Configurations. 1C releases editions for Kazakhstan: 1C:Accounting 8, Trade Management, Retail, UNF and Integrated Automation 8 for Kazakhstan, among others. Their documents and reporting are local. Descriptions of the standard exchange on 1C websites are often written for the Russian editions, so what is actually available in your database is checked in the database itself, not in someone else's manual.
ESF. VAT payers issue invoices electronically in the IS ESF system (Article 492 of the Tax Code). A convenient setup: an order from the site becomes a document in 1C, and the invoice is issued from 1C, not from the site. How the connection works is on the ESF page, and when an invoice is needed for online sales is covered in the guide on ESF in online sales.
Kaspi. For many stores in Kazakhstan this is the second channel, sometimes the first. The master data is the same: products, prices and stock from 1C. How a Kaspi connection differs from a website connection is covered in the article on Kaspi Marketplace and 1C.
Customers and deals. If a sales team handles inquiries, a CRM joins the site and 1C. How to choose one with 1C, Kaspi and WhatsApp in mind is covered in our article on CRM in Kazakhstan.
How we build the connection and what it costs
- Review. We look at your 1C configuration and find out what is typed in by hand today and where orders get lost.
- Exchange design. We fix the ownership table, directions, frequency and mechanism.
- Database copy. We build and test on a copy and touch the live database only at launch.
- Log and alerts. Built in from the first version, not after the first failure.
- Launch and support. We switch over, watch the first days of the exchange and fix what comes up.
A standard connection between two systems starts at 270 000 ₸. If you do not have a site yet, an online store with online payments starts at 800 000 ₸. With several storefronts or a heavily customized configuration, we quote after the review and fix the price in the contract. Our work comes with a 6-month warranty, and the code and 1C changes stay with you. More on the 1C integration page.
What we do on this topic
Short and to the point.
Can 1C be connected to a website without a developer?
Sometimes. If the configuration is standard and the site CMS has a module for the 1C and 1C-Bitrix exchange protocol, the exchange is set up with a wizard inside 1C. If 1C is customized or there are several storefronts, you will need a developer.
Which is better: the standard CommerceML exchange or your own API?
The standard exchange is faster to launch on a standard 1C with one site. Your own API on HTTP services is more reliable when the configuration is customized, there are several channels and orders must not be lost. Companies often start with the standard exchange and move to an API as they grow.
How often should stock be updated on the site?
Send orders immediately or every few minutes, and stock more often the faster items sell. Send only changes, and keep a buffer on the last units, especially if the item also sells on Kaspi.
Will an ESF be issued for a website order?
It is easiest to issue it from 1C: the website order becomes a document in the accounts, and the invoice goes to IS ESF from 1C. Who must issue an ESF and when is a question to check with your accountant against the Tax Code of Kazakhstan.
How much does 1C and website integration cost?
A standard connection between two systems starts at 270 000 ₸. With several storefronts or a heavily customized 1C, we quote after reviewing the configuration and fix the price in the contract.
Read also
Automation10 min readIntegrating Kaspi Marketplace with 1C: price list, stock and orders without manual workHow 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.
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.
CRM and ERP8 min readDoes your business need a full ERP, or is a system for your own processes enough?Many companies do not need a heavyweight ERP with a long rollout. They need a system for their processes next to 1C. How it works and when a big ERP is worth it.Shall we discuss your project?
We will tell you what it costs and how long it takes. The price is fixed in the contract.