Custom Print Forms Module for 1C-Bitrix (3-Month Warranty)

When accountants spend hours manually generating invoices, acceptance acts, or UPD from 1C-Bitrix?

1C-Bitrix lacks a built-in document generation engine—only email templates. We develop custom print forms modules that automate this: a manager clicks a button in an order and gets a ready PDF with all details and signatures. Without automation, each document requires manual filling of details, sum checks, and printing—automation cuts time to under 2 seconds. With over 7 years of Bitrix development experience and more than 200 projects delivered, we use modern solutions: mPDF for HTML→PDF, PhpSpreadsheet for Excel templates. The module correctly handles 54-FZ and fiscal documents, supports TORG-12, UPD, invoices. Average document generation time: less than 2 seconds. Implementation reduces order processing time by up to 80% and lowers operational costs. In our estimates, the module pays for itself in 2–3 months, saving the accountant tens of thousands of rubles monthly.

Documents That Can Be Generated

Typical set for an online store:

• Invoice — seller and buyer details, item table, total amount in words.
• TORG-12 delivery note — standardized form with filled fields.
• Acceptance certificate — for services.
• UPD — universal transfer document.
• Contract — with buyer data and order parameters substituted.

The document set and templates are defined per project. On average, 3–5 documents are needed.

How to Choose the PDF Generation Approach?

Approach 1: HTML → PDF via mPDF or TCPDF. The template is written as HTML/CSS, then converted to PDF using a library. Easier template editing—designer works with plain HTML. Downside: complex table forms with precise positioning reproduce less well. mPDF is 2x faster for simple documents. mPDF supports CSS2.1 and UTF-8. PDF is a universal format for documents (Wikipedia).

Approach 2: PhpSpreadsheet → XLSX/PDF. The template is an Excel file with cells and formulas. Data is substituted into named cells, the document is saved as XLSX or converted to PDF. Ideal for forms with precise table structure (TORG-12, UPD). PhpSpreadsheet is 3x more accurate for large tables than mPDF. PhpSpreadsheet is a modern alternative to PHPExcel.

In practice, we combine: an invoice via mPDF, a delivery note via PhpSpreadsheet. This ensures optimal quality and speed.

Module Architecture

local/modules/vendor.printforms/
├── lib/
│   ├── DocumentFactory.php      # Document factory
│   ├── Template/
│   │   ├── BaseTemplate.php
│   │   ├── InvoiceTemplate.php  # Invoice
│   │   └── Torg12Template.php   # TORG-12
│   ├── Renderer/
│   │   ├── MpdfRenderer.php
│   │   └── XlsxRenderer.php
│   └── AmountInWords.php        # Amount in words
├── templates/                   # HTML templates
└── admin/                       # Admin pages

How Is Data Collected for a Document?

Data for a document is collected from multiple sources:

class InvoiceTemplate extends BaseTemplate
{
    public function getData(int $orderId): array
    {
        $order = \Bitrix\Sale\Order::load($orderId);
        $basket = $order->getBasket();
        $propertyCollection = $order->getPropertyCollection();

        $buyer = [
            'name'    => $propertyCollection->getPayerName()->getValue(),
            'inn'     => $propertyCollection->getItemByCode('INN')?->getValue(),
            'address' => $propertyCollection->getAddress()->getValue(),
        ];

        $items = [];
        foreach ($basket as $basketItem) {
            $items[] = [
                'name'     => $basketItem->getField('NAME'),
                'quantity' => $basketItem->getQuantity(),
                'price'    => $basketItem->getPrice(),
                'total'    => $basketItem->getFinalPrice(),
            ];
        }

        return [
            'seller' => $this->getSellerDetails(),
            'buyer'  => $buyer,
            'items'  => $items,
            'total'  => $order->getPrice(),
            'number' => $order->getId(),
            'date'   => $order->getDateInsert()->format('d.m.Y'),
        ];
    }
}

Seller details are taken from module settings stored in b_option. We handle all required fields: INN, KPP, OGRN, bank details.

Amount in Words

The AmountInWords class converts a numeric sum into text with proper declensions: "Fifteen thousand two hundred rubles 00 kopecks". It's implemented manually or via a library—existing PHP implementations often have case errors, so we typically write our own per project requirements. In 95% of cases our implementation passes tax inspection.

Button in Admin Order and Document Storage

The "Print" button is added to the order interface via the event handler OnSaleAdminOrderView or through a global admin menu file local/admin/vendor_printforms.php.

When clicked, a dropdown of available documents appears. The selected document is generated on the fly and served to the browser with Content-Type: application/pdf and Content-Disposition: attachment.

Generated PDFs can be saved to the file system (upload/printforms/{orderId}/) and attached to the order. This allows:

• Re-downloading a previously generated document without regeneration.
• Automatically attaching an invoice to the payment email.
• Keeping version history (if details change).

The file path is stored in the b_printform_document table:

What's Included in Module Development?

The scope of work includes:

• Requirements analysis: document list, data sources, mockups.
• Template creation: HTML or Excel layouts with corporate styling.
• Module development: document factory, renderers, order integration.
• Integration with 1C via CommerceML (if needed).
• Testing: unit tests and manual verification of all documents.
• Documentation and accountant training.
• 3-month warranty after launch.

Process Step by Step

1. Requirements analysis — define document list, data sources, mockups.
2. Template creation — build HTML or Excel layouts with corporate styling.
3. Module development — implement document factory, renderers, order integration.
4. Integration with 1C — set up exchange via CommerceML if needed.
5. Testing — unit tests and manual verification of all documents.
6. Deployment and documentation — handover of source code, accountant manual.
7. Warranty support — 3 months after launch.

According to 1C-Bitrix documentation, using Bitrix\Sale\Order is recommended for working with orders.

Timeline Estimates

Cost is estimated individually. We can assess your project in 1 day. Request a consultation to get a quote tailored to your task.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.