Bitrix: implementation and integration

Popularleader of the paid CMS segment in the RuNet: easy to hire developers and pull ready-made integrations from the Marketplace

Out of the boxThe catalog, cart, orders, and 1C exchange work without building an e-commerce engine from scratch

AI-readyThe REST API is wrapped in an MCP server — the agent reads the catalog, stock and orders as tools

In the registryA listing in the domestic software registry satisfies import substitution requirements

Industry solutions

What you can build on 1C-Bitrix

Retail and DIY Large online store with a catalog of millions of SKUs Highload blocks for attributes, composite cache for peak traffic, stock exchange with 1C

Manufacturing and B2B B2B portal with personalized prices and terms for counterparties Two-way CommerceML exchange with 1C, customer account, and orders at contract prices

Distribution A single catalog source for the website, marketplaces, and the app The catalog is published via REST API and a bus, and frontends consume it independently

State-owned companies and regulated industries A corporate website built on software from the domestic registry Bitrix from the registry, content info blocks, access control, and change auditing

Services and media A content portal with forms, mailings, and a customer account Standard edition, content infoblocks, integration with CRM and analytics via the API

FMCG and retail chains Omnichannel storefront with synchronized stock across locations Warehouse stock exchange from 1C, recommendations and semantic search on top of the catalog

Electronics and appliances Store with rich product cards and AI-generated descriptions AI wrappers for copy and meta tags, recommendations, agent MCP access to the catalog

Capabilities

1C-Bitrix capabilities

1C (accounting): the source of truth for products, prices, stock, and ordersESB / data bus: routing and transformation between 1C, Bitrix and external systemsBitrix: catalog, cart, checkout, storefront contentREST API / webhooks: exposing the catalog and orders externallyHeadless frontend and mobile app: consume the API, independent of CMS templatesAI layer: content generation, semantic search, recommendations, MCP access to the catalogExternal systems: CRM, marketplaces, analytics, payment, and logistics servicesCorporate memory: architecture and API contract documentation for transferability

Bitrix handles the storefront and checkout, but does not become the only source of truth. The catalog comes from 1C, orders and events are distributed across systems through a bus, and AI and external channels connect via API, without direct integrations inside the monolith.

Built-in two-way exchange with 1C via CommerceML 2.x

products, prices, stock, orders and counterparties sync without building a separate connector

Catalog, cart, orders, and discounts out of the box

Launch an online store without building a core e-commerce engine from scratch

Highload blocks for large reference catalogs

attributes and custom data across millions of records run faster than regular infoblocks

Composite cache and performance dashboard

lower load on PHP and the database, spotting bottlenecks under peak traffic

REST/SOAP API and webhooks

The catalog and orders are available to external systems, mobile apps, and headless frontends

Ready-made editions for every scale (Standard to Enterprise)

the license scales with the project without a platform migration

CIS Software Registry

compliance with import-substitution requirements for state companies and regulated industries

A large base of integrators and solutions in the Marketplace

standard tasks are covered by ready-made modules, and hiring contractors is predictable

Approach

How we implement 1C-Bitrix

Minimal core modification

We don't fork or patch the 1C-Bitrix core. 1C-Bitrix stays on a standard, updatable version — we move business logic into separate microservices alongside it, so platform updates don't break your customizations.

International Standards, Not Homegrown Hacks

Where a mature international solution exists, we use it instead of inventing our own protocol or platform. Before writing code, we study how the problem is already solved in the industry.

Transferability

The solution is loosely coupled and documented: it can be handed over between teams and contractors without rewriting. You are not tied to us.

AI compatibility

1C-Bitrix in an AI stack

Content generation

AI writes and optimizes product card copy, descriptions and SEO meta tags; the Marketplace has wrapper modules for GPT/GigaChat/YandexGPT

Semantic search and recommendations

The catalog from info blocks is fed into a vector index, which powers recommendations and semantic search

MCP access to the catalog

The REST API is wrapped in an MCP server, and the agent reads products, stock and orders as tools without touching the core

Agentic development on top of the repository

a deployed agent edits templates and components from a skill library instead of manual edits for every task

AI outside the monolith

models and agents live in separate services and talk to Bitrix over the API — a CMS update does not break the AI layer

Context 2026

What changed in the market

Composable / headless commerce

the frontend is decoupled from the engine, Bitrix stays the backend for the catalog and orders via the REST API

AI generation of content and meta tags

The model creates product cards and SEO copy, and a person reviews them, which is now the norm rather than an experiment

Semantic search and recommendations

semantic search and personalized recommendations on top of the catalog are becoming a baseline expectation

MCP and agent access to data

The catalog and orders are exposed to agents as tools through MCP on top of API, without touching the core

Import substitution and stack sovereignty

demand for a CMS from the CIS Software Registry in the public sector and regulated industries

Honestly

Pros and cons

Pros

Out-of-the-box 1C exchange via CommerceML, saving on connector development and giving 1C-based businesses predictable operations
Leader of the paid CMS segment for online stores in the RuNet: a large pool of integrators, ready-made solutions and hiring
A mature e-commerce engine (catalog, cart, orders, discounts) and load-ready tools such as Highload blocks and composite cache
Listed in the domestic software registry, meeting import substitution requirements
REST/SOAP API and webhooks let you move the frontend and AI into a separate layer instead of keeping everything in the monolith

Cons

Licensing model: a one-time edition purchase plus paid renewal of updates. From November 1, 2025, the discounted renewal is 30% of the license price when arranged within the window (90 days before and up to 15 days after expiry), otherwise renewal is at full price; in 2026 prices go up
A heavy monolith with a specific core API — without architectural discipline it's easy to end up with vendor lock-in and fragile point integrations
Tied to the vendor's ecosystem and versions: PHP 8.2+ required from 02/01/2026, updates depend on an active license
Customization requires knowledge of Bitrix specifics (info blocks, components, core API), which raises the entry barrier and creates dependence on specialized talent
Weak position in the international market: outside the RuNet the ecosystem and support are limited

Blog