Why the integration is needed
Manual exchange between the site and 1C costs more than it seems: a manager retypes orders (typos included), stock is updated once a night at best, and a client who ordered "the last one" is told next morning it ran out. Prices drift between systems, discounts are applied unevenly, and the CRM never knows what happened after the invoice. Integration removes the whole class of problems: 1C stays the single source of truth for stock and prices, the site sells what really exists, orders reach accounting in seconds and buyers appear in the CRM as deals with full history.
What we connect
Four streams, both directions. Orders: from the site into 1C (and the CRM) with items, quantities, discounts and payment status. Stock and prices: from 1C to the site — balances per warehouse, price types and special offers, on a schedule or on change. Customers: contacts, companies and order history flow into the CRM, tagged with the source; deals move along the funnel as 1C issues invoices and payments. Documents: invoices and closing documents can be pushed back to the customer area. We work with 1C:Enterprise of common configurations — Trade Management, Accounting, ERP, UNF — and with Bitrix24 or amoCRM in the same loop.
How the exchange works technically
We choose the channel per configuration: native commerce exchange (CommerceML), REST/API OData, or file exchange as a fallback for restrictive hosting. The rules are explicit before a line is coded: what happens on a partial payment, who wins on a price conflict, how returns and cancellations travel, what the retry policy is when a side is offline. Every exchange writes to a log with a payload snapshot; errors raise notifications to a responsible person instead of dying silently in a cron. Before go-live the whole loop is tested on a copy of your accounting base — never on production.
Typical scenarios and nuances
Retail stores need fast stock so nobody buys a phantom item. B2B portals add personal prices per contract, credit limits and document flow. Manufacturers sync custom properties and reserve stock at order time. Franchises consolidate several warehouses and legal entities. Each scenario has known traps — rounding rules, unit measures, bundled items, partial shipments — and we carry this checklist into the project from day one. If your 1C was customized by another company, we audit the configuration first and coordinate changes with its maintainer instead of fighting it.
Cost and timelines
A typical website + 1C integration (orders, items, prices, stock) — from 60 000 RUB, 2–3 weeks. Adding a CRM to the loop — from 30 000 RUB. A B2B portal with personal prices — from 120 000 RUB. Complex accounting schemes (batches, characteristics, multi-warehouse) — estimated after the 1C audit. The price includes: the accounting audit, exchange setup, the log and notifications, testing on a copy, an integration passport and training of the responsible person. Exchange support — from 8 000 RUB/mo: monitoring, adjustments to accounting changes, help during 1C updates.
Why integration is built at ZXY
We build both ends: the site side and the exchange logic are ours, and we speak 1C fluently enough to audit configurations before touching them. Every project ships with an integration passport — channels, rules, error handling, contacts — so you are never hostage to one contractor. The log and notifications are mandatory, not optional: silent failures are the real enemy of e-commerce. And after launch we stay nearby: exchanges break when accounting changes, and a support plan turns those moments from emergencies into routine fixes.
