Integration with ATOL Online for 1C-Bitrix

We build ATOL Online integration with 1C-Bitrix stores for turnkey fiscal compliance — cloud cash register receipts per 54-FZ without a physical device on-site. We meet 54-FZ requirements without purchasing physical cash registers. Typical cost savings: 25,000–50,000 rubles per year compared to a physical cash register. Receipts are fiscalized via the operator's REST API and forwarded to the OFD. The buyer receives an electronic receipt by email or SMS. The ready solution is deployed in 3–5 days. Our company has 10+ years of experience in 1C-Bitrix, 40+ completed fiscal integrations, and 5 years on the market. We have served clients with annual turnover from 2 to 200 million rubles.

We have 10+ years in 1C-Bitrix and 40+ completed integrations of fiscal services (ATOL, Robokassa, OFD.ru, YooKassa). Our portfolio includes clothing stores, electronics, FBO and FBS marketplaces, and B2B catalogs with turnovers from 2 to 200 million rubles a year. We work with labeled items from Honest Sign. We handle complex product matrices, hybrid tax schemes, and custom refund scenarios. According to 54-FZ, all online payments from individuals must go through a fiscal service within 5 minutes of payment.

Why a cloud cash register is better than a physical one for an online store

A physical cash register on the merchant side requires equipment purchase (from 25,000 ₽ per device), registration with the Federal Tax Service, an OFD contract (from 3,000 ₽ per year), maintenance, and replacement of the FN every 13–36 months. The cloud solution eliminates these costs — you pay a subscription per number of fiscalized receipts. Subscription cost starts from 1,500 ₽ per month for up to 500 receipts. For a store with up to 1000 orders per month, a SaaS cash register is 3–5 times cheaper than owning a set of devices.

If a store has a pickup point that accepts cash, you will need a physical cash register — the cloud service fiscalizes only non-cash online payments. For a hybrid scheme (online payment + offline handover with payment on site), we use the fiscal service only for online receipts and serve offline nodes with a separate physical cash register. We choose the approach based on the actual payment flow of your store.

How ATOL fits into the chain

ATOL guarantees 99.9% uptime, and we achieve over 99% callback success rate with our retry mechanism. The fiscalization payment chain:

1. The buyer pays for the order — the payment aggregator (YooKassa, Tinkoff, etc.) processes the transaction.
2. The aggregator sends a notification to Bitrix about successful payment.
3. Bitrix (or the integration module) creates a fiscalization request.
4. The ATOL service registers the receipt on the cloud cash register and sends it to the OFD in 1–3 seconds.
5. The buyer receives an electronic receipt by email or SMS.
6. Fiscal data (receipt number, FN, FP) returns to Bitrix via webhook.

Key point: ATOL works asynchronously. The receipt creation request is sent, but the result comes via webhook or on a status re-query. Ignoring this is the most common cause of 'lost' receipts and dissatisfied customers. In our projects, the callback handler always includes a retry queue and a dead-letter log.

Official ATOL module vs. custom integration

ATOL provides an official module atol.kkt54 for 1C-Bitrix — installed via Marketplace or manually. It covers the basic scenario and is suitable for stores with a typical product matrix and a single tax system.

After installation, configure in Store → Settings → ATOL:

In production we almost always need customizations or a replacement with a custom integration: separate accounting for OSN and USN, labeled items with auto-fill codes from Honest Sign, partial shipment scenarios, retry queue on ATOL timeouts, correct VAT distribution for delivery services. For stores with complex needs, custom integration reduces fiscalization errors by 30%. For these tasks, we write the integration directly with the REST API.

Structure of a receipt creation request

// Sending a receipt to ATOL
class AtolClient
{
    private string $token;
    private const API = 'https://online.atol.ru/possystem/v4/';

    public function getToken(): void
    {
        $resp = $this->post('getToken', [
            'login'    => ATOL_LOGIN,
            'pass'     => ATOL_PASSWORD,
        ]);
        $this->token = $resp['token'];
    }

    public function sendReceipt(array $order): array
    {
        $items = [];
        foreach ($order['basket'] as $item) {
            $items[] = [
                'name'          => mb_substr($item['name'], 0, 128), // ATOL limit
                'price'         => (float)$item['price'],
                'quantity'      => (float)$item['quantity'],
                'sum'           => round($item['price'] * $item['quantity'], 2),
                'payment_method'=> 'full_payment',
                'payment_object'=> 'commodity',
                'vat'           => ['type' => 'none'], // or 'vat20', 'vat10'
            ];
        }

        if ($order['delivery_price'] > 0) {
            $items[] = [
                'name'           => 'Delivery',
                'price'          => (float)$order['delivery_price'],
                'quantity'       => 1.0,
                'sum'            => (float)$order['delivery_price'],
                'payment_method' => 'full_payment',
                'payment_object' => 'service',
                'vat'            => ['type' => 'none'],
            ];
        }

        $payload = [
            'external_id' => 'BX-' . $order['id'] . '-' . time(),
            'receipt'     => [
                'client'   => [
                    'email' => $order['buyer_email'],
                    'phone' => $order['buyer_phone'] ?? null,
                ],
                'company'  => [
                    'email'           => ATOL_COMPANY_EMAIL,
                    'sno'             => 'osn', // tax system: osn|usn_income|usn_income_outcome|envd|esn|patent
                    'inn'             => ATOL_INN,
                    'payment_address' => ATOL_PAYMENT_ADDRESS,
                ],
                'items'    => $items,
                'payments' => [
                    [
                        'type' => 1,  // 1=electronic, 0=cash
                        'sum'  => (float)$order['total'],
                    ],
                ],
                'total'    => (float)$order['total'],
            ],
            'service'     => [
                'callback_url' => ATOL_CALLBACK_URL,
            ],
            'timestamp'   => date('d.m.Y H:i:s'),
        ];

        return $this->post(ATOL_GROUP_CODE . '/sell', $payload);
    }

