Automating Bitrix24 Business Processes: From Simple to Complex Scenarios
A travel request hangs: the manager doesn’t see the notification, the accountant misses the deadline. Each such failure costs 5,000 rubles of working time. Manual processing of 20 requests takes 4 hours for a manager. Bitrix24 business processes automate this chain—but only if you choose the right tool: BPs or CRM robots. We break down the criteria and set up the process for your tasks.
According to statistics, companies lose up to 30% of time on approvals. Automation returns those hours and saves up to 180,000 rubles per year on operational expenses. This article contains real examples from practice, technical details, and a step-by-step setup scheme. Integration with 1C via CommerceML allows automating document exchange and procurement approval.
How to distinguish a business process from a CRM robot?
CRM robots are a simplified designer for linear scenarios inside the funnel. Business processes are an engine with branching, loops, waiting for user actions, and conditions. Technically both run on \Bitrix\Bizproc\Workflow, but the BP editor gives more elements: “If-Then-Else”, “Loop”, “Parallel Actions”, “Assignment for user”. According to the Bizproc documentation, this is the main tool for complex processes.
| Criterion |
CRM Robots |
Business Processes |
| Complexity |
Up to 10 steps |
Any, with branching and loops |
| Conditions |
Only by CRM fields |
Full conditions, variables |
| User actions |
No |
Yes (assignments, confirmations) |
| Performance |
Faster on large volumes |
Heavier under high loads |
Use BPs when:
- user action is required (confirm, reject, specify data)
- there is branching by conditions
- the process involves several departments sequentially
- loops or parallel branches are needed
Which entities support business processes in Bitrix24?
BPs work on four entity types: list elements (requests, registers), disk documents, CRM elements, site pages (on-premise). For corporate requests, Lists are most often used. Path: Bitrix24 → Lists → [List] → Business Processes → Add. In 10 minutes, a template for vacation approval is configured.
Business process variables and their application
BPs operate with three types: parameters (passed at launch, e.g. request amount), variables (internal, e.g. voting result), document fields. They are passed via {=Variable:VariableName} or {=Document:FIELD_NAME}. For example, the variable {=Document:Sum} allows branching: if sum exceeds a threshold – approval with the financial director.
Setting up a business process in 5 steps
- Requirements analysis. We identify approval points, roles, conditions, throughput (e.g. 50 requests per day).
- Scheme design. We draw a graph in the BP editor – using assignments, conditions, waits.
- Implementation. We configure actions: upon request creation, a chain of assignments launches.
- Testing. We check on 10 test elements all branches, fix errors.
- Deployment and training. We launch into production, instruct employees, record feedback.
Practical example: procurement approval
Client – a manufacturing company: 100 purchase requests per month, the process was via email – 40% were lost. We configured a BP on the “Purchase Requests” list:
- Roles: manager (approves up to a set limit), director (above).
- Branching: if urgent → chat notification, otherwise – email.
- Result: approval time reduced from 3 days to 6 hours, resulting in significant annual savings.
What is included in the business process setup
Each project includes:
- documentation of the BP scheme (graph, roles, conditions)
- access and user rights configuration
- writing instructions for employees
- testing on 10–20 elements
- support for 30 days after launch
Typical mistakes when setting up BPs:
- Wrong choice of launch type (manual instead of automatic).
- Lack of error handling (process freezes on failure).
- Excessive assignments that slow down the process.
- Not accounting for performance: on 1000+ elements, BP may slow down.
We identify these mistakes during testing and fix them before deployment.
Process and timelines
We work in stages: analysis → design → implementation → test → deploy. In analysis we record every approval point, roles and conditions.
| BP Type |
Estimated Time |
| Simple linear |
2–3 hours |
| With several approval stages |
4–6 hours |
| Complex with branching and variables |
1 day |
Cost is calculated individually after task analysis. We assess the project for free. Contact us for a consultation on your tasks. Order a setup and we will turn chaos into streamlined automation.
Why choose us?
Experience in Bitrix – over 10 years. We have completed 50+ automation projects. 1C-Bitrix certificates confirm qualification. We guarantee the process works – if something goes wrong, we fix it without additional charges.
How Choosing the Wrong 1C-Bitrix Edition Breaks Your Project
You bought Small Business, launched a store, traffic grew to 5,000 unique visitors per day — and the site crashed. Composite cache is only available in Business, web cluster too. An upgrade costs the difference in license price plus work to configure new modules. Choosing and configuring the right 1C-Bitrix edition upfront saves up to 40% on licensing. It also avoids unplanned upgrade costs — saving on average 15,000–30,000 RUB when upgrading from Small Business to Business in advance instead of urgently. Over 8 years of working with Bitrix, we have performed over 200 upgrades and seen all typical mistakes: from buying Start for a 50,000-product catalog to using Business for a landing page with 100 visits per day. Our principle is to select the edition that matches your real needs and configure it so you do not overpay for unnecessary modules — and also do not hit a ceiling at the first traffic spike.
1C-Bitrix Editions: Site Management
Four editions, and the difference lies not in the number of features but in the available core modules. The official 1C-Bitrix documentation states that composite cache is only available in Business and above.
| Module / Feature |
Start |
Standard |
Small Business |
Business |
| Information blocks |
+ |
+ |
+ |
+ |
| Web forms |
+ |
+ |
+ |
+ |
| Basic SEO |
+ |
+ |
+ |
+ |
| Blog, forum, social network |
– |
+ |
+ |
+ |
sale (e-store) module |
– |
– |
+ |
+ |
1C exchange (catalog) |
– |
– |
+ |
+ |
Composite cache (main.composite) |
– |
– |
– |
+ |
Web cluster (cluster) |
– |
– |
– |
+ |
| Multisite |
– |
– |
– |
+ |
| REST API |
– |
– |
– |
+ |
Start is minimal, only content modules: iblock, form, basic SEO. For business card sites and landing pages. No sale module — cannot build a store.
Standard adds communication: blog, social network, forum, extended tech support. For corporate sites and portals with user-generated content.
Small Business is the first edition with e-commerce: the sale module appears. Comfortable ceiling is up to about 10,000 products without serious optimization. For small stores and catalogs with ordering.
Business is the full set: composite cache (TTFB drops from 800 ms to 50–80 ms — 10–15 times faster), web cluster, multisite, multi-warehouse, REST API. For large stores, marketplaces, projects with 10,000+ visitors per day.
How Does Composite Cache Reduce Server Load?
Composite cache (main.composite) speeds up page loading 10–15 times compared to dynamic generation. For a store with 3,000+ visitors per day, without composite the server starts struggling: average response time increases, database overload, checkout pages time out. Composite solves this radically — HTML is served by nginx without running PHP. It is important to correctly configure exclude masks for cart, personal account, and pages requiring real-time data. We configure this on every upgrade to Business.
1C-Bitrix official documentation: "Composite cache is available only in Business edition and higher."
Avoiding Common Mistakes in Edition Selection
Typical Mistakes
- Buying Start for an online store — no
sale module, you either need to upgrade immediately or hack a custom ordering system.
- Choosing Small Business for a project that will grow to 10,000 products in six months — composite cache cannot be enabled, upgrading to Business costs the license difference plus configuration work.
- Using Business for a landing page — overpaying for features that will never be used.
Choosing an Edition for an Online Store
| Store Type |
Recommended Edition |
Key Limitation |
| Up to 1,000 products, traffic up to 500 unique visitors/day |
Small Business |
No composite cache (TTFB > 500 ms at peaks) |
| 1,000–10,000 products, 500–5,000 unique visitors/day |
Small Business with tuning or Business (immediately) |
Load hits PHP-FPM limit |
| 10,000+ products, 5,000+ unique visitors/day |
Business |
Need composite + cluster |
| Marketplace, 100,000+ products |
Business + web cluster |
Horizontal scaling mandatory |
Hard Criteria for Edition Selection
By modules:
- 1C exchange (
catalog) → at least Small Business
- Composite cache (
main.composite) → only Business
- Web cluster (
cluster) → only Business
- Multisite → only Business
- REST API → only Business
By load:
- Up to 1,000 unique visitors/day — any edition can handle
- 1,000–10,000 unique visitors/day — Small Business with nginx/php-fpm tuning hits a ceiling. Business with composite cache is the right choice
- 10,000+ unique visitors/day — only Business with composite and cluster
By budget:
- The price difference between editions is 2-5x
- Upgrade at any time — pay the difference in license cost
- Our principle: take the minimum sufficient. But if you know you will need composite in six months, get Business immediately, because an upgrade also involves configuration work. The total upgrade cost (license difference + setup) typically ranges from 10,000 to 50,000 RUB.
What Happens If You Ignore License Renewal?
An active license provides updates — new versions, security patches, bug fixes, marketplace access, and vendor tech support. When it expires, the site continues to work but remains without updates. For stores this is dangerous — security patches fix vulnerabilities in sale, catalog, main modules. Data leaks from b_sale_order or b_user are just a matter of time. Renewal costs a fraction of buying a new license — typically 20–30% of the full price. Regular renewal is insurance against unpatched CVEs.
Cost Benefits of Planned Edition Upgrades
1C-Bitrix allows upgrading without reinstallation — data is preserved. Process:
- Pay the difference in license cost
- Activate new key: Settings → Updates → Registration
- Install newly available modules via admin panel
- Configure new functionality
- Test compatibility
What we do during an upgrade:
- Check custom code for conflicts with new modules — especially custom event handlers like
OnBeforeOrderAdd, OnSaleBasketSaved
- Enable and configure composite cache — correct exclude masks for dynamic pages (cart, checkout, personal account)
- Configure multi-warehouse if needed —
b_catalog_store, warehouse selection rules
- Run full functional testing on staging
- Document changes
As a result, you get:
- A working site on the new edition with no data loss
- Configured composite cache (if upgraded to Business)
- Testing report and recommendations for further optimization
- Access to staging and documentation of changes
Integrating Site Management with Bitrix24
A common scenario: site on 1C-Bitrix + CRM in Bitrix24. Orders from b_sale_order automatically become leads or deals, unified authorization, client base synchronization. Site forms (form or custom) feed into the CRM funnel. These are two separate licenses and two separate products — integration between them is standard and stable.
Practical Recommendations
- Do not skimp on the edition if you know the functionality will be needed in six months. Upgrading costs the same difference plus configuration and testing.
- Business for projects with growth ambitions — composite cache pays for the price difference at the first traffic spike. Without composite, 3,000+ unique visitors/day will strain the server.
- Bitrix24 and Site Management are different products with different licenses. Confusion here costs money.
- Renew your license annually — renewal is much cheaper than buying a new one, and without updates you risk unpatched CVEs.
What We Offer: Turnkey Selection and Configuration
We do not just consult — we handle the full cycle: analyze your current project, select the edition, purchase the license (if needed), migrate, configure all modules, and train your team. As part of the service, you get:
- An edition selection report with justification
- Migration plan (if upgrading)
- Fully set up staging with the new edition
- Composite cache and cluster configuration (if necessary)
- Documentation of the new configuration
- Guarantee of site functionality after the transition
Contact us today — we can assess your project within one business day and propose the optimal configuration. Receive a personalized cost estimate for selecting and configuring your 1C-Bitrix edition right now.