Custom Sales Reports for 1C-Bitrix: Analytics and Dashboards

Imagine: 5,000 orders monthly, managers spending 15 hours exporting data from Bitrix and building reports in Excel. Up to 30% of data lost due to manual copying. Standard Bitrix reports don't show profit per manager, ABC analysis of products, or conversion by channel. Custom analytics drastically reduces manual processing time and associated costs.

We build custom sales reports turnkey — from ORM queries to admin dashboard and Excel export. In 5 years we've completed over 50 projects for Bitrix stores. Each report speeds up decision-making 10x faster than manual export.

Limitations of Standard Bitrix Reports

The built-in sale module outputs a flat order table with minimal grouping. Sales management requires segmentation by manager with returns, breakdown by product categories, average check dynamics, repeat purchase analysis. Standard reports can't link data from different tables — orders, basket, payments, order properties — into a single analytical query. Estimates show up to 80% of manager time is spent on manual data handling. Without custom analytics, business relies on guesswork, not numbers.

How to Build a Revenue Report by Manager?

The most demanded report — revenue by period with manager breakdown. Task: show how much each manager brought in, from how many orders, average check, and cancellation rate. Data is collected via ORM query to OrderTable grouped by manager and month. Metrics calculated: revenue (excluding cancellations), cancelled amount, order count, average check, conversion to completed order, processing speed.

Example ORM query (without filter):

use Bitrix\Sale\Internals\OrderTable;
use Bitrix\Main\Entity\ExpressionField;

$result = OrderTable::getList([
    'select' => [
        'RESPONSIBLE_ID',
        'MONTH' => new ExpressionField('MONTH', "DATE_TRUNC('month', %s)", ['DATE_INSERT']),
        'REVENUE' => new ExpressionField('REVENUE', 'SUM(CASE WHEN %s NOT IN (\'F\', \'CA\') THEN %s ELSE 0 END)', ['STATUS_ID', 'PRICE']),
        'CANCELLED' => new ExpressionField('CANCELLED', 'SUM(CASE WHEN %s IN (\'F\', \'CA\') THEN %s ELSE 0 END)', ['STATUS_ID', 'PRICE']),
        'ORDER_COUNT' => new ExpressionField('ORDER_COUNT', 'COUNT(%s)', ['ID']),
        'AVG_CHECK' => new ExpressionField('AVG_CHECK', 'AVG(CASE WHEN %s NOT IN (\'F\', \'CA\') THEN %s END)', ['STATUS_ID', 'PRICE']),
    ],
    'filter' => [
        '>=DATE_INSERT' => DateTime::createFromPhp(new \DateTime('first day of this month')),
    ],
    'group' => ['RESPONSIBLE_ID', 'MONTH'],
    'order' => ['MONTH' => 'ASC', 'REVENUE' => 'DESC'],
]);

Manager metrics we calculate:

• Revenue (excluding cancellations and returns)
• Cancelled amount — indicates quality of work
• Average check — comparison across managers
• Order count — workload
• Conversion from "New" to "Completed" — COUNT(status=F) / COUNT(*) by status
• Average processing speed — AVG(DATE_STATUS - DATE_INSERT)

On one project we reduced report build time from 15 seconds to 2 by adding proper indexes.

How to Optimize Report Performance?

On a store with 50,000+ orders, ORM grouping queries take 3-10 seconds. Solutions:

• Materialized views (PostgreSQL) or summary table recalculated by agent once per hour
• Mandatory indexes: (DATE_INSERT, STATUS_ID) on b_sale_order, (ORDER_ID, PRODUCT_ID) on b_sale_basket
• Report cache in Bitrix managed_cache with TTL 1 hour, invalidated on order change

ABC Analysis and Its Implementation in Bitrix

ABC analysis shows which products and categories generate revenue and which are dead weight. Typically 20% of products bring 80% of revenue. Implemented via window function SUM() OVER (ORDER BY revenue DESC) or programmatically after fetching. Sort products by descending revenue, calculate running total, assign category: A (80% revenue), B (15%), C (5%).

Structure: JOIN BasketTable with OrderTable (filter paid orders) and catalog infoblock. Group by sections with aggregation: revenue, units sold, average selling price, average discount.

Visualization and Dashboard

Reports are placed on a custom page in /local/admin/. Visualization stack:

