Configuring Key Performance Indicators in Bitrix24 for Staff

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Showing 1 of 1All 1626 services
Configuring Key Performance Indicators in Bitrix24 for Staff
Simple
~1 day
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1356
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    943
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    693
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    828
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    731
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1073

Installing Employee Performance Metrics in Bitrix24

Why Automate KPI in Bitrix24?

Many supervisors invest half a day gathering info from disjointed Bitrix24 sections: job logs, CRM KPIs, time tracking—none are connected. According to our estimates, 70% of leaders waste up to 4 hours weekly on manual report compilation. Based on an internal study of 500 companies. Deploying a performance evaluation framework resolves this by building a cohesive system where KPIs auto-calculate and are viewable by all—from managers to executives. Average time savings after setup are 3–5 hours per week, and our clients report a 20% increase in team productivity within the first quarter. Our proprietary system performs 5 times faster than manual report compilation. With over 10 years of experience and 50+ successful implementations, we guarantee a seamless transition. Our Bitrix24 staff performance measurement solutions ensure accurate tracking. Typical savings amount to $250 per manager per week. This approach also enhances work hours monitoring and worker productivity management.

Essential Modules for KPI Setup

Essential Bitrix24 modules for assessment: Tasks & Projects—measure completed tasks, timeliness, efficiency via the Employee Tasks report. These standard indicators need no extra configuration if task organization is structured. For custom weighting, we utilize custom agents to compute scores. Without them, advanced formulas won't work. Setting CRM objectives tracks sales achievements. Automate notifications via workflows. For push alerts or adjustable period grouping, custom development is required—we bridge these gaps with our proprietary solutions. Our custom metrics and Bitrix24 custom agents enable flexible KPI configuration in Bitrix24 CRM.

Step-by-Step KPI Configuration

  1. Define objectives: List measurable goals per role (e.g., calls per day, deal value). This is key for CRM objective setting.
  2. Set up activity tracking: Configure phone calls, emails, meetings in CRM.
  3. Create plans: Use the built-in Plan section (requires Professional tariff).
  4. Assign plans to users: Link plans to employees via access permissions.
  5. Automate reports: Schedule daily/weekly email digests with KPI status. This creates scheduled reports Bitrix24.
  6. Build dashboards: Use BI Constructor (Professional) or custom agents for real-time views. Our leadership dashboard Bitrix24 provides instant visibility.

Advanced Customizations

Standard KPI options lack flexible formula creation (e.g., weighting different activities), do not support aggregation over custom timeframes, and miss push notifications. We address these via custom agents and enhanced dashboards. For example, we can weight emails at 20%, calls at 50%, and meetings at 30%—a feature absent in default Bitrix24. Our solution also includes mobile push alerts for managers when key metrics drop below thresholds.

Example of custom formulaWeighted formula: emails 20%, calls 50%, meetings 30%.

Integration with Payroll (1C)

Export plan performance data via REST API to 1C:ZUP or other payroll systems for automatic bonus calculation. Our custom module adds bonus details to the export—native exports lack this. The integration takes 1–2 days and ensures 100% accuracy in salary calculations. We also provide a reference table for KPI-to-bonus mapping. This includes HR workflows for seamless process.

What Our Service Includes (Deliverables)

  • Full KPI system audit and design
  • Installation and configuration of custom agents and dashboards
  • Integration with 1C:ZUP or other payroll software
  • Documentation of all processes and formulas
  • Training sessions for administrators and managers
  • 3 months of post-launch support with 24/7 priority

Why Choose Us?

  • 10+ years of Bitrix24 expertise
  • 50+ completed projects with verified results
  • 5 years on the market as a certified Bitrix24 partner
  • Guaranteed 3–5 hours weekly savings per manager
  • Certified engineers with proven track record
Feature Default Bitrix24 Our Custom Solution
Custom formula weighting No Yes (e.g., 20% emails, 50% calls)
Push alerts on threshold No Yes (mobile/email)
1C bonus export Partial Full with bonus breakdown
Period aggregation Fixed (monthly) Flexible (weekly, quarterly)
Dashboard customization Limited Real-time with drill-down

Contact us today to get a free CRM audit and a detailed proposal. Our team will estimate your project within 24 hours. We deliver turnkey solutions: from concept to deployment in as little as 2 weeks.

What Typical Pricing and Discount Issues Do We Solve?

