Size Table Binding in 1C-Bitrix: Reduce Returns by 15–20%

Returns of clothing in online stores reach 30–40% — and 80% of those are due to incorrect size. A size table tied to a product reduces this indicator by 15–20%. But standard Bitrix does not store or output such data. We configure infoblocks and properties to tie the size grid to the product and category. Our experience: over 8 years we have implemented this for dozens of stores — one project with a catalog of 10,000 products reduced returns from 35% to 22% within two months after implementation. Savings on logistics and repackaging with an average order of 3,000 rubles and 10,000 orders per month amounted to over 4 million rubles (approx $50,000).

Why is a Size Table Critical for a Clothing Store?

Returns of clothing in online stores reach 30–40% — and most are due to incorrect size. A size table next to the trade offer selection directly reduces this indicator. Our experience: implementing such a table reduces returns by 15–20% within the first month. This pays for development costs through reduced logistics and repackaging.

Storage Architecture

Size tables are structured data tied to products or categories. In Bitrix, there are two places for this:

Property of infoblock type 'Bind to elements' — a separate infoblock 'Size Tables' is created, each element of which contains table data. Products reference the desired table via the PROP_SIZE_TABLE property. Advantage: convenient to reuse one table for hundreds of products of the same brand.

User field of type 'HTML/text' — the table is stored directly in the product property as HTML markup. Cheaper but does not scale: when changing the size grid, each product must be edited manually.

The first option is recommended. Structure of the 'Size Tables' infoblock:

Table data stored in JSON:

{
  "headers": ["Size EU", "Size RU", "Chest (cm)", "Hips (cm)"],
  "rows": [
    ["XS", "40", "80-84", "86-90"],
    ["S", "42", "84-88", "90-94"],
    ["M", "44", "88-92", "94-98"]
  ]
}

function getSizeTableForProduct(int $productId, int $sectionId): ?array {
    // First check product property
    $element = CIBlockElement::GetByID($productId)->GetNextElement();
    $props = $element->GetProperties();
    $tableId = (int)($props['SIZE_TABLE']['VALUE'] ?? 0);

    // If not, get from category
    if (!$tableId) {
        $section = CIBlockSection::GetByID($sectionId)->Fetch();
        $tableId = (int)($section['UF_DEFAULT_SIZE_TABLE'] ?? 0);
    }

    if (!$tableId) return null;

    $table = CIBlockElement::GetByID($tableId)->GetNextElement();
    $tableProps = $table->GetProperties();
    return json_decode($tableProps['TABLE_DATA']['VALUE'], true);
}

How to Implement Cascading Size Table Binding?

Binding is implemented at two levels:

Category level — a UF field UF_DEFAULT_SIZE_TABLE (bind to element of size table infoblock) is created for the section. All products in the category automatically inherit this table if they do not have a personal one.

Product level — an infoblock property PROP_SIZE_TABLE of type 'Bind to elements'. Allows overriding the table for a specific product.

This approach is better than storing the table as HTML text because it allows easy centralized data changes — through one infoblock element, not through all products.

Output in the Product Card

The size table is displayed in the template of the bitrix:catalog.element component. The standard approach is a modal window when clicking the 'Size Table' link next to the trade offer selector.

In the template, we include the data:

// In result_modifier.php or directly in template.php
$sizeTable = getSizeTableForProduct(
    $arResult['ID'],
    $arResult['IBLOCK_SECTION_ID']
);
$this->SetViewTarget('size_table_data');

Important nuance: if the product has trade offers of different sizes, the table should only be shown when a size parameter is actively selected (color changes with size are not needed — only the table).

Multilingual and Multiple Measurement Systems

For stores operating in different regions, one table should contain several measurement systems. In JSON, grouping by system is added:

{
  "systems": {
    "EU": { "headers": [...], "rows": [...] },
    "US": { "headers": [...], "rows": [...] },
    "UK": { "headers": [...], "rows": [...] }
  }
}

The measurement system switch is displayed above the table via JS without page reload.

Timeline

What is Included in the Work

• Designing the infoblock structure and properties for your catalog.
• Setting up cascading binding (category → product) with inheritance.
• Implementing a modal window with size table in the product card.
• Integrating with 1C for automatic size grid loading via CommerceML.
• Testing on test products and mock returns.
• Providing documentation on the data structure and API for further development.
• One month of support after delivery: fixing issues, helping with content.

The 'size table — trade offer' combination pays for itself by reducing returns in the first month. If you want a consultation for your project — contact us. We will evaluate the task, propose architecture and timeline. Order implementation to reduce returns and increase profit.

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.