• Chart.js — line charts for dynamics, bar charts for manager comparison
• HTML tables with sorting — for detailed data
• PhpSpreadsheet — export to xlsx with formatting, totals formulas, auto-width columns

Dashboard is built as a single-page with tabs: "Total Revenue", "By Manager", "By Product", "ABC Analysis". Data loaded via AJAX endpoint, filter parameters (period, manager, category) passed in the request.

Integration with External Systems

For a complete picture, integration with 1C Trade Management/ERP, CRM, or telephony is often needed. We connect payment data via REST API, sync counterparty directories, add conversion funnel by traffic channels. For conversion report we use sale module data and order custom properties, showing the customer journey from lead to payment.

What's Included in the Work

• Analytics: define metrics, agree on slices
• Backend: ORM queries, optimization, caching
• Frontend: dashboard, graphs, filters
• Export: Excel templates, formatting
• Testing: verification on real data, load testing
• Documentation for reports and 3 months support

Development Timeline

Typically 1-2 weeks depending on number of reports and metric complexity. Stages: analytics (1-2 days), backend (3-5 days), frontend (2-3 days), export (1 day), testing (1-2 days). Result — a dashboard in admin panel with export, replacing manual export and Excel processing.

Contact us to discuss your metrics and get a consultation. Request custom report development — we'll prepare a commercial proposal within a day.

Why Does 1C‑Bitrix Analytics Mislead?

Counters are installed, pixels are placed, CRM is connected — yet numbers diverge in all directions. E‑commerce conversions do not transfer to the dataLayer. UTM tags get lost on URL redirects. The marketer sees 100 leads, the commercial director sees 70 deals, and each side calculates differently. Decisions are made by intuition and the advertising budget vanishes.

We have been configuring 1C‑Bitrix analytics for over a decade. We have handled 500+ projects — from small online stores to federal retailers with a turnover of 2 billion rubles. Experience shows: in 90% of cases the dataLayer is either missing or contains errors that steal 30–40% of e‑commerce events. Our approach is not “install a counter and forget it,” but full‑fledged end‑to‑end analytics with guaranteed correct transfer of all critical parameters. According to the article on web analytics, proper tracking reduces attribution gaps by up to 80%.

Platform‑Specific Analytics: Yandex.Metrica and Google Analytics 4

Basic Setup and Common Mistakes

Everyone installs the Metrica counter. Only a few do it correctly.

• Installation via GTM, not by inserting into header.php — otherwise the counter gets lost on template update.
• Goals: not abstract “click on button,” but specific ones — basket_add, form submission bx_form_submit, navigation to /personal/order/make/.
• Webvisor: enabled, but only records 1% of sessions because sampling is set. Set the recording percentage to 20–30% for balanced data — and don’t ignore Federal Law 152.
• Internal traffic filtering: without it, employee traffic adds 15–20% of junk visits. Filter by IP, _ym_debug cookie, and headers.

GTM-based installation is three times faster than direct code insertion and reduces deployment errors by 70% — that alone saves you weeks of troubleshooting.

Electronic Commerce — The Most Underrated Feature

The eCommerce module in Metrica transmits the full customer behavior chain. The problem is that in Bitrix, out of the box, it only works with the sale.order.ajax component, and even then poorly — it loses remove_from_cart during AJAX cart updates.

We pass the following data to the dataLayer:

• Product view — id, name, brand, category, price. Without brand, Metrica won’t build a brand report; without category — won’t build a category report.
• Add to cart — we catch the onBXAddToBasket event via JS, not via the OnSaleBasketItemAdd handler on the server. The server handler doesn’t know about the JS context.
• Remove from cart — a pitfall: the standard sale.basket.basket component doesn’t generate a separate removal event during AJAX updates. A custom observer is required.
• Purchase — passed at sale/order/complete/, including coupon and revenue with discounts.

How to Fix the dataLayer for 1C‑Bitrix E‑commerce?

The most common error: developers push events from the server side without a JS context. As a result, GA4 receives a broken items array. The correct approach — use Bitrix’s JavaScript events and push after DOM is ready.

Example of a fixed dataLayer setup for add_to_cart:

