Integrating 1C with a website starts from one rule: the books stay in 1C, and the website, client portal or CRM only show what is recorded there and send back what has to appear in it - orders, requests, payments. 1C is the most common accounting system in Russia. From it you usually take products, stock, prices, contracts and dates; back into it go orders and their statuses. When the same record is edited in two places, the books drift apart, so for each kind of data you decide in advance which system is the master.
What to take from 1C and what to send back
The first question we ask a client sounds dull: where is each figure kept today. Products and prices are almost always kept in 1C. Stock too. Contracts, licences and service dates sit in 1C if accounting or sales enter them. Client tickets, correspondence and managers’ tasks usually do not belong in 1C; they live in the portal or CRM.
| Data | Master record | Where it goes |
|---|---|---|
| Products, prices, stock | 1C | to the website or portal |
| Contracts, licences, dates | 1C | to the client portal |
| Orders and requests | website or portal | to 1C, status back |
| Invoices and payments | 1C | to the CRM, to the manager |
| Support tickets | portal | not sent to 1C |
The table looks obvious, but there is nearly always a disputed field. Who edits a product description: the merchandiser in 1C or the marketer on the website? If both edit the same field, one of the edits disappears at the next exchange. The fix is to split the fields: name, article number and price come from 1C and are read-only on the website, while the long description and photos are kept on the website and never go to 1C.
How the standard 1C website exchange works
The 1C company publishes an open website exchange protocol, developed together with 1C-Bitrix. The built-in export of standard 1C programs uses it. The exchange has two parts. The first sends the catalogue to the website, stock by warehouse or in total, or just prices and stock without product descriptions. The second passes website orders into 1C and keeps their statuses in sync.
A few details of the protocol that later shape a project:
- 1C starts the exchange. The website does not pull data itself; it waits for 1C to call it over HTTP. So how often prices and stock update is set on the 1C side.
- Data travels as CommerceML 2 files. This is XML describing products, groups, units of measure and tax rates.
- The website states its limits. Before an upload 1C asks whether the website accepts archives and the largest file it takes in one request. 1C splits a large catalogue into parts by itself.
- Every step gets an answer. The website replies “success”, “progress” (still loading, repeat the request) or “failure” with an error description.
The last point matters more than it seems. If the website silently swallows a broken file, 1C treats the exchange as successful, and the mismatch surfaces a week later when a buyer orders an item that is not there. So in any integration of 1C with external systems we agree up front who sees an exchange error and where.
The protocol suits an online shop well. For a portal where a client sees their contracts and dates it is not enough: that needs data a catalogue does not have.
Example: a customer portal with data from 1C:ERP
One of our current projects is a customer portal for an equipment supplier. It is under NDA, so the company is not named. The supplier keeps everything in 1C:ERP: what was sold to whom, which licences and service contracts a client has and when they end. Before the portal a client could only learn this through a manager: write, ask when a licence ends, and wait. Renewals and requests went through emails and calls.
In the portal the client sees purchased equipment, licences and technical support with their dates. The data comes from 1C:ERP and nothing is copied by hand, so the portal shows the same as the books. That is the first direction of the exchange - out of 1C.
The second direction is the client’s own actions. The client prices service and licence renewals by the supplier’s rates and places them in the portal. Support tickets and requests follow a route agreed with the supplier, and the client sees which step they are at. Output documents are generated from the supplier’s templates.
The work is split into four stages:
- The portal base and the link to 1C:ERP.
- Viewing data.
- Actions and sales: renewals, tickets, requests.
- Trial operation and launch.
The 1C link sits in the first stage for a reason. Until you know which fields 1C:ERP returns and in what form, drawing portal screens is premature. At each stage the client accepts the result on its own data rather than made-up samples, which quickly shows empty fields or old contracts nobody closed.
Exchange with 1C on a B2B marketplace
Another project is the system behind a B2B marketplace, also under NDA. Here 1C is one system among several rather than the centre. The catalogue, orders, warehouse, the path of every item by QR code and team tasks are kept in the system itself. Accounting exchanges data with 1C, while agency contracts, agent reports and acts are generated from templates and sent through electronic document exchange.
Hence a second conclusion: you do not have to push everything into 1C. The marketplace needs exact accounting, but accounting does not need an item’s path from incoming inspection to the pick-up point, so there is no reason to keep it in 1C. Only what accounting and reporting need goes to 1C.
One more detail from this project: the client chose the order of work. Catalogue, roles and the storefront link first, then item tracking and QR codes, then recommendations and the bot, and in the next stage documents, 1C and a mobile app. The 1C exchange does not have to come first if the warehouse matters more right now.
A ready-made module or your own link
For many tasks a ready-made solution exists, and it is worth checking first. For example, amoCRM integrates with 1C through a widget: according to amoCRM’s description, a manager issues an invoice straight from the deal, products, prices and counterparties come from 1C, the invoice goes to 1C at once, and when accounting marks payment or shipment the status updates in the CRM and the manager gets a notification. If that is exactly what you need - invoices and payments between CRM and accounting - there is no reason to build your own.
Your own link is needed when the data is non-standard. In the equipment supplier’s portal the client sees licences and service contracts with dates, and renewals are priced by the supplier’s rates. There is no off-the-shelf “portal with licences from 1C:ERP”, so the exchange is designed around these documents.
Questions that tell you whether a ready-made module will do:
- What data moves: only products, prices and orders, or contracts, dates and your own reference lists.
- Which system is the master for each field, and whether it is edited anywhere else.
- Whether the client acts on 1C data: renews, files a request, receives a document.
- Where the system runs: in the cloud or in a closed environment on the client’s server, as with the B2B marketplace.
If the answers are simple, take the ready-made option. If not, we connect 1C with websites, portals and CRMs around your data.
How not to break the books
Rules we keep in every project with 1C:
- One master record per field. A price changes in 1C, and on the website its field is read-only.
- Only what accounting needs goes back to 1C. An order, a request, a payment. Correspondence and internal tasks stay outside.
- An exchange error reaches a person. A “failure” reply under the protocol or a fault in your own link must reach whoever is responsible rather than sit in a log nobody reads.
- Testing on real data. As in the equipment supplier’s portal: the client accepts each stage on its own 1C:ERP data.
- Nothing extra is stored. On the B2B marketplace data the platform does not need for its work is not stored at all, which beats any protection.
Frequently asked questions
How much does integrating 1C with a website cost?
Our prices: websites from 50 000 ₽; CRM and accounting systems, automation, bots and AI, mobile apps, loyalty cards, integrations and promotion from 150 000 ₽. Any project takes from 1 month. The exact price depends on the task - we name it after reviewing it.
How often does a website exchange data with 1C?
Under the standard protocol 1C itself starts the exchange, so the schedule for prices, stock and orders is set on its side. For a custom link the frequency is chosen by the task: stock is usually needed more often than reference lists.
Can a website built on a site builder be connected to 1C?
Yes, if the builder accepts the 1C exchange protocol or gives programmatic access to its catalogue and orders. If it offers neither, a small layer between 1C and the website takes data from 1C and passes it on.
What should a client portal take from 1C?
What clients most often ask a manager about: purchased equipment or goods, contracts, licences and their dates, request statuses. In our portal for an equipment supplier this data comes from 1C:ERP, and the client sees it without a call.
Do amoCRM and 1C need custom development?
If you need invoices, payments and products inside a deal, amoCRM has a ready-made 1C widget. Custom work is needed when the data or actions go beyond invoices: contracts, dates, renewals, your own reference lists.
Who this fits
Suppliers of equipment, software and services whose accounting is in 1C and whose clients regularly ask about dates, renewals and request status. B2B marketplaces and distributors whose warehouse and documents are kept in their own system while accounting stays in 1C. If this sounds like your task, describe it in the form below: we will look at what data you have in 1C and what of it your clients need to see.







