How long does it take to set up the exchange?

A typical “catalog + orders” exchange on clean configurations takes one to two weeks including testing. Composite schemes with customized 1C, multiple databases or a site + CRM + 1C chain take longer; we name the timeline after discovery and fix it in the contract.

Bitrix already has a free built-in exchange — why pay for setup?

The stock module is a mechanism, not a ready solution: it works great when both systems are stock and the data structures match. In practice almost every company has customized 1C, its own product logic and its own accounting rules. Our job is to design the data mapping and configure the exchange so it works on your data, not on a demo database.

Will the exchange slow down the website?

No. Regular exchange sends only changes and runs in the background; a full reconciliation runs on a schedule during low-load hours. If the site slows during export, that is a sign of a misconfigured exchange — and that is exactly what we fix.

How safe is this for our 1C database?

The exchange is initiated from the 1C side over a secure channel — the site has no direct access to the database; the systems run on different servers. Even if the site is compromised, the accounting database stays unreachable. We also set up logging so any export can be reviewed and rolled back.

Our 1C was heavily customized by a developer. Is that a problem?

Not a problem — input data. During discovery we study the customizations and determine how they affect the exchange: some we account for in configuration, some need a small adaptation on the 1C side. All of that goes into the estimate before start — working with customized configurations is familiar to us.

Can the site catalog differ from the 1C product directory?

Yes — that is normal practice. We design the storefront structure for the buyer and SEO, and map it to nomenclature with matching rules in the exchange. The 1C directory does not need to change.

We already have an exchange set up, but it glitches. Will you take it on?

Yes — we regularly take apart third-party exchanges. From the logs we find where sync breaks — duplicates, lost properties, a stuck export — fix the root cause and set up monitoring. If the current scheme was poorly designed, we show what should be redone and why.

We have a site, but 1C is only being rolled out. Where should we start?

You can go the other way: export the catalog from the site, help structure nomenclature in the new database and start regular exchange. After that 1C becomes the source of truth — all changes are made there.

What do you need from us to start the work?

1C version and configuration, the Bitrix site or Bitrix24 portal URL, a description of what should sync, and sample data — a few product items with prices and stock. For discovery we ask for access with minimal rights; afterwards we send an exchange scheme and an estimate.

Who will monitor the exchange after go-live?

We set up failure alerts and hand over instructions to your staff — typical issues are resolved on the spot in minutes. If you want to offload monitoring entirely, we can connect the exchange to our technical support with monitoring and response by SLA.

Bitrix24 and site integration with 1C

We configure two-way exchange between 1C, a Bitrix site, and Bitrix24: catalog, prices, and stock go to the site automatically; orders and payments return to accounting without manual entry. We also repair existing exchanges that “suddenly stopped working.”

Discuss integration View pricing

Why connect the site and 1C

While the site and accounting system live apart, the least reliable interface between them is a person with a keyboard. A manager manually moves orders from the site into 1C, a content manager updates site prices from a week-old export, and a buyer orders stock that ran out long ago. Every one of these steps costs staff time and risks an error that costs money and reputation.

Integration removes the manual link. Data is entered once — in 1C, where it belongs — and the system distributes it to the storefront: names, descriptions, photos, SKUs, price types, stock by warehouse. Orders, buyers, and payments travel back. Staff stop being “data couriers,” and the site always shows the truth.

Important caveat: integration is not “checking a box in a module.” Every company has its own 1C configuration, product structure, and accounting rules, so exchange is always designed for the specific project. That stage determines the difference between an exchange that runs for years and one that breaks every month.

What a tuned exchange delivers

A catalog without manual labor

A new product entered in 1C appears on the site with properties, price, and photos. Taken off sale — it disappears from the storefront. Content managers work on descriptions and promotion, not retyping the catalog.

Honest prices and stock

Buyers see current prices and stock by warehouse — not last week’s data. Fewer cancelled orders and “is it actually in stock?” calls — more trust and repeat purchases.

Orders land in accounting immediately

A site order is created automatically in 1C with the buyer, line items, and amount. The manager processes it in the familiar system, and statuses — confirmed, shipped, delivered — return to the site for the customer.

Documents without manual typing

Invoices, delivery notes, and acts are formed from order data — no retyping details or amount errors. For B2B clients, documents are available right in the customer account.

Online and offline in one system

With retail stores and a site on one database, a buyer can order online and pick up in-store — or the reverse. Stock is honest across channels; sales don’t compete with each other.

Less routine — lower costs

Double entry disappears; managers’ freed time goes to selling. The savings aren’t abstract: count how many hours a week your team spends moving data between systems.

Three integration directions

Exchange is set up between different system pairs — often one project combines all three directions.

The classic online-store link. From 1C to the site: catalog sections, products with SKUs, properties, images, price types, stock by warehouse, kits and bundles. From the site to 1C: orders, buyers, payments. We map structures — the site catalog doesn’t have to mirror the accounting nomenclature: the storefront is designed for buyers, and category–SKU links live in the exchange rules.

How exchange works technically

Change-based exchange, not “everything again”

After the initial full export, systems exchange only changes — every few minutes or on event. The site doesn’t slow during sync, and new orders reach 1C almost immediately.

A schedule for your accounting

A full catalog reconcile can run on a schedule — at night or in low-load hours. We tune frequency and contents to your work rhythm, not “whatever happened.”

Security and rollback

Exchange runs over a protected channel and is initiated from 1C — the site has no direct access to your database; the systems are physically separated. A bad export can be rolled back: we set up exchange logging and recovery points.

How setup works

Request and initial review

You describe the task: which site or CRM, which 1C, what should sync. We clarify details and agree on assessment access — with only the minimum required rights.

Configuration assessment

We study the 1C version and configuration, customizations, product structure, price types, and warehouses; on the site side — Bitrix edition, catalog, and installed modules. This is where nuances that break “quick” integrations surface.

Data map

We document what syncs which way: source of truth per field, category and property mapping, conflict and incomplete-data rules. We agree the scheme with you — it becomes the exchange documentation.

Estimate and agreement

After assessment we state the scope, cost, and timeline. If the configuration is non-standard, we honestly show which parts need custom work — no mid-project surprises.

Setup on a test environment

We deploy exchange on system copies and run test operations: catalog export, order transfer, stock updates. The live site and production database keep running as usual.

Test export and reconcile

We verify results on a control set: duplicates, lost properties, broken images, behavior on connection loss and incomplete export. We fix before launch — not after customer complaints.

Full exchange go-live

We run the initial full sync, enable regular change-based exchange, and watch the first cycles on real data.

Handover

We set up failure alerts, hand over instructions, and show responsible staff how to check exchange health and handle typical errors. You learn about problems from monitoring — not from a customer.

Typical situations clients bring

Integration isn’t always built from scratch — often an existing one needs repair or redesign. A few scenarios from practice.

Which configurations we work with

We set up exchange with the main inventory configurations: 1C:Trade Management, 1C:Our Company Management, 1C:ERP, 1C:Retail, 1C:Comprehensive Automation — both standard and customized. On the site side, standard exchange needs 1C-Bitrix Small Business or Business; if you have another edition or a custom site, we’ll propose an API approach. Exact version requirements are checked during assessment — if your configuration needs an update first, we’ll say so before work starts, with the cost.

Frequently asked questions

Tired of moving data by hand?

We’ll assess your 1C and site, design the exchange scheme, and launch sync with monitoring. Estimate after assessment — then it doesn’t change.