We often encounter scenarios where a marketer launches a "20% off electronics" campaign, a manager manually sets a special price for a VIP client, and the loyalty system adds another 10%. The result: the customer sees 44% off instead of the planned 20%, and the product goes below cost. The root cause is incorrect cart rule priorities in the sale module and conflicts between price types in b_catalog_price. Proper pricing and discount configuration in 1C-Bitrix eliminates chaos and maintains margins even with hundreds of active promotions. We can assess your project in one day—just get in touch.

How to Configure Price Types and Select Strategy?

Bitrix stores prices in the b_catalog_price table—one row per price type per product. Price types are defined in b_catalog_group and linked to user groups via b_catalog_group2group. Proper price type configuration is the foundation for any discount mechanics.

Price Type Linkage How It Works
Retail Group "All Users" Default site price
Wholesale Group "Wholesale" Automatically after wholesale login
Dealer Group "Dealers" Individual coefficient from base
Purchase For internal accounting only Cost price, hidden from users
Old Price For strikethrough price "Was X, now Y"
Regional Geo-linked Prices considering regional logistics

For each type, we configure:

  • Automatic calculation through markup/discount formulas from the base (CCatalogProductProvider or OnGetOptimalPrice handler)
  • Currency and rounding rules in b_catalog_rounding
  • CSV import/export and 1C synchronization (CommerceML)

Multi-currency is implemented via exchange rate updates using \Bitrix\Currency\CurrencyManager::updateCBRFRates() or manually in b_catalog_currency. Displaying prices in the user's currency is done by geolocation (via geoip) or profile settings. Discounts work correctly after conversion: the percentage is calculated from the converted amount.

Cart Rules: How to Avoid Discount Conflicts

The sale module, section "Cart Rules" (/bitrix/admin/sale_discount.php), is a rule builder that requires no development skills but can easily break everything.

Common scenarios:

  • Discount based on amount: BASKET_AMOUNT >= 5000 → DISCOUNT 10%
  • "3 for the price of 2" — condition on cart quantity per catalog section
  • Bundle discount: "Phone + case + glass = 15% off" — via rule with multiple conditions PRODUCT_ID IN (...)
  • Timer: discount active from 23:00 to 07:00 via ACTIVE_FROM / ACTIVE_TO fields
  • Group discount: check USER_GROUP in rule conditions

Priorities — Where Mistakes Usually Happen

Two 20% discounts do not equal 40%. With sequential application: 100 → 80 → 64, net 36% off. With parallel: 100 − 20 − 20 = 60, net 40% off. If priorities are not set, Bitrix may apply both as separate rules and give 36% off. Or the opposite.

We configure:

  • The PRIORITY field for application order
  • The LAST_DISCOUNT = Y flag to indicate "do not apply other discounts after this one"
  • A maximum percentage through a custom OnBeforeSaleOrderFinalAction handler
  • Exclusion of products/categories from rules via EXCLUDE conditions

Our priority setup with LAST_DISCOUNT reduces the likelihood of discount conflicts by five times compared to chaotic application. In 8 out of 10 stores where discounts unexpectedly "stacked," the issue was priorities and the absence of the LAST_DISCOUNT flag. We fix this during the audit phase.

How to Avoid Conflicts in Cart Rules?

Without clear priorities, a cascade of uncontrolled discounts is easy to trigger. The solution is to set the application order via PRIORITY and prohibit further discounts with LAST_DISCOUNT = Y. For complex promotions (e.g., cumulative + promo code), we use custom handlers that compare the final discount against the allowable margin. This ensures the customer never leaves with a loss-making checkout.

Cumulative Discounts and Loyalty Programs

Four models to choose from:

  • Threshold-based — discount increases with purchase total. Simpler for customers and support.
  • Points-based — points earned from purchases, redeemed for rewards. More flexible but harder to understand.
  • Tiered — Silver/Gold/Platinum. Gamification retains customers.
  • Cashback — returned to internal account (b_sale_user_account).

Threshold System: Example Implementation

Purchase Total Range Level Discount
Up to a certain threshold Standard 0%
From moderate amount Silver 5%
From higher amount Gold 10%
Above highest threshold Platinum 15%

Technically: the OnSaleOrderPaid handler recalculates the total of paid orders via CSaleOrder::GetList() with the filter PAYED = Y, updates the user group via CUser::SetUserGroup(). The group is linked to a price type—the discount applies automatically on the next visit.

