Bitrix24 for 223-FZ Procurement: Practical Setup Guide

Procurement Department Drowning in Excel

Procurement under Federal Law No. 223-FZ requires strict adherence to deadlines — missing a deadline can result in fines of up to 300,000 rubles. Bitrix24 can become a single center for procurement management, but without proper configuration it's just another tracking tool. We share practical experience: how to turn Bitrix24 into a procurement coordinator, reduce the load on the department, and eliminate human error. Automation pays off in 3–4 months, reducing late submissions by 70% and approval costs by 30%.

Why Bitrix24 Doesn't Cope 'Out of the Box'

Out-of-the-box Bitrix24 does not account for 223-FZ specifics: strict deadlines, special procedure stages, need for protocol generation, and interaction with the Unified Information System (EIS). Therefore, setup requires customization of CRM, business processes, and access rights. A properly configured system is a full-fledged procurement coordinator; without configuration, it's just a mailbox for emails.

What Is Configured in Bitrix24 for 223-FZ

CRM for Procurement Procedures

Each procurement is a deal in CRM. Pipeline stages correspond to procedure phases:

• Procurement Planning → Plan Publication → Documentation Preparation → Notice Publication → Bid Acceptance → Bid Review → Winner Determination → Contract Signing → Execution → Archive

Custom deal fields: PURCHASE_PROCEDURE (list: request for quotations, request for proposals, tender, auction), INITIAL_PRICE (number), PROCUREMENT_SUBJECT (string), EIS_NUMBER (string), BID_SUBMISSION_DEADLINE (date), FINANCING (list: 44-FZ / 223-FZ / commercial).

Automation via Business Processes

Bitrix24 robots trigger on deal stage transitions:

• When moving to the 'Notice Publication' stage: task for the lawyer 'Check documentation', task for the responsible person 'Publish on EIS'
• 3 days before BID_SUBMISSION_DEADLINE: notification to the commission
• When moving to the 'Contract Signing' stage: task for contract approval via approval route

Document Templates

Bitrix24 generates standard documents (review protocol, evaluation protocol) from Word templates filling fields from CRM using macros like {DEAL.FIELD_NAME}.

How to Organize Procurement Document Storage?

Documents are stored on Bitrix24 Drive in folders linked to the deal. Folder structure:

Procurement/
└── Current Year/
    └── ZK-Current Number Server Equipment Supply/
        ├── 01_Planning/
        ├── 02_Documentation/
        ├── 03_Participant_Bids/
        ├── 04_Protocols/
        └── 05_Contract/

Folder permissions are assigned automatically via business process when creating a deal: the responsible person and commission get access, others do not.

How Does Bitrix24 Control Deadlines?

223-FZ deadlines are strict: for example, for a request for quotations, the publication period must be at least 5 working days. Bitrix24 manages deadlines through:

• Date-type fields in deals with automatic deadline calculation via formulas
• Tasks with deadlines linked to the deal
• Notifications N days before deadline via robots

Bitrix24 calculates working days (as opposed to calendar days) considering the production calendar — this is critical for correct 223-FZ deadline calculation. Automatic deadline control reduces late submissions by 70%.

Compare: in Excel, average time per procurement is 8 hours; with configured Bitrix24, it's 2–3 hours. A 3–4x difference. This is achieved through automatic notifications, clear task routing, and a unified document base.

What Is Included in Bitrix24 Setup for 223-FZ?

Full deliverables include: setup documentation (pipeline description, user guides), system access, employee training, and warranty support. Get in touch with our engineers — they will design a solution tailored to your regulations.

Limitations and What Is Configured Outside Bitrix24

Bitrix24 does not replace specialized systems for EIS interaction. Publishing notices and documentation on zakupki.gov.ru is done through the EIS personal account with an electronic signature — that's an external tool. Bitrix24 only stores the publication fact (date, EIS number) as a deal field and a confirmation task.

For organizations with high procurement volume (50+ procedures per year), it is recommended to use a specialized module or integration with systems like 'Kontur.Zakupki', 'Tenderplan', RTS-tender — with data transfer to Bitrix24 via REST API for team coordination.

Setup Timelines

A properly configured Bitrix24 for 223-FZ reduces the risk of missed deadlines, provides a history of each procurement, and gives management an overview of all active procedures. Order a consultation on setup — our engineers will design the pipeline, configure business processes, and conduct training, ensuring stable operation.

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.