When an online store on 1C-Bitrix has 10,000 products and five customer categories (retail, wholesale, dealer, VIP, employees), manual configuration of rights and prices becomes a headache?
Customers see others' prices, discounts apply incorrectly, and closed dealer sections are open to anyone. The cause is chaotic configuration of buyer groups without relation to business logic. We solve this problem turnkey: we design segmentation for B2B and B2C, automate transitions between groups based on order totals, and integrate with 1C.
What problems does configuring buyer groups solve
Incorrect price group linking. Each product in the trade catalog can be linked to several price groups (base, wholesale, dealer). If a buyer from the "Retail" group sees a dealer price, it means their group has extra rights. We fix the settings in the "Store → Catalog → Price Groups" section: leave only the necessary links. This approach reduces complaints about incorrect prices by 3 times.
Closed sections visible to all. Sections with dealer documentation or internal promotions should be accessible only to certain groups. Without configuring infoblock section access rights, any user can see the content. We restrict visibility via CIBlockSectionRights.
Manual upgrade management. Automatic group upgrade based on order total is a typical B2B task. Without an OnBeforeUserUpdate event handler or agent, managers have to manually transfer customers. This takes up to 3 hours daily.
How we configure buyer groups
Let's take an example of a B2B building materials store. After auditing the current structure, we:
- Created groups: "Retail", "Small Wholesale", "Large Wholesale", "Dealer", "Employee".
- Linked each to its own price group. For dealers — a hidden section with price lists.
- Wrote a handler for the
OnSuccessCatalogOrder event — when order total reaches a certain threshold, the user is automatically moved to "Large Wholesale".
- Set up an agent for weekly synchronization with 1C: if the customer category changes in 1C, the group in Bitrix is updated.
Result: customers see correct prices, managers don't waste time on manual assignment, and hidden sections are open only to dealers. Automation speeds up group change by 3 times compared to manual.
Why standard group configuration is insufficient
Built-in Bitrix capabilities cover basic scenarios: price linking, coupon discounts, section restrictions. But for complex B2B logic (automatic transitions between groups, integration with CRM, different delivery conditions), customizations are required. We use the standard API (CGroup, CIBlockSectionRights, CPrice) without hacks. For example, the user group mechanism in Bitrix is based on the standard RBAC model, but dynamic segmentation requires extension.
How to automate group transition
Example configuration for a B2B store:
- Retail: only base price available
- Small Wholesale: automatic upgrade upon reaching a lower threshold
- Large Wholesale: upon reaching a higher threshold
- Dealer: access to hidden section with price lists
Handler for OnSuccessCatalogOrder checks the order total and upon reaching the threshold moves the user to the next group. This approach reduces manager workload by 5 times compared to manual upgrade.
What our work includes
- Audit of existing groups and access rights
- Designing segmentation for business processes
- Configuring groups, linking to prices, discounts, sections
- Implementing automatic assignment (events, agents)
- Testing on a copy of the site and providing documentation
Typical mistakes when configuring buyer groups
- Forgetting to restrict rights for service sections (admin part remains open).
- Not removing extra groups from price linking — buyer gets incorrect price.
- Confusing group priority when rights overlap.
Approach comparison
| Parameter |
Typical configuration |
Professional configuration |
| Speed |
1-2 hours |
3-5 hours (with automation up to 2 days) |
| Flexibility |
Only manual assignment |
Automatic transitions by total, status |
| Integration with 1C |
No |
Yes (CommerceML, REST API) |
| Documentation |
No |
We provide settings description |
| Guarantee |
No |
30 days free support |
Work phases
| Phase |
Duration |
Result |
| Analysis |
1-2 days |
Identify discrepancies, describe current structure |
| Design |
0.5-1 day |
Matrix of groups-prices-rights, approval with client |
| Implementation |
3-5 hours |
Create groups, links, write handlers |
| Testing |
1-2 days |
Verify all scenarios on test domain |
| Deployment |
0.5 day |
Move to production, train managers |
Timelines and cost
Basic configuration (up to 4 groups) — from 3 to 5 hours. If automation by order totals or integration with 1C is required — from 1 to 3 days. Cost is calculated individually after getting to know the project. We evaluate the scope for free and provide a fixed timeline.
If you have issues with customer segmentation or customers see others' prices, contact us for a consultation. Get a free audit of your current buyer groups. We have been working with Bitrix for over 10 years, completed 100+ online store implementations, and guarantee results. Order buyer group configuration and get rid of price confusion.
Official 1C-Bitrix documentation: "User Groups" — https://dev.1c-bitrix.ru/learning/course/index.php?COURSE_ID=43&LESSON_ID=3436
What Professional 1C-Bitrix Installation Includes
We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.
How to Choose Hosting and Edition for 1C-Bitrix Installation?
BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.
VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.
Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
What Server Settings Are Critical for 1C-Bitrix?
Web Server and PHP
nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.
Database and Caching
MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:
'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
SSL, Email, and Cron
SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.
Security and Administration
File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.
How Long Does 1C-Bitrix Installation and Configuration Take?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.
Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.
Deliverables
- Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
- Installed and activated license of the required edition.
- SSL certificate, email settings, cron and backups.
- Documentation: all configuration parameters, access credentials, cron tasks.
- Content manager training: how to log into admin panel, add products, upload images.
- Post-installation support for 30 days — consultations on settings.
Why Trust Professionals with Installation?
Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.
