Accurate Inventory Sync Between Online Store and 1C-Bitrix

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    694
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    830
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    732
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1075

Accurate Inventory Sync Between Online Store and 1C-Bitrix

Incorrect stock levels lead to overselling

Overselling occurs when stock data is outdated. Proper 1C-Bitrix inventory management solves this. We've encountered situations where an online store on 1C-Bitrix shows 10 units of an item, but the physical warehouse is already empty. The customer places an order, we forward it to 1C, and it's rejected. Overselling eats up to 20% of revenue, and losses can exceed 200,000 rubles monthly. Standard synchronization via CommerceML runs every 15–60 minutes. That's not enough for high-volume sales: discrepancies accumulate. Our engineers solve this with webhooks and real-time document flow.

What synchronization approaches exist?

Let's compare two main methods:

Method Update frequency Latency Suitable for
CommerceML Scheduled (15-60 min) High Small online stores
Webhooks Real-time Seconds High-volume stores

CommerceML is the standard exchange protocol with 1C, documented in CommerceML. It's reliable but not suitable for scenarios where stock changes quickly. Webhooks update data in 1-2 seconds — 30 times faster than CommerceML. Our experience — over 50 projects with webhooks — shows that payback occurs within six months.

How we implement real-time updates?

To minimize discrepancy — integrate the cash register with Bitrix in real time. Each offline sale immediately triggers a webhook to Bitrix. Implementation steps:

  1. Create a PHP endpoint that accepts JSON from the cash register.
  2. Validate the data and find the product by SKU.
  3. Create a warehouse document of type 'S' (sale) via DocumentTable.
  4. Post the document by calling conduct() — this automatically updates stock in b_catalog_store_product.
  5. Invalidate the product cache.
Webhook implementation example
// /local/ajax/pos-sale-callback.php
$data = json_decode(file_get_contents('php://input'), true);

foreach ($data['items'] as $item) {
    $product = \CCatalogProduct::GetByID($item['sku']);
    if (!$product) continue;

    // Decrease stock on specific warehouse
    \Bitrix\Catalog\StoreProductTable::update(
        ['PRODUCT_ID' => $item['product_id'], 'STORE_ID' => $data['store_id']],
        ['AMOUNT' => new \Bitrix\Main\DB\SqlExpression('AMOUNT - ?', $item['quantity'])]
    );

    // Recalculate total stock in b_catalog_product
    \CCatalogProduct::RecalcQuantity($item['product_id']);
}

RecalcQuantity() recalculates b_catalog_product.QUANTITY as the sum across all warehouses in b_catalog_store_product. After that, the product cache must be invalidated — via BXClearCache(false, '/catalog/') or tagged cache. We guarantee update time under 2 seconds.

How to reserve stock for online sales?

A common practice for multi-channel stores: allocate a separate 'online warehouse' in b_catalog_store, whose stock is only for the online store. Physically, goods may be in one warehouse, but logically separated.

Offline sales decrease the 'physical warehouse', while online orders are reserved from the 'online warehouse'. At night, 1C replenishes the online warehouse from the physical one according to a set proportion.

Physical warehouse: 100 units
Online quota: 30% = 30 units → stored in b_catalog_store_product (STORE_ID = online_store)
Offline quota: 70% = 70 units → not exposed to Bitrix

This eliminates overselling but reduces available stock for online sales. We tailor the proportion individually based on sales statistics.

How document flow works?

In Bitrix, the catalog module supports warehouse documents: \Bitrix\Catalog\Document\DocumentTable. Document types: A — receipt, S — sale, M — transfer, R — return.

When posting a document via \Bitrix\Catalog\Document\DocumentController::conduct(), stock in b_catalog_store_product is automatically recalculated. This is the correct way to update stock — through documents, not direct UPDATE.

For offline sales: on receiving a webhook from the cash register, we create a document of type S with sale items and post it. This ensures full movement history and accurate inventory accounting.

Inventory reconciliation

Discrepancies between 1C and Bitrix are inevitable. It's crucial to detect them. Once a day we run a reconciliation agent:

// Get stock from 1C via REST API
$bx1cItems = get1cQuantities();

// Compare with b_catalog_store_product
foreach ($bx1cItems as $sku => $qty) {
    $bitrixQty = StoreProductTable::getList([
        'filter' => ['PRODUCT.XML_ID' => $sku],
        'select' => ['AMOUNT'],
    ])->fetch()['AMOUNT'] ?? 0;

    if (abs($bitrixQty - $qty) > 0) {
        logDiscrepancy($sku, $bitrixQty, $qty);
    }
}

The discrepancy log allows you to decide: correct Bitrix to match 1C (1C as master) or flag an integration issue. After implementation, the client saves up to 500,000 rubles per year by eliminating overselling and manual reconciliation. Annual savings average 300,000 rubles.

What's included in the turnkey 1C-Bitrix setup

In each project we provide:

  • Audit of current inventory accounting scheme and integration points
  • Selection of optimal synchronization protocol (CommerceML or webhooks)
  • Endpoint development for cash register and POS terminal webhooks
  • Document flow setup: receipt, sale, transfer, return
  • Implementation of stock reconciliation agent with discrepancy logging
  • Staff training on the updated system
  • Detailed documentation on integration and settings
  • Technical support for one month after launch

Investment starts from 150,000 rubles.

Stages and timelines

Stage Duration Result
Analysis 2-3 days Integration scheme, synchronization method selection
Design 3-5 days Technical specification, prototype
Development 5-10 days Webhooks, documents, reconciliation agent
Testing 3-5 days Validation on real data, bug fixing
Launch 1-2 days Deployment, staff training

Timelines — from 2 to 4 weeks. Investment calculated individually based on complexity. Payback — 4–6 months. We are certified 1C-Bitrix specialists with over 10 years of experience. We guarantee that after setup, stock discrepancies will not exceed 0.1% provided stable communication channels.

If you notice stock discrepancies in your store, order an audit and get a synchronization plan. Contact us for a consultation.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

Edition For Whom Key Limitation
Start Business cards, landing pages No infoblocks 2.0, no trade catalog
Standard Corporate sites No e-commerce module
Small Business Small stores 1 price type, 1 warehouse, no 1C exchange
Business Medium stores, B2B Multi-warehouse, multicurrency, CommerceML
Enterprise Highload, cluster Web cluster, CDN, multisite

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis

Add to .settings_extra.php as above.

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Task Timeline
Installation on virtual hosting 2–4 hours
Installation on VPS with stack configuration 1–2 days
Installation on dedicated with architecture design 2–5 days
SSL + email + cron + security 1–2 days
Backup and monitoring setup 0.5–1 day

Post-Installation Checklist

  1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
  2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
  3. Security Scanner — check for typical vulnerabilities.
  4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
  5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

  • Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
  • Installed and activated license of the required edition.
  • SSL certificate, email settings, cron and backups.
  • Documentation: all configuration parameters, access credentials, cron tasks.
  • Content manager training: how to log into admin panel, add products, upload images.
  • Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.