Brother Label Printer Integration with 1C-Bitrix

1C-Bitrix Integration with Brother Label Printers

When switching to self-adhesive labels, many online stores face a problem: Zebra printers are expensive and overkill for small volumes. Brother offers a budget-friendly alternative, but integration with Bitrix requires a non-standard approach—via the system printer rather than a direct data stream. We have experience of over 10 projects integrating Brother into the 1C-Bitrix ecosystem and guarantee stable printing in office and light warehouse scenarios.

Brother is an alternative to Zebra for office and light warehouse tasks. The QL series (thermal printing on DK tapes) and PT series (label printers) are used where small batches of labels are needed: packaging marking, address labels for shipments, shelf labels. The key difference from Zebra: Brother works primarily through system printer (GDI/CUPS), not through RAW TCP/IP with ZPL. Brother is 30–50% faster to set up for small businesses—no need to learn ZPL, basic PHP knowledge is enough.

Why Brother instead of Zebra for starters?

Brother is significantly more cost-effective for volumes up to 500 labels per day: the printer cost is 2–3 times lower, and integration setup takes 3–5 days less. For an online store with 50–200 orders per day, this is the optimal solution. If volumes grow, we can scale the system to Zebra without data loss.

Interaction methods with Brother printer

Option 1: Via system printer (recommended for office)

Brother is installed as a system printer in Windows or macOS. Bitrix generates a PDF or PNG of the required size and sends it to print via a system command:

function printLabelViaCups(string $pdfPath, string $printerName): bool
{
    $cmd = escapeshellcmd("lp -d " . escapeshellarg($printerName) . " " . escapeshellarg($pdfPath));
    exec($cmd . ' 2>&1', $output, $returnCode);
    return $returnCode === 0;
}

For Windows — similarly via SumatraPDF -print-to or mspaint /pt.

Option 2: Brother SDK / b-PAC (Windows only)

Brother provides a COM object b-PAC for working with .lbx templates in P-touch Editor. Integration via PHP COM interface:

$doc = new COM('bpac.Document');
$doc->Open('C:\\Labels\\price_label.lbx');
$doc->GetObject('barcode')->Text  = $barcode;
$doc->GetObject('price')->Text    = number_format($price, 2, ',', ' ') . ' rub.';
$doc->GetObject('name')->Text     = $productName;
$doc->StartPrint('', 0);
$doc->PrintOut(1, 0);
$doc->EndPrint();
$doc->Close();

This approach works only if PHP runs on a Windows server with Brother P-touch Editor installed. Not applicable for production servers under Linux.

Option 3: Brother Web API (QL-820NWB and newer models)

Some network Brother models have a web API. Documentation is model-specific, but the general principle: HTTP POST with base64-encoded image or PDF. This method is faster than system printing but requires additional development on the Bitrix side.

How to organize a print queue for Brother?

Unlike Zebra (where TCP sending is fast), printing via system printer takes time. We use the same queue architecture bl_brother_print_queue:

CREATE TABLE bl_brother_print_queue (
    id           SERIAL PRIMARY KEY,
    printer_name VARCHAR(128) NOT NULL,  -- name in CUPS
    template     VARCHAR(64) NOT NULL,
    product_id   INT,
    data_json    JSONB,
    copies       SMALLINT DEFAULT 1,
    status       VARCHAR(20) DEFAULT 'pending',
    created_at   TIMESTAMP DEFAULT NOW(),
    processed_at TIMESTAMP
);

A Bitrix agent takes jobs from the queue, renders a PNG via BrotherLabelRenderer, and sends it to CUPS. For large volumes, you can scale by using multiple printers and running several agents in parallel.

Label generation on the Bitrix side

For Linux servers (Option 1), generate the label image via GD or Imagick:

class BrotherLabelRenderer
{
    public function renderPriceLabel(array $product, int $widthMm = 62, int $heightMm = 29): string
    {
        $dpi = 300;
        $wPx = (int)($widthMm / 25.4 * $dpi);
        $hPx = (int)($heightMm / 25.4 * $dpi);

        $image = imagecreatetruecolor($wPx, $hPx);
        $white = imagecolorallocate($image, 255, 255, 255);
        $black = imagecolorallocate($image, 0, 0, 0);
        imagefill($image, 0, 0, $white);

        // Product name (use TTF font)
        $fontPath = $_SERVER['DOCUMENT_ROOT'] . '/local/fonts/DejaVuSans.ttf';
        imagettftext($image, 14, 0, 20, 60, $black, $fontPath, mb_substr($product['NAME'], 0, 35));

        // Price large
        $price = number_format($product['PRICE'], 2, ',', ' ') . ' rub.';
        imagettftext($image, 28, 0, 20, 120, $black, $fontPath, $price);

        // Barcode via library (picqer/php-barcode-generator)
        $barcodeGenerator = new \Picqer\Barcode\BarcodeGeneratorPNG();
        $barcodePng = $barcodeGenerator->getBarcode($product['BARCODE'], $barcodeGenerator::TYPE_EAN_13, 2, 60);
        $barcodeImg = imagecreatefromstring($barcodePng);
        imagecopy($image, $barcodeImg, 20, 150, 0, 0, imagesx($barcodeImg), imagesy($barcodeImg));

        $tmpPath = sys_get_temp_dir() . '/label_' . $product['ID'] . '_' . time() . '.png';
        imagepng($image, $tmpPath);
        imagedestroy($image);
        return $tmpPath;
    }
}

Imagick gives sharper fonts and supports vector elements. We recommend using it on servers with PHP 8.1+.

Method comparison

Integration with the administrative interface

In the Bitrix product card, we add a "Print label" button—it adds a job to the queue with printer selection from the list (bl_brother_printers). When bulk-selecting products in a list, a group action "Print labels" is available.

A "Print labels for shipment" button is added to the order admin card: it generates an address label (name, address, order number) and picking labels. All templates are easily customizable to your company's design—we provide SVG sources.

Scope of work

• Label renderer with barcode, price, name support (GD/Imagick) — 2 days
• Print queue + agent with error handling and retries — 1 day
• System printer integration (CUPS/Windows) — 1 day
• Print buttons in product and order cards — 2 days
• Testing with a real Brother printer — 1 day
• Installation and setup documentation — included
• 2 weeks of post-launch support — free of charge

Timeline

We will evaluate your project for free—just describe the task. We will perform a turnkey integration in 7–9 business days with a guarantee of stable operation.

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.