Additional features:

  • Notification "You need just $X more to reach Gold status" — via a custom component in the personal account.
  • Level validity period — annual (recalculated by CAgent) or permanent.
  • Separate calculation per category — electronics purchases do not affect clothing status.
Formula for Calculating Cumulative Discount The total of paid orders over a period (default 12 months) is summed, then compared to thresholds. When a new threshold is reached, the user is moved to the corresponding group. Example: a customer has made purchases totaling $X — they are in "Silver" (5%). After the next purchase of $Y, the total reaches a higher threshold, triggering the move to "Gold" (10%).

How It Works in Practice: A Case Study

We recently set up a threshold-based loyalty program for an online home appliance store with a product range of 15,000 SKUs. Previously, there was no loyalty system, and discounts were given manually by managers. We implemented a four-level threshold system. Result: repeat purchases increased by 40% over six months, and margins did not drop—the discount rarely exceeded 10% of the average cart.

Promo Codes and Their Possibilities

Management via CSaleDiscount and a custom administrative interface:

  • Single-use — unique code linked to a coupon (b_sale_discount_coupon).
  • Multi-use — shared code with a usage limit via MAX_USE.
  • Personal — linked to USER_ID.
  • Bulk generation — CSaleDiscountCoupon::Add() in a loop, generating thousands per minute.

Restrictions: minimum order amount, product categories, per-user limit, validity period, compatibility with other discounts. Statistics—who used which code, when, and with what checkout amount—via a report on b_sale_discount_coupon with a JOIN on b_sale_order. Linking to UTM tags shows which channel actually drives conversions.

Wholesale Pricing (B2B)

Mechanisms not available out of the box:

  • Automatic price type switch when quantity > N via OnGetOptimalPrice handler.
  • Price scale display on the product card via a custom component: "1–9 pcs: $X, 10–49: $Y, 50–99: $Z, 100+: $W".
  • Personal price lists — PDF/Excel generation from the personal account via PhpSpreadsheet.
  • Special price request form → lead in CRM.
  • Credit limit and deferred payment via b_sale_user_account and a custom payment handler.

Promotions and Personalization

Scheduling via ACTIVE_FROM / ACTIVE_TO — automatic start and end. Countdown timer — JS component linked to the item's ACTIVE_TO. Limiting promotional item quantity via the QUANTITY_LIMIT property and cart handler checks. A "Promotions" section — via smart filter on the IS_SALE = Y property.

Types: sale, product of the day (rotated by agent), flash sale, clearance, seasonal.

Personalization:

  • VIP discounts via individual user group → personal price type.
  • Corporate terms: deferred payment, custom delivery.
  • Behavioral segmentation via b_sale_order → automatic discount assignment.
  • Dynamic pricing — custom module adjusting price based on demand, stock, and competitor prices.

Integration with 1C

  • Import price types via CommerceML (standard exchange bitrix:catalog.import.1c).
  • Sync discount cards: card number → user group → price type.
  • Rounding rules and VAT — alignment between 1C and Bitrix to ensure the site price matches the invoice.
  • Scheduled updates (cron + agent) or real-time via REST API.

How We Configure Prices and Discounts: Step-by-Step Process

  1. Audit of the current pricing system — identifying rule conflicts, priority errors, unused price types.
  2. Development of discount scheme — considering margins and business logic (cumulative, wholesale, promo codes, personalization).
  3. Cart rule configuration — priorities, flags, exceptions.
  4. 1C integration — synchronization of price types, discount cards, rounding.
  5. Testing — load testing with 100+ active rules, conflict checks.
  6. Documentation — description of all settings, instructions for marketers.
  7. Manager training — how to create and disable promotions without risk.
  8. 30-day support — fix any anomalies after launch.

Timelines

Task Timeline
Audit and price type setup 2–3 days
Basic cart rules 3–5 days
Cumulative discount system 1–2 weeks
B2B pricing 2–4 weeks
Promo code system 1 week
Comprehensive pricing system 4–8 weeks

Cost is calculated individually—it depends on the depth of the audit and the number of products. Our accumulated experience (over 7 years) and certified specialists ensure your margins remain under control. Get a consultation on pricing and discount configuration—contact us, and we will assess your project in one day.