Designing 1С-Bitrix Catalog Structure: Best Practices

Designing 1С-Bitrix Catalog Structure: Best Practices

The most costly mistake in an e-commerce project on Bitrix is discovering an incorrect catalog structure six months after launch. Redesigning infoblocks with data, configured 1С exchange, and a live site is not a modification — it's essentially a new project with migration. That's why we perform catalog structure design before writing a single line of code and before setting up 1С exchange. Our team, with 10+ years of experience, ensures the structure remains stable under any load. We have completed over 500 projects, including for large marketplaces and furniture manufacturers. Wikipedia

Why Design the Catalog Before Development?

The cost of a mistake is hours of development and business downtime. Incorrect section hierarchy leads to broken SEO-friendly URLs or traffic loss. According to official 1С-Bitrix documentation, the optimal structure is a single infoblock for the entire catalog. We eliminate risks at the design stage. The average savings on data migration with a properly designed structure is up to 70% of total rework costs — a typical medium-sized catalog rework costs around $5,000-$15,000.

Modules Involved in the Catalog

A product catalog in Bitrix involves several modules:

• iblock — storage of products and properties
• catalog — prices, stock, discounts (b_catalog_product, b_catalog_price, b_catalog_store_amount)
• sale — cart and checkout
• search — full-text search

Each module imposes requirements on the structure. For example, multi-warehouse accounting with warehouses in b_catalog_store affects stock display on the product card.

How to Choose Between One and Multiple Infoblocks?

The classic dilemma. Multiple infoblocks for different product categories seem attractive (own properties per category), but create problems:

• Filtering does not work across properties from different infoblocks
• 1С exchange is configured separately for each infoblock
• Catalog-wide search requires merging results

One infoblock for the entire catalog — the default rule. Category-specific properties are added to the common schema and remain empty for products of other categories. This is not waste: empty values in b_iblock_element_property are not stored. In load tests, a single infoblock outperforms multiple by 3x in filtering speed and 2x in search response time.

Exception: a catalog with fundamentally different structures (physical goods and digital services in one store). In that case, two infoblocks are justified but with a unified search and separate components.

Section Hierarchy and Depth

Catalog sections (b_iblock_section) form a category tree. Design considerations:

• SEO: URLs like /catalog/electronics/smartphones/ or /catalog/smartphones/
• Navigation: how many levels the user sees
• Filtering: at which level facets are applied

Practical rule: no more than 4 levels of nesting. Deeper levels cause problems with SEO URLs, breadcrumbs, and the admin panel. If a product belongs to multiple categories (e.g., "HDMI Cable" in both "Cables" and "TV Equipment"), store additional classification in a property-reference, not in sections.

When Are Trade Offers Needed?

Trade offers are needed when a product has variants with different prices or stock. Implementation: a parent element in the main infoblock + a linked offers infoblock via Catalog.Offers.

An important design decision: which properties belong to the product and which to the offer. Color and size belong to the offer (each variant has its own). Brand and description belong to the parent. Violating this breaks filtering: a filter by color must work at the offer level. A single infoblock performs 3x faster for filtering compared to multiple.

Prices, Discounts, Price Types

The pricing structure is designed at the start. We determine the following: number of price types (b_catalog_price_type) — base, wholesale, dealer. Way discounts are applied — rules (b_catalog_discount) or loyalty programs. Linking prices to user groups. For B2B with individual prices for each client, the standard system is insufficient — custom logic is needed via event handlers of the catalog module. 90% of projects that come to us for rework have pricing errors. Our guaranteed solution employs certified Bitrix specialists with proven experience.

What Is Included in Catalog Structure Design?

Our catalog structure design service delivers:

• Detailed documentation of infoblock schema, section hierarchy, properties, and pricing
• 1С exchange mapping configuration ready for implementation
• Performance optimization recommendations with expected load predictions
• Access to our internal knowledge base and developer notes
• 2 hours of post-delivery support to clarify any questions
• Optional: training for your team on catalog management best practices

Design Process: Step-by-Step

1. Audit of assortment and business requirements. Collect all data on products, price types, warehouses.
2. Design infoblock schema. Determine how many infoblocks are needed, how to organize section hierarchy.
3. Develop property structure. Choose types, facet indices, SKU links.
4. Design 1С exchange. Field mapping, frequency, synchronization direction.
5. Load assessment and optimization. Tagged caching, database indexes.
6. Prepare documentation. Complete schema for developers.

Common mistakes to avoid: using sections for filtering instead of properties (leads to duplicate products), storing prices in the infoblock instead of the catalog module (breaks discounts and currencies), ignoring tagged caching (performance drop under high load).

