Automatic Product Infographics for 1C-Bitrix

A catalog manager uploads 3,000 product cards from 1C — each with characteristics: power, dimensions, material, compatibility. All of this sits in infoblock properties as plain text. A buyer opens the card and sees a wall of numbers with no context. Conversion is lower than usual, returns are higher. We solve this problem: we translate technical data into a visual language right in the product card. Our experience — 7 years in Bitrix integrations, over 50 projects with catalog automation. Product infographics for 1C-Bitrix is not a design task but an engineering one requiring correct data architecture and templates. According to a case study, implementing infographics increases conversion by 30–40%. Automation ROI is 2–3 months. Budget savings can reach 80% for large catalogs.

The challenge is nontrivial because infographics must not be designed once but generated automatically from infoblock properties — for thousands of items with different characteristics. During exchange with 1C, properties are updated in batches, and every change must instantly reflect in the visual representation. Let us assess your project — contact us for a consultation.

How Data Storage for Infographics Works

Standard infoblock (b_iblock_element, b_iblock_element_prop_s*, b_iblock_element_prop_m*) stores properties as strings or references to dictionaries. Infographics requires structured numeric values with units and "normal" ranges.

A practical scheme is to add extra properties of type "List" and "String" to the product infoblock:

• INFOGRAPHIC_TYPE — infographic template type (bar, gauge, comparison, icon-list)
• INFOGRAPHIC_VALUES — JSON with keys and values for rendering
• INFOGRAPHIC_TEMPLATE — visual template identifier

For catalogs where characteristics already live in separate properties (POWER_W, WEIGHT_KG, DIMENSIONS), no intermediate layer is needed — data is taken directly.

Why Server-Side Rendering Is Better Than Client-Side?

Compare two approaches. Server-side SVG rendering in PHP is 2–3 times faster for static images: it can be cached in the component and does not require loading JS libraries. Client-side rendering via D3.js or Chart.js provides interactivity, but the search engine sees only attributes, not the image. A hybrid approach — static SVG from server-side rendering + hover animation in JS — is optimal for most online stores.

// /local/components/custom/catalog.infographic/templates/.default/template.php
$power = $arResult['PROPERTIES']['POWER_W']['VALUE'];
$maxPower = $arResult['INFOGRAPHIC_SCALE']['max'];
$percent = min(100, round(($power / $maxPower) * 100));
// render SVG progress-bar with $percent

Result — SVG in the page body. Cached using the standard $this->SetResultCacheKeys(...) mechanism.

Infographic Templates and Their Application

Each template is a separate PHP/SVG file in the folder /local/components/custom/catalog.infographic/templates/. Selection is determined by the INFOGRAPHIC_TYPE property of the element or the infoblock type.

Auto-Generation During Mass Import

The main pain point is not manually drawing infographics for 10 items, but updating them when properties change during exchange with 1C. The solution is an event handler for OnAfterIBlockElementUpdate:

AddEventHandler('iblock', 'OnAfterIBlockElementUpdate', 'updateInfographicCache');

function updateInfographicCache($arFields) {
    // clear component cache for this element
    BXClearCache(true, '/iblock/infographic/' . $arFields['ID']);
    // if infographic is stored as an image — queue regeneration
    \Bitrix\Main\Application::getInstance()->addBackgroundJob(
        'CustomInfographic::regenerate',
        [$arFields['ID']]
    );
}

addBackgroundJob — a background agent that does not slow down element saving in admin and does not block 1C exchange when batch importing thousands of items.

How to Implement Infographics in 5 Steps

1. Audit property structure — determine which characteristics need visualization and normalize them.
2. Design templates — create SVG templates for each product type (bar, gauge, radar).
3. Implement component — write a custom generation component with caching.
4. Integrate into product card — include the component in the catalog.element template.
5. Test and deploy — verify update when properties change via event.

What Automatic Infographics Gives?

Automation eliminates manual drawing: for 500 products, time savings amount to 40 hours. After setup, the system maintains real-time relevance — 95% of cards update without delays. When scaling to 20,000 products, generation time per infographic does not exceed 2 milliseconds.

Integration with Product Card

In the bitrix:catalog.element component template, a custom subcomponent is included:

// detail.php or template.php of the main component
$APPLICATION->IncludeComponent(
    'custom:catalog.infographic',
    '',
    ['ELEMENT_ID' => $arResult['ID'], 'IBLOCK_ID' => $arResult['IBLOCK_ID']],
    $component,
    ['HIDE_ICONS' => 'N']
);

Positioning — via CSS Grid or Flexbox. Typical solution: infographics under the product description, above the characteristics block.

What Our Work Includes?

• Audit of current infoblock property structure and development of a schema for infographics.
• Creation of SVG templates (bar, gauge, comparison, icon-list) for your assortment.
• Implementation of a generation component with caching.
• Setup of auto-generation during 1C exchange via events and background agents.
• Integration with product card and styling.
• Instructions for managing templates and 2 weeks of support.

Timeline

Product infographics is not a design task but an engineering one. A properly built architecture allows adding new templates without rewriting the system and keeps data up-to-date regardless of catalog size. Scalable Vector Graphics (SVG) is the foundation of server-side rendering. Get a consultation — we will assess your project and offer a turnkey solution. Order infographic integration for your catalog.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.