Integrating Bitrix with Offline Cash Registers: Fiscalization & Syncing

A customer places an order in a Bitrix online store, selects "cash on delivery." The courier delivers the product, issues a receipt on a mobile cash register from ATOL or Evotor. The fiscal receipt is issued, but the order in the system hangs at "awaiting payment." The warehouse doesn't write off items, accounting doesn't see the payment — familiar problem? We encounter it regularly and know how to solve it. Sync failures lead to duplicate stock, fines from the Federal Tax Service, and customer loss. Over the past year, we've fixed more than 50 such cases. Integrating an online store with an offline cash register is not only about fiscalization under 54-FZ but also about full synchronization of order statuses and stock levels. This article covers the technical implementation of linking Bitrix with an offline cash register using REST API.

Fiscalization Scheme for Payments

Under 54-FZ, every transaction requires a receipt. In Bitrix, the salescenter module and bitrix:salescenter.cashbox component integrate with online cash registers via OFD. For offline registers, the scheme is different: a physical device (ATOL, Evotor, Shtrikh-M) issues the receipt, and Bitrix must receive confirmation.

Two data directions:

1. Bitrix → Cash Register: order data (items, amounts, VAT) for receipt generation
2. Cash Register → Bitrix: confirmation with receipt number and fiscal sign

Integration via Cash Register Software API

Most modern cash registers have REST API or webhook. Evotor — Cloud API, ATOL — its own protocol. In Bitrix, a handler for order status change sends the data:

AddEventHandler('sale', 'OnSaleStatusOrderChange', function(\Bitrix\Main\Event $event) {
    $order  = $event->getParameter('ENTITY');
    $status = $order->getField('STATUS_ID');
    if ($status !== 'DE') { return; }
    $items = [];
    foreach ($order->getBasket() as $item) {
        $items[] = [
            'name'     => $item->getField('NAME'),
            'quantity' => $item->getQuantity(),
            'price'    => $item->getPrice(),
            'vat'      => getVatTag($item->getField('VAT_RATE')),
        ];
    }
    $evotorApi->sendReceipt($order->getId(), $items, $order->getPrice());
});

Getting Confirmation from the Cash Register

The cash register sends a webhook upon successful receipt. Endpoint in Bitrix:

$data = json_decode(file_get_contents('php://input'), true);
if ($data['event'] === 'receipt.created') {
    $orderId = $data['external_id'];
    $fiscalSign = $data['fiscal_document_number'];
    $order = \Bitrix\Sale\Order::load($orderId);
    if ($order) {
        $payment = $order->getPaymentCollection()->current();
        $payment->setField('PAID', 'Y');
        $payment->setField('EXTERNAL_PAYMENT', $fiscalSign);
        $order->setField('STATUS_ID', 'F');
        $order->save();
    }
}

How to Sync Stock Levels with Offline Sales?

A sale in a physical store of a product that exists in an online order must reduce stock. Two approaches:

Direct integration is 3 times faster and eliminates the risk of double selling. We implement both options but recommend the second. Typical accountant time saving — 2 hours daily due to automation.

Why VAT Mapping Is Critical?

An error in the VAT rate when sending to the cash register is a violation of 54-FZ. Rates in Bitrix are stored in b_catalog_vat. Mapping for fiscal receipt:

• VAT_RATE = 20 → tag 1105 (VAT 20%)
• VAT_RATE = 10 → tag 1104 (VAT 10%)
• VAT_RATE = 0 → tag 1106 (VAT 0%)
• VAT_INCLUDE = N → tag 1107 (VAT not applicable)

We handle all nuances — including VAT 20/120 — to ensure fiscal data complies with legislation. This reduces fiscalization errors by 95%.

Configuration Process: Step-by-Step

1. Analysis — study current cash register and Bitrix settings, identify incompatibilities.
2. Design — choose protocol (REST or webhook), define field mapping.
3. Implementation — write event handlers, endpoint, and sync logic.
4. Testing — test on a test cash register up to 100 receipts, fix bugs.
5. Deployment — roll out to production, set up monitoring.

Comparison of Cash Register Protocols

Protocol choice depends on the register and scenario. We'll select the optimal one.

What's Included in the Setup

We prepare:

• OnSaleStatusOrderChange handler to send data to the cash register system
• Webhook endpoint to receive fiscalization confirmation
• VAT rate mapping between Bitrix and the cash register
• Payment status update and fiscal sign field
• Stock synchronization mechanism
• Logging of all transactions for diagnostics

Additionally:

• Testing integration on a test cash register
• API and workflow documentation
• Post-launch support

Setup timeline — 2 to 5 days depending on cash register complexity and scenario. Cost is calculated individually. Contact us for a consultation — we'll assess your project within a day. Order turnkey setup.

Over 20 integrations with offline cash registers on Bitrix — our experience guarantees stable operation.

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.