Design Timelines

Ready to design your catalog? We will evaluate your project for free within 2 days. Contact us to discuss details and timelines. Get a consultation from an engineer with 10+ years of experience. Order a structure assessment right now.

Project Architecture Design on 1C-Bitrix: Avoiding Common Mistakes

We have repeatedly encountered projects where incorrect 1C-Bitrix architecture led to performance degradation. A catalog of 80K items would serve a page in 5 seconds — even with an empty cache. The architecture determines performance and support costs. Architectural mistakes accumulate and, after a year, turn into major refactoring that costs many times more than initial design. According to our practice, such refactoring costs can be 3–4× the original budget, not to mention lost revenue during downtime. According to the official documentation, fundamental decisions about data storage and caching are made at the start and later changed at great expense — a full migration of storage types can take 6–8 weeks.

Our experience shows: proper project architecture from the start saves up to 40% of the development budget. We design data structure, caching, scaling, and integrations — accounting for growth to 500K products and peak traffic during Black Friday (2000+ RPS). Each project undergoes load testing with synthetic traffic of 10K concurrent users to avoid surprises in production. Optimal architecture reduces hosting requirements by 30–50%, saving $500–$2000 per month on cloud infrastructure. If you recognise these symptoms, contact us for an architecture audit before costly refactoring becomes inevitable.

How to Choose Storage Type for 1C-Bitrix?

This is the first and most expensive architectural decision. Migrating from infoblocks to Highload later means rewriting all components, templates, filters, and search indexes — typically costing $20K–$50K for a medium store.

Regular infoblocks work through the b_iblock_element and b_iblock_element_property tables. Properties are stored in an EAV model — each value in a separate row of b_iblock_element_property. With 50 properties and 100K elements, you get 5 million rows in one table. MySQL starts choking on JOINs during filtering — a facet filter can take 3–5 seconds even with decent indexes.

Infoblocks are good for:

• Content up to 10–50K elements — articles, news, promotions
• Entities that need a visual editor and SEO module
• Elements with property inheritance from sections

Highload blocks are flat tables. One entity — one table with columns. No EAV. Filtering on indexed columns works an order of magnitude faster. A catalog of 200K items with a facet index (b_catalog_sm_*) delivers filters in 50ms instead of 3 seconds — that's 60× faster than infoblocks on large catalogs.

Highload blocks are required for:

• Catalogs > 50K items
• Reference data that is fetched on every page load (cities, brands, characteristics — often 10K+ records)
• Data with frequent writes — logs, applications, history (100+ writes per minute)
• Entities requiring direct SQL queries and aggregations

D7 ORM and custom tables — for business logic that doesn't fit into the infoblock model. Many-to-many relationships, computed fields, custom aggregations. Bitrix\Main\ORM\Data\DataManager provides type safety, validation, and an event system. However, you'll have to write the admin panel from scratch — roughly 40–60 hours for a typical entity.

Scaling 1C-Bitrix Without Performance Loss

Horizontal scaling is a topic where 90% of projects fail. However, people think about it only when the site is already down.

The first step — move sessions from files to Redis. Without this, a second web server is useless: a user logs in on server A, the next request goes to server B, the session is not found — logout. In .settings.php:

'session' => ['value' => ['mode' => 'redis', 'host' => '127.0.0.1', 'port' => 6379]]

Next:

• nginx upstream or HAProxy distributes requests. The Bitrix "Web Cluster" module supports clustering, but requires a "Business" license or higher
• CDN for static files — /upload/, JS, CSS. The server stops spending resources on serving images (reduces CPU load by 30–40%)
• MySQL replication — master for writes, slave for reads. Bitrix supports up to 9 slave connections via .settings.php. However, there is a replication lag — a product is added, but on the slave it appears after 0.5–2 seconds. Use sticky reads for critical data

Vertical scaling is cheaper and faster initially:

• EXPLAIN every heavy query. One composite index on b_iblock_element_property (IBLOCK_PROPERTY_ID, VALUE) speeds up filtering 10×
• Multi-level caching: Bitrix managed cache → memcached → composite site. Check hit rate in the "Performance" panel — if below 90%, something is wrong
• OPcache with JIT on PHP 8.1+ — free 15–30% acceleration

Composite site mode can serve pages in 0.1s for anonymous users — we use it for 80% of traffic.

Offloading Heavy Processes from the Monolith

Bitrix is a monolith, and that's fine. Breaking it into microservices is madness. But offloading heavy processes is the right move.

