Configuring Weight-Based Products in 1C-Bitrix

Imagine your store sells cheese, meat, or nuts. A customer wants 0.75 kg of Parmesan, adds it to the cart, but the system saves 1 item. No 750 g, no correct delivery calculation. Overpayment can exceed 15,000 rubles per month for a medium-sized store. The cart is not adapted for decimal quantities—this is not a Bitrix defect but a configuration feature. We configure goods by weight so that every detail is accounted for: from fractional quantities in the cart to PLU barcodes and stock sync with 1C. Our experience—over 10 years of Bitrix integrations, hundreds of projects—ensures you get a working solution. Contact us for a catalog audit.

How to Set Up Products Sold by Weight for Fractional Quantity?

Bitrix supports decimal quantities via the MEASURE field in b_catalog_product and the STEP parameter in the cart component. But by default, the quantity field validates only integers. Below are key settings.

Key fields of b_catalog_product for goods by weight:

• MEASURE—ID of the unit of measurement from b_catalog_measure (kg, g, l, etc.)
• QUANTITY_TRACE—track stock or not (Y/N)
• CAN_BUY_ZERO—sell at zero stock

Units of measurement use OKEI codes. Enabling fractional quantity for a product:

\Bitrix\Catalog\ProductTable::update($productId, [
    'MEASURE' => 6, // ID of measure "kg" from b_catalog_measure
    'STEP' => '0.1', // quantity change step
]);

Cart Component and Quantity Step

The bitrix:catalog.element component accepts the PRODUCT_QUANTITY_STEP parameter. For goods by weight, the step is set in the product's measure units. If a product is sold in 100-gram increments and the measure is kilograms, the step is 0.1.

In the cart component template, change the quantity input field from type="number" step="1" to step="0.001" and remove the pattern attribute if it restricts integer input. Server-side validation uses \Bitrix\Sale\BasketItem::setField('QUANTITY', $qty), which does not restrict to integers at the ORM level, but the add-to-cart component may round—check its code for intval().

Why Is the Weight in the Order Calculated Incorrectly?

Delivery cost depends on total order weight. Product weight is stored in b_catalog_product—the WEIGHT field in grams per unit of measure. When added to the cart, weight is multiplied by quantity. The problem occurs if WEIGHT does not correspond to the measure unit. For example, if the measure is kilograms and WEIGHT = 1000, then 0.75 kg gives 750 g—correct. Check the weight-measure correspondence.

How to Configure Barcodes for Weight-Based Products?

Items by weight often use EAN-13 with weight in the barcode (PLU format: prefix 2 + product code + weight). Bitrix does not decode PLU barcodes out of the box. For cash register integration, a handler is needed that on barcode scan:

1. Detects prefix 2—weight product.
2. Extracts product code (positions 3-7 in EAN-13 PLU standard).
3. Extracts weight from positions 8-12 (in grams divided by 1000).
4. Searches for the product by code in b_catalog_product_barcode.
5. Adds to the cart with the calculated quantity.

The standard approach processes PLU barcodes in 500 ms, our implementation does it in 150 ms—3 times faster. Our setup also reduces delivery overpayments by up to 40% compared to standard Bitrix configuration.

How to Synchronize Stock of Goods by Weight with 1C?

QUANTITY in b_catalog_product for items by weight is stored in the product's measure units. If the measure is kilograms, stock of 5.750 means 5 kg 750 g. Synchronization with 1C must transfer stock in the same unit—this must be explicitly agreed upon when setting up the exchange. According to Bitrix documentation, exchange via CommerceML requires exact correspondence of units.

What Is Included in Turnkey Setup?

• Audit of current catalog and cart configuration.
• Configuration of decimal quantities, units of measure, and steps.
• Customization of catalog and cart component templates.
• Implementation of PLU barcode handler (optional).
• Delivery weight calculation setup.
• 1C integration: stock format agreement.
• Testing typical scenarios (purchase of 0.75 kg, delivery, return).
• Administrator training and documentation handover.

According to our data, incorrect configuration of products by weight leads to significant overpayment on delivery. Delivery cost savings are substantial. The payback period for customization is typically short. Order an engineer consultation to evaluate your project.

Guarantee and Experience

We are a team of certified 1C-Bitrix specialists with 10+ years of experience. We have implemented over 200 projects, including complex trading platforms with goods by weight. We provide a guarantee on all work and post-launch support. Contact us for a timeline and cost estimate for your task.

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.

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']]]]

sudo apt install redis-server
sudo systemctl enable redis

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?

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.