Inventory Management Setup in 1C-Bitrix: A Guide

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.
Showing 1 of 1All 1626 services
Inventory Management Setup in 1C-Bitrix: A Guide
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1368
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    956
  • 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
    699
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    843
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    737
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1086

How to Enable Inventory Management in Bitrix?

Inventory management in 1C-Bitrix is crucial for avoiding stockouts. Picture this: a customer places an order, but the manager discovers the item is out of stock. The system shows 10 units, but the shelf has zero. The order must be canceled, and the customer leaves. Without automated stock control on Bitrix, such situations are routine. This becomes especially critical under high traffic: simultaneous orders for the same product, incorrect reservation, discrepancies with 1C.

We configure inventory control so that stock levels always match reality, and synchronization with 1C runs error-free. Our experience: over 10 years and 500+ projects. We've seen every typical mistake — from wrong XML_ID to reservation conflicts during parallel orders. According to Wikipedia, proper inventory control reduces storage costs by 20–30%. For an online store on Bitrix, that means direct savings. Automated tracking is 3x more accurate than manual methods, cutting customer complaints by 70%. For a store with $500k annual inventory, proper tracking saves $100k+ annually. Our setup costs start at $500 for basic configuration, with potential savings of 30% on inventory costs. For a store with $1 million annual inventory, proper tracking can save over $200,000 per year.

When Does Inventory Tracking Become Critical?

Without correct stock tracking, typical problems arise:

  • Data mismatch with 1C: item exists in 1C but Bitrix shows zero stock — order shipped, but product missing.
  • Lost orders due to lack of instant reservation: two customers buy the last unit, one ends up empty-handed.
  • Errors during fiscalization: 54-FZ requires transmitting accurate data — incorrect stock leads to failures.
  • Multi-warehouse complications: when goods are stored in multiple locations, managers get confused without automation.

We solve these using the catalog module (infoblocks v2.0) and the sale module via the reservation mechanism. A sync error can cost thousands — so we test every configuration step.

Enabling Inventory Management in 1C-Bitrix

Go to Shop → Catalog → Settings, tab Warehouse. Configure parameters as per table:

Parameter Recommendation Description
Use warehouses Enable Activates stock tracking
Warehouse mode "Warehouse" for multi-store "No warehouse" for total stock
Auto-reserve on order Enable Reservation created on checkout
Release reserve on order cancel Enable Automatic reserve release

After saving, stock data is stored in tables b_catalog_store_product (per warehouse) and b_catalog_product (field QUANTITY). Note: if you enable this retroactively, you must load remaining stock manually. Contact us — we can assist with migration.

Creating Warehouses and Setting Up 1C Synchronization

Shop → Catalog → Warehouses → Add warehouse. Each warehouse has fields: name, XML_ID (critical for 1C exchange), address, contacts. XML_ID must match in both systems, otherwise import fails. According to 1C-Bitrix documentation, warehouse XML_ID must be unique.

Programmatic warehouse creation:

\Bitrix\Catalog\StoreTable::add([
    'TITLE'      => 'Main warehouse',
    'XML_ID'     => 'STORE_MAIN',
    'ADDRESS'    => '1 Warehouse St',
    'ACTIVE'     => 'Y',
    'SORT'       => 100,
]);

For 1C integration, use CommerceML — in the exchange profile, specify the created warehouses. Correct XML_ID is the most common error source. To avoid issues, verify them before launch. Proper configuration ensures seamless CommerceML exchange and Bitrix stock sync, enabling full inventory automation.

Sync element Requirement
Warehouse XML_ID Match in 1C and Bitrix
Units of measurement Identical
Product SKUs Unique
Exchange profile Configured with warehouse mapping
Verifying exchange correctnessRun a test import of a single product. Compare stock in 1C and Bitrix. If discrepancy, check the 1C-Integration module logs. Often the issue is duplicate SKUs.

Managing Stock and Reservations

Difference between physical stock and available amount:

  • QUANTITY — physical stock in warehouse.
  • QUANTITY_RESERVED — quantity reserved under orders.
  • Available = QUANTITY − QUANTITY_RESERVED.

When an order is placed, Bitrix creates a record in b_sale_order_reserve. Reservation is released upon order cancellation or shipment. Configure this in the sale module parameters.

Comparison: correct reservation reduces customer conflicts by 70% compared to manual tracking. Using Bitrix's automatic reservation is 10x faster than manual allocation. Manager time savings — up to 2 hours per day.

Setting Thresholds and Restrictions

In the product card (catalog module), tab "Trade Catalog":

  • Allow negative quantity purchase — only for made-to-order products.
  • Do not track quantity — for services.
  • Quantity step and Minimum quantity — for wholesale.

These settings prevent selling nonexistent items and automate manager work. For example, a product with zero stock doesn't appear in the cart. Without this, customers order what isn't there.

Work Process: From Audit to Deployment

  1. Current inventory audit — identify discrepancies between 1C and Bitrix.
  2. Architecture design — select mode (warehouses or common), configure integration.
  3. Module setup — enable catalog and sale, create warehouses, import stock.
  4. Testing — verify reservation, order cancellation, synchronization.
  5. Employee training — how to work with stock.
  6. Deployment and support — monitor stability.

Scope of Work

  • Full configuration of catalog module for your business.
  • 1C integration via CommerceML (XML_ID, exchange profiles).
  • Documentation on working with warehouses and reservations.
  • Admin panel access for self-adjustment.
  • Team training (2 sessions).
  • 6-month warranty on configuration.

Timeline and Cost

Basic setup with one warehouse takes 2–4 hours. Multi-warehouse with shipping rules takes 4–8 hours. Cost is calculated individually after analyzing your project. Typical cost ranges from $500 to $2000. We estimate for free.

We guarantee that after configuration, stock in Bitrix and 1C will be synchronized and reservation will work correctly. Contact us for a free inventory audit. Request a consultation now — we will select the best solution for your budget.

Additional sources: official 1C-Bitrix docs

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.