Middleware for 1C-Bitrix Integration: Development & Implementation

A website on Bitrix24, an accounting system in 1C, a CRM, and a warehouse management system—each pair requires its own integration. Six bidirectional links, six points of failure. An API change in one system breaks the rest. Each manual fix costs 20,000–40,000 RUB. We have encountered such scenarios many times and know how to radically simplify the architecture.

Middleware is a universal intermediary layer that receives data from any source, transforms it according to defined rules, and delivers it to the target system. Both systems only know about the middleware, not each other. This drastically reduces the number of failure points and makes each integration independent.

How Middleware Solves the Tight Coupling Problem

Middleware is an event bus through which all messages pass. Instead of "each-to-each" connections, you get a single entry point for all systems. Our experience: over 50 integration projects, with an average 70% reduction in failure points. Cost savings on maintenance — 200,000–300,000 RUB per year.

When Do You Need Middleware and Why Is It Better Than Direct Integration?

Direct integration is a tight coupling: change a schema in 1C — you have to rewrite the connector in Bitrix. Middleware isolates changes: only the connector to the system that changed needs updating. Modification time is reduced by a factor of 3–5. Middleware is essential with three or more systems, complex transformations, buffering needs, and full audit requirements.

Architecture and Implementation of Middleware

Option 1. PHP middleware inside Bitrix — a separate module in /local/modules/, receives requests via HTTP, transforms, proxies. Downside: tied to Bitrix infrastructure.

Option 2. Independent microservice (Node.js, Python FastAPI, Go) — lives separately, Bitrix is one of the sources/destinations. Advantage: scales independently, does not consume PHP resources.

Option 3. iPaaS platforms — Make (Integromat), n8n, Apache Camel. Visual building of transformations without code. Suitable for non-developers but limited with complex transformations.

PHP Middleware: Structure and Contracts

// Central middleware router
class IntegrationBus {
    private array $handlers = [];

    public function register(string $eventType, callable $handler): void {
        $this->handlers[$eventType][] = $handler;
    }

    public function dispatch(string $eventType, array $payload): array {
        $results = [];
        foreach ($this->handlers[$eventType] ?? [] as $handler) {
            try {
                $results[] = $handler($payload);
            } catch (\Throwable $e) {
                $this->logError($eventType, $payload, $e);
                $results[] = ['error' => $e->getMessage()];
            }
        }
        return $results;
    }
}

// Register handlers in init.php
$bus = IntegrationBus::getInstance();

// Order from site → CRM and accounting system
$bus->register('order.created', [CrmConnector::class, 'handleNewOrder']);
$bus->register('order.created', [AccountingConnector::class, 'createInvoice']);
$bus->register('order.created', [WarehouseConnector::class, 'reserveGoods']);

Data Transformation (Mapping)

Transformation is the most complex part of middleware. We use the Pipeline pattern:

class TransformationPipeline {
    private array $pipes = [];

    public function pipe(callable $transformation): self {
        $this->pipes[] = $transformation;
        return $this;
    }

    public function process(array $data): array {
        return array_reduce(
            $this->pipes,
            fn($carry, $pipe) => $pipe($carry),
            $data
        );
    }
}

// Example: Bitrix order → SAP format
$pipeline = (new TransformationPipeline())
    ->pipe(fn($d) => normalizeCustomerData($d))     // normalize customer
    ->pipe(fn($d) => enrichWithFiasData($d))         // add FIAS by address
    ->pipe(fn($d) => convertCurrencyFields($d))      // currency conversion
    ->pipe(fn($d) => mapStatusCodes($d, 'bitrix2sap'))  // status mapping
    ->pipe(fn($d) => validateSapSchema($d));          // SAP schema validation

Audit and Reproducibility

Every message is logged before and after transformation:

-- Audit table
CREATE TABLE integration_audit (
    id            BIGSERIAL PRIMARY KEY,
    event_type    VARCHAR(100),
    source_system VARCHAR(50),
    target_system VARCHAR(50),
    payload_in    JSONB,
    payload_out   JSONB,
    status        VARCHAR(20), -- success, error, retry
    error_msg     TEXT,
    duration_ms   INT,
    created_at    TIMESTAMP DEFAULT NOW()
);

On error in a downstream system, we replay the operation by audit record ID without resending the request to the source.

Case Study: Manufacturing Company

What's Included in Middleware Development?

On each project we deliver a complete set of results:

• Architectural documentation and contract descriptions
• Middleware source code with comments
• Access to repository and development server
• Deployment and configuration instructions
• Training for your team on middleware usage
• 6-month support after delivery

Process, Timelines, and Cost Estimation

We work in several stages:

1. Analysis — interviews with teams, studying system APIs. Result: data schema, contracts.
2. Design — architecture selection (PHP, microservice, iPaaS). Result: architectural documentation.
3. Core development — event bus, transformation pipeline, audit. Result: working middleware.
4. Connectors — one per system (1C, Bitrix, CRM, etc.). Result: documented connectors.
5. Testing — integration tests, load testing. Result: test protocol.
6. Deployment and support — monitoring setup, alerts, backups. Result: SLA, 6-month code warranty.

Indicative development timelines:

Exact estimates are given after a free audit of your infrastructure. Get a consultation for your project — our engineers will help determine if you need middleware and choose the optimal solution. Contact us for an audit.

Order an integration audit today—we will analyze your current architecture and propose options.

Our team consists of certified Bitrix specialists with 10+ years of experience.

Middleware definition according to Wikipedia

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.