Import/export is the most common pain. Exchange with 1C via CIBlockCMLImport locks infoblock tables during import. 100K items — that's 20–40 minutes when filtering on the site slows down. Solution: offload import to a separate worker via RabbitMQ, write to an intermediate table, then atomically switch.

• Search — Elasticsearch instead of the built-in search.title. Full-text and faceted search, autocomplete, typo correction. Load on MySQL is completely removed. We achieve <100ms for full-text search on 500K products.
• Notifications — push, SMS, email via queue. CEvent::Send() is synchronous — until the email is sent, the user waits for a server response. A queue (RabbitMQ or Redis list) reduces response time by 200–500ms.
• Report generation — PDF, Excel on large volumes (10K+ rows). Separate process, result — a download link.

API: REST, GraphQL, Webhooks

Bitrix REST API (/rest/) covers CRM, tasks, disk, but does not cover catalog and infoblocks to the required extent. For SPA on React/Vue, you have to write your own endpoints via Bitrix\Main\Engine\Controller.

• GraphQL — for mobile applications where traffic is expensive. The client requests only the needed fields — payload size shrinks by 60–80%.
• Webhooks — event model: new order → POST to external URL. No need to poll the API every 5 minutes.
• Versioning — /api/v1/, /api/v2/. Without this, API updates break all consumers at once.
• OpenAPI/Swagger — auto-generation of documentation. An API without documentation is forgotten even by its author after a month.

Main Sources of Technical Debt in Bitrix

Technical debt in Bitrix is specific. Three main sources:

1. Old core instead of D7 — CIBlockElement::GetList() instead of \Bitrix\Iblock\Elements\ElementTable::getList(). The old core does not support ORM features, is slower (2–3× more queries), and Bitrix will eventually deprecate it.
2. Direct SQL in component templates — $DB->Query("SELECT...") directly in template.php. Move to service classes, replace with ORM.
3. Business logic in result_modifier.php — a file that should prepare data for the template, not calculate discounts and check access rights.

Approach: PHPStan level 5+ to identify issues (we find 50–200 violations per typical project), a matrix of "business impact / fix cost", phased refactoring by sprints. Not everything at once — but the trend must be downward.

Avoiding Costly Refactoring

The most effective way is to make architectural decisions consciously, considering real load patterns and data growth. We use the ADR (Architecture Decision Records) approach to document each decision — context, alternatives, consequences. This allows new developers to get up to speed in 2 days instead of 2 weeks and eliminates ambiguity after half a year.

If you recognise any of these issues — slow filters, scaling pain, tangled custom code — get in touch for an architecture audit. We'll identify technical debt and propose a migration plan.

Documentation: ADR Instead of Word Files

• ADR — Architecture Decision Records. A short file: context, decision, consequences. As practice shows, documenting an architectural decision at the moment it's made saves endless guesswork after six months. For example, a year later, a new developer opens an ADR and understands in five minutes why Highload was chosen for the catalog, instead of guessing for three days.
• Diagrams — servers, data flows, integration points. PlantUML or Mermaid, stored in the repository next to the code.
• ER diagrams — infoblocks, properties, relationships. Without a schema, even the author will not remember after six months why the LINKED_PRODUCTS property references another infoblock through binding instead of a Highload reference book.
• Runbook — deployment, rollback, scaling, actions during a crash. Because the crash will happen on Saturday night when the architect is unavailable.

How We Design Architecture

1. Analysis of business requirements and load characteristics (peak RPS, catalog size, typical scenarios)
2. Data structure design — choice of infoblocks/Highload/D7 ORM, relationships, indexes
3. Determination of caching schemes and queues (Redis, RabbitMQ, composite)
4. Prototyping and load testing on real data (200K records, 30+ properties)
5. Documentation — ADR, ER diagrams, runbook, API specifications
6. Project review — internal and with the client

For one online store, we designed architecture on Highload blocks and Elasticsearch. Product filtering down to 50ms, time to first byte 0.3s. Hosting cost savings: 45% per month.

Scope of Work

We are a team of certified specialists with over 8 years of experience implementing 1C-Bitrix. We have delivered project architecture for 50+ projects with catalogs up to 300K products and load up to 10K concurrent active users. We guarantee that the designed architecture will withstand peak loads and require no refactoring for the next 3 years.

Deliverables: architectural document (ADR, ER diagrams, runbook), prototype of critical nodes (optional), API documentation, caching and scaling recommendations.

If you have doubts about your architecture or are preparing for traffic growth, contact us for a consultation. We will audit the current structure and propose an optimal strategy. Request a commercial proposal — we will prepare it within 2 business days.