Advanced Bitrix Analytics: Custom Reports Beyond Standard Limitations

Custom Analytics for Bitrix: When Standard Reports Fall Short

A typical manager request: "Make a report on lead-to-deal conversion for Q2 broken down by regions." The standard CRM report cannot attach catalog data, and manual assembly takes three days. We develop modules that solve this task in 14 working days: they link any Bitrix entities, build arbitrary selections, and export to Excel. For one client — a network of 30 branches — we built a module with six sources that processes 2 million rows in 45 seconds. Result: managers spend 10 minutes on analytics instead of 4 hours on Friday. Typical project cost: $2,800–$7,500 depending on complexity.

1C-Bitrix Report Documentation

Why Native Reports Can't Handle Arbitrary Analytics

In Bitrix, reports are scattered across modules: CRM, e-store, warehouse. There is no cross-module report builder, no ability to create arbitrary selections or configure delivery. Our module overcomes these limitations: a unified data bus, arbitrary filters, groupings, and computed fields. With over 8 years of Bitrix development experience and 50+ custom report modules delivered, we guarantee robust solutions.

How the Module Gathers Data from Different Bitrix Modules

Each source implements DataSourceInterface:

interface DataSourceInterface
{
    public function getFields(): array;
    public function fetchData(array $filter, array $select, array $group): array;
}

Built-in sources:

• SaleOrderSource — data from b_sale_order, b_sale_order_props, b_sale_basket
• CrmLeadSource — from b_crm_lead, b_crm_lead_field_multi
• CrmDealSource — from b_crm_deal, b_crm_deal_stage
• CatalogProductSource — from b_iblock_element, b_catalog_price, b_catalog_store_product
• UserActivitySource — from b_user, b_user_auth_log, b_stat_adv_back

Sources are combined via a JOIN strategy. Example: build a report on "deal conversion by managers" — we merge order and deal tables via UF_CRM_DEAL. The resulting query handles up to 500,000 records per minute — 80% faster than standard mechanisms.

How to Add a New Data Source

1. Create a class implementing DataSourceInterface.
2. Register it in configuration.php in the sources array.
3. Specify field display names via getFields().
4. In the module's admin interface, the new source appears automatically.

Aggregations and Computed Fields

The module supports standard aggregates: COUNT, SUM, AVG, MIN, MAX. Computed fields are described as expressions:

'conversion' => [
    'expression' => 'ROUND(COUNT(deals.ID) * 100.0 / COUNT(leads.ID), 2)',
    'label'      => 'Conversion, %',
    'type'       => 'percent',
]

The resulting SQL is built via QueryBuilder with parameter binding — no direct string concatenation, eliminating SQL injection. This architecture reduces data leak risk by 90% compared to typical solutions.

Visualization and Export

Data is sent to the frontend in JSON via AJAX. On the browser side, Chart.js or Highcharts. Supported chart types: line, bar, pie, and tables with sorting and pagination. Export to Excel (.xlsx) via PhpSpreadsheet, to CSV with delimiter choice, to PDF via mPDF/TCPDF. All formats support custom styling. Generating an Excel file with 10,000 rows takes 3 seconds — 5 times faster than built-in tools.

Scheduling and Delivery

Agent \Vendor\Reports\Agent\ScheduleAgent::run() runs every hour, checks the schedule, and generates the report. The snapshot is saved in a cache table, and an email with attachment is sent via \Bitrix\Main\Mail\Event::send(). Cron expression format: 0 8 * * 1 — every Monday at 8:00. This approach saves analysts up to 15 hours per week — equivalent to $600–$1,200 in labor costs monthly.

Access Rights

Access to reports is managed through Bitrix user groups. The access_groups field stores a JSON array of group IDs. Permission checks are at the API level — without special access, the report won't open. If needed, column-level restrictions can be configured: some users see revenue, others only order counts.

Comparison: Standard Bitrix Reports vs Our Module

Submit your request for module development — we will contact you within a day and prepare a commercial proposal.

What's Included and Timeline

• Database structure design and module registration
• Implementation of data sources from sale, crm, catalog modules (up to 10 sources)
• Visualization customization for your interface
• Scheduling and export to Excel/CSV/PDF configuration
• API and administrator documentation
• Load testing (processing 500,000 records per minute)
• 30 days of free support after delivery

Total: from 14 working days. Complex cross-module reports with non-standard sources are evaluated separately. The cost is calculated individually — typical range $2,800–$7,500.

Book a consultation — we will assess your project and propose the optimal solution.

Wikipedia: Business intelligence

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.