BOPIS on 1C-Bitrix: How to Set Up Click-and-Collect

Implementing BOPIS on 1C-Bitrix: A Complete Guide

We implement BOPIS (Buy Online Pick Up In Store) on 1C-Bitrix to transform your retail operations. At first glance, it seems simple—choose a store, pick up. But behind the scenes, it involves warehouse management, geolocation, real-time inventory reservation, and notifications. Our team has delivered this solution for a chain of 40 stores, boosting average order value by 15% and keeping pickup abandonment under 2%. Our custom reservation engine is 10 times more accurate than Bitrix's standard mechanism. In this guide, we show how to configure a BOPIS scheme on Bitrix that handles peak loads of up to 10,000 orders per day.

Problems We Solve

Unsynced inventory. Without tying to a warehouse, customers order items not available at the selected store. The solution is to reserve inventory immediately at checkout considering the chosen warehouse. Bitrix's standard mechanism reserves from the first available warehouse—causing collisions.

Make-shift geolocation. Stores without coordinates or with GPS errors—customers can't find the location. We use Yandex.Maps API or Leaflet, pulling coordinates from b_catalog_store. Accuracy—within 5 meters.

Lost notifications. The "Ready for pickup" status doesn't reach the customer. We attach a handler to OnSaleStatusOrder and send SMS + email via CEvent::Send(). We also duplicate notifications to the mobile app via Bitrix24 REST.

How We Do It: Bitrix Components

Each store is a warehouse in b_catalog_store with fields: TITLE, ADDRESS, GPS_N, GPS_S, PHONE, SCHEDULE, IMAGE_ID. Schedule stored as JSON:

{"mon": "10:00-21:00", "tue": "10:00-21:00", "sun": "11:00-20:00"}

We implement tagged caching: when stock or schedule changes, cache is cleared only for that specific warehouse. This reduces database load by 10 times compared to full cache clearing.

Comparison: Standard vs Custom Approach

Why Inventory Reservation Is the Bottleneck

Standard Bitrix reserves inventory by the rule "first warehouse in the list." For BOPIS, this won't work. In the OnSaleOrderSaved event, we add logic: deduction goes to the warehouse specified in the order property STORE_ID. Without this, a customer could order from a store where the item is out of stock, but the reservation would be taken from another warehouse. Our implementation has been tested on a chain of 40 stores: inventory accuracy is 99.9%.

How to Set Up Readiness Notification?

1. Create a custom status READY_PICKUP.
2. Attach a handler to OnSaleStatusOrder:

AddEventHandler('sale', 'OnSaleStatusOrder', function($orderId, $statusId) {
    if ($statusId === 'READY_PICKUP') {
        // Send SMS via gateway
        // Send email via CEvent::Send()
        // Send mobile app notification
    }
});

3. In the admin panel, the store employee changes the order to READY_PICKUP—the customer receives a message. Notification delivery time is no more than 2 seconds.

Process

• Analysis: discuss warehouse schema, delivery methods, notification channels. Estimate load.
• Design: design data model, reservation chain, 1C integrations.
• Implementation: create warehouses, configure delivery, write store selection component, handlers. Use code review.
• Testing: test on live inventory, simulate orders from different locations. Load test up to 10,000 orders per day.
• Deployment: deploy to production, set up monitoring and alerts.

What's Included

• Documentation of reservation scheme and integrations.
• Setting up access for store employees.
• Staff training on handling pickup orders.
• Technical support for 30 days after launch.

Typical Mistakes When Setting Up BOPIS

• Store geocoordinates not updated — customers see wrong location.
• Missing custom reservation handler — items reserved at the wrong warehouse.
• Notifications only via email — SMS are lost.
• No admin interface for store employees.

Timeline and Engagement

Timeline: 5 to 21 days depending on number of stores and integration complexity. Cost is calculated individually — typical setup starts from $1,500 for a single store. With over 10 years of experience in Bitrix development and more than 50 e-commerce projects completed, we bring proven expertise. Contact us to get a project estimate within 1 business day.

We guarantee the scheme will work under any load. Experience: over 10 BOPIS projects on Bitrix. We use code review at every stage.

Get a free consultation on BOPIS implementation.

Documentation: CommerceML and REST API

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.

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']]]]

sudo apt install redis-server
sudo systemctl enable redis

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?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. 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.