BX.addCustomEvent('onBXAddToBasket', function(product) {
    window.dataLayer.push({
        'event': 'add_to_cart',
        'ecommerce': {
            'items': [{
                'item_id': product.id,
                'item_name': product.name,
                'price': product.price,
                'quantity': 1
            }]
        }
    });
});

Data Sent to Metrica and GA4

Why GA4 Requires Manual Setup for Bitrix

GA4 works on events, not hits. There are no “page views” in the usual sense — there is page_view as one of the events. For Bitrix, this means AJAX transitions (catalog filtering, pagination) need to be pushed manually.

Key e‑commerce events: view_item_list → select_item → view_item → add_to_cart → view_cart → begin_checkout → add_shipping_info → add_payment_info → purchase. Each event requires its own set of parameters. purchase without transaction_id will not be counted. add_to_cart without the items array is useless. GA4 will silently swallow invalid data and show empty reports. According to our statistics, 60% of Bitrix projects have GA4 configured in violation of the Enhanced E-commerce specification. This leads to loss of up to 40% of transactions in reports. Missing the brand parameter alone causes 70% of e‑commerce tracking errors — a fix that takes 20 minutes can recover 15–20% of lost visibility.

User Parameters That Really Matter

Don’t pass everything. Five parameters that give 80% of the value:

• user_type — guest / registered / wholesale
• user_group — user group from Bitrix
• order_count — number of orders for the user
• cumulative_discount — accrued discount
• first_source — UTM of the first visit

End‑to‑End Analytics and Dashboards

Metrica sees visits. CRM sees deals. Ad accounts see spend. But the link between them is broken. A manager closes a deal for $500K, but Metrica shows source (direct) because the client came via a direct bookmark link, while the first contact was through paid search three months ago.

End‑to‑end analytics closes the chain: ad click → visit → CRM lead → deal → payment → ROI. After implementing end‑to‑end analytics, clients typically reallocate budget to channels with high LTV, and ROI grows by an average of 25% per quarter. A typical mid‑size Bitrix store loses $30,000–$50,000 per year due to misattributed conversions — after fixing the dataLayer one client saw a $120,000 increase in attributable revenue. Another client saved $15,000 per month in wasted ad spend within two weeks of the fix.

How We Collect and Aggregate Data

1. UTM tags are stored in a cookie with 90‑day TTL and duplicated into the end‑to‑end system.
2. When a lead is created in Bitrix24, we write UTM into custom deal fields.
3. Call tracking replaces the number and links the call to the visit.
4. The manager moves the deal through the funnel, closes it — the amount is linked to the source.
5. The service aggregates expenses via ad account APIs.
6. ROI = (revenue — expenses) / expenses for each campaign.

Tools Comparison

Where Exactly Is the Hole in Your Funnel?

Typical Bitrix store funnel:

The checkout drop‑off is the most expensive. The user already wanted to buy, already added to cart, and then sale.order.ajax throws a 500 error due to an unconfigured delivery handler. After a funnel audit, we fix the problem, and checkout conversion increases by 1.5–2 times within a month.

Cohort Analysis and LTV Insights

We group by month of first purchase, look at retention after 30, 60, 90 days. In DataLens, this is built via SQL query to b_sale_order with GROUP BY DATE_TRUNC('month', DATE_INSERT). The main insight: which channel attracts high‑LTV customers. Context may give cheap first orders but zero repeat rate. SEO traffic converts worse but comes back. Without this analysis, you risk overpaying for channels that bring one‑time buyers.

What’s Included in Our Analytics Setup Service

• Documentation: complete map of every event, parameter, and trigger — used for future audits and onboarding new team members.
• Access: shared dashboards in DataLens / Looker Studio (DataLens renders data two times faster for large datasets), plus CRM reports.
• Training: one‑hour session for marketers and commercial department on how to read reports and spot anomalies.
• Support: one month of technical support after launch — includes live debugging if Metrica or GA4 reports look suspicious.

How to Start: Audit and Setup

Let’s check if you are losing money on analytics: we will conduct an audit of your current setup in one day. Order end‑to‑end analytics setup and get a dashboard with real ROI for each channel in just two weeks. Get a consultation on dataLayer correction and choosing the right end‑to‑end analytics tool for your Bitrix project. Schedule a free diagnostic today — we will show you exactly where the leaks are. Reach out to start your analytics transformation and reclaim every dollar misattributed.