Custom Clothing Size Table Development for 1C-Bitrix

Why Size Tables Are Critical for a Clothing Store on Bitrix?

Size mismatch is the leading cause of returns in fashion retail. According to industry data, returns due to size account for up to 40% of all orders. A static size image doesn't help: the user can't see how their measurements match. Our team develops dynamic size tables that reduce returns by 20–40%. There is no standard solution in 1C-Bitrix, so we design a custom architecture. We account for the fact that one product may be sold in RU, EU, US, UK size charts, and each brand has its own data. Only customization delivers real results.

How We Design the Size Storage Architecture

The wrong approach is hard-coding sizes in the template. A month later a new brand appears and everything has to be redone. We store tables in the database with links to brands and categories. Here is the structure:

CREATE TABLE b_size_charts ( ID SERIAL PRIMARY KEY, NAME VARCHAR(255) NOT NULL, CATEGORY VARCHAR(100), BRAND_ID INT, GENDER VARCHAR(10), ACTIVE BOOLEAN DEFAULT TRUE ); CREATE TABLE b_size_chart_rows ( ID SERIAL PRIMARY KEY, CHART_ID INT NOT NULL REFERENCES b_size_charts(ID), SIZE_RU VARCHAR(10), SIZE_EU VARCHAR(10), SIZE_US VARCHAR(10), SIZE_UK VARCHAR(10), CHEST_CM NUMERIC(5,1), WAIST_CM NUMERIC(5,1), HIPS_CM NUMERIC(5,1), HEIGHT_FROM SMALLINT, HEIGHT_TO SMALLINT, SORT INT DEFAULT 100 ); 

This gives us flexibility: one table for men's Nike t-shirts, another for women's Zara dresses. A dynamic table works more efficiently than a static image: returns drop by 20–40% versus 5–10%.

How to Bind a Table to a Product?

We add a product property SIZE_CHART_ID of type "Number" in Bitrix. If it's not filled, the component automatically finds the default table via section or brand. Implementation in component.php:

$chartId = $arResult['PROPERTIES']['SIZE_CHART_ID']['VALUE']; if (!$chartId) { $chartId = SizeChartTable::getDefaultForSection($arResult['IBLOCK_SECTION_ID']); } 

The custom:catalog.size.chart component displays the table in a modal or tab. For performance, caching is set to 24 hours since data changes rarely.

Interactive Size Advisor — Why It's Needed?

The advisor is a calculator: the user inputs chest, waist, and hip measurements and gets a recommended size. We synchronize it with SKUs: when a size is selected, the corresponding row in the table is highlighted; when the advisor is used, the appropriate SKU is auto-selected. Implementation in pure JavaScript:

function recommendSize(chest, waist, hips) { const chartData = window.sizeChartData; for (const row of chartData) { if (chest >= row.chest_min && chest <= row.chest_max && waist >= row.waist_min && waist <= row.waist_max) { return { sizeRu: row.size_ru, sizeEu: row.size_eu }; } } return null; } 

Such interactivity increases conversion and trust in the store.

Static vs. Dynamic Table Comparison

What's Included in Turnkey Size Table Development

The project includes:

• Database architecture and migrations
• Output component with responsive layout
• Size advisor with selection
• Admin interface for content managers
• Integration with SKUs and highlighting
• Documentation for managing tables

We have over 8 years of experience with Bitrix and have completed 40+ projects for fashion retail. Our developers are 1C-Bitrix certified, and we provide a code guarantee. Contact us for a consultation — we will assess your project and propose a solution.

SEO and Microdata for the Size Table

The size table is an SEO asset. A properly structured table can be indexed and appear in rich snippets. We recommend adding ItemList or SizeSpecification schema.org markup to each table row. Also add aria-label attributes for accessibility and a unique id for anchor links from the product card.

A "Go to size table" link on the product card increases time on page and reduces bounce rate. Anchor navigation is especially helpful on mobile devices where scrolling long pages is tedious.

Keeping Data Up-to-Date

Brand size charts are updated every season. Our admin interface allows content managers to edit tables themselves without developer assistance. CSV import enables bulk updates when collections change. A change log records who, when, and what was edited in the tables.

Timelines and Results

The size table is a conversion tool. Order a turnkey development and start reducing returns from the first month.