    private function post(string $endpoint, array $data): array
    {
        $ch = curl_init(self::API . $endpoint);
        curl_setopt_array($ch, [
            CURLOPT_POST           => true,
            CURLOPT_POSTFIELDS     => json_encode($data),
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_HTTPHEADER     => [
                'Content-Type: application/json; charset=utf-8',
                'Token: ' . $this->token,
            ],
        ]);
        $response = curl_exec($ch);
        curl_close($ch);
        return json_decode($response, true) ?? [];
    }
}

Critical implementation details

Line item sums must exactly match total — ATOL checks this. A discrepancy of 1 kopeck causes an error. Typical rounding issue: three items at 33.33 rubles = 99.99, but total = 100.00. In our projects, the last item gets the remainder sum — the algorithm is covered by unit tests.

Item name — max 128 characters. We trim long names preserving meaning (drop attribute tail, keep category + brand + model).

Nomenclature code (field nomenclature_code) — mandatory for labeled goods: clothing, footwear, perfumes, dairy, tires, cameras, etc. The code comes from Honest Sign. If your store works in these niches, receipts will fail without it. We include this step by default for labeled items.

Asynchrony — the response to POST /sell contains only the task uuid. The actual fiscalization result comes in the callback. We store the uuid in a utility table atol_receipts and process the callback with at-least-once guarantee. We retry on network timeouts from ATOL. We alert the manager after 3 failed attempts.

Callback handler from the service

// local/api/atol-callback.php
$body = json_decode(file_get_contents('php://input'), true);

$uuid   = $body['uuid']   ?? '';
$status = $body['status'] ?? '';  // 'done' | 'fail'

if ($status === 'done') {
    $fiscalData = $body['payload']['fiscal_receipt_number'] ?? '';
    $fnNumber   = $body['payload']['fn_number'] ?? '';
    $fnDocument = $body['payload']['fiscal_document_number'] ?? '';

    // Save fiscal data to the order
    saveAtolReceiptData($uuid, [
        'fiscal_number' => $fiscalData,
        'fn'            => $fnNumber,
        'fd'            => $fnDocument,
        'status'        => 'done',
    ]);
} elseif ($status === 'fail') {
    $error = $body['payload']['message'] ?? 'Unknown error';
    logAtolError($uuid, $error);
    // Queue a retry
    scheduleAtolRetry($uuid);
}

http_response_code(200);
echo 'OK';

Refund receipt

For refunds, we send a refund receipt using the /sell_refund method (full) or /sell_correction (correction). The structure is identical to the original receipt, but the endpoint differs:

// Full refund receipt
$atol->post(ATOL_GROUP_CODE . '/sell_refund', $payload);

// Partial refund receipt — only returned items
// total and items contain only the returned part

Important: the refund receipt is checked by the tax office during audits. Discrepancies between internal refunds in the store and fiscalized refunds in the OFD can lead to fines of 10,000 rubles per unclosed refund. In our projects, we reconcile the refund register with ATOL daily via cron.

Our case: a clothing store with 50+ SKUs of labeled goods

One of our clients — an online clothing store on 1C-Bitrix with ~800 orders per month. Initially, the ATOL integration worked correctly for non-labeled items. After expanding the assortment with labeled goods, errors started. Some items were missing the nomenclature code from Honest Sign. ATOL returned fail with a missing mandatory field message.

Our solution: we added a mandatory 'Marking Code' field (UF_MARKING_CODE) to the 'Catalog' infoblock with DataMatrix format validation. When sending a receipt, we check for the code for labeled categories. If the code is missing, the order goes to 'Needs Verification' status, and the manager enters the code manually. We also connected auto-loading of codes from Honest Sign via its REST API and a background sync every hour.

Result: order processing time increased by 5–15 minutes. But the store eliminated fines for labeling violations (50,000 rubles per receipt missing a mandatory code) and passed the tax audit without remarks.

What's Included in the Work

Our standard ATOL integration package for 1C-Bitrix includes these deliverables:

• Integration documentation (API scheme, callback flow, configuration guide)
• AtolClient class with token handling, retries, and logging to atol.log
• Callback handler with retry queue and dead-letter logic
• Receipt register (utility table + admin page with statuses done/pending/fail)
• Daily reconciliation script between your store and the OFD (cron)
• Access to the admin receipt register
• One-hour training for your team on operational procedures
• Alerts setup for failures (Telegram and email)
• Operational documentation
• Testing in the ATOL staging environment before switching to production
• First month of post-launch support — we fix whatever comes up

Timeline

The cost is calculated based on the scope and specifics of your store — describe your stack and fiscalization scenarios, and we'll provide a free estimate within 1–2 days.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.