Quality Document Binding to Products in 1C-Bitrix
We have developed an efficient mechanism for binding quality documents to products in 1C-Bitrix. Unlike conformity certificates, documents such as TR CU declarations, quality passports, test protocols, SGRs, and instructions for use require flexible storage and display. Our solution allows management of multiple document types with expiry control and bulk binding — exactly what is needed for catalogs with hundreds of items. Over 5 years of work, we have completed more than 50 projects integrating document workflow on Bitrix, and each time we encountered typical problems: inconvenient manual binding, loss of document relevance, difficulties with updating via CommerceML. In this article, we share a proven method that guarantees compliance and saves time. Implementation typically costs between $1,500 and $3,000 and saves up to $2,000 annually in manual labor.
Flexible Document Binding Setup
For flexible binding of multiple document types to products, the optimal scheme uses a separate infoblock. Using ready-made modules often requires modifications, while our implementation is initially optimized for your catalog structure — this saves up to 30% of maintenance time and reduces manual binding effort by 80%.
Infoblock QUALITY_DOCS (no catalog type needed, regular content):
| Property |
Code |
Type |
Description |
| Document type |
DOC_TYPE |
List |
Declaration / Certificate / Quality passport / SGR |
| File |
FILE |
File |
PDF or image |
| Document number |
DOC_NUMBER |
String |
Declaration/certificate number |
| Valid until |
VALID_TO |
Date |
Expiry date |
| Products |
PRODUCTS |
Link to infoblock |
Multiple, product IDs |
| Brands |
BRANDS |
Link to infoblock |
Optional, if the document covers an entire brand |
One Document, Many Products
A TR CU declaration is usually issued for a series of products or for a trademark. The PRODUCTS property in the document infoblock is made multiple — one document references a list of products.
When outputting in the product card, do a reverse query:
Code example: Reverse query
```php
$docsRes = \CIBlockElement::GetList(
['PROPERTY_VALID_TO' => 'DESC'],
[
'IBLOCK_ID' => QUALITY_DOCS_IBLOCK_ID,
'PROPERTY_PRODUCTS' => $productId,
'ACTIVE' => 'Y',
],
false,
false,
['ID', 'NAME', 'PROPERTY_DOC_TYPE', 'PROPERTY_FILE',
'PROPERTY_DOC_NUMBER', 'PROPERTY_VALID_TO']
);
$docs = [];
while ($doc = $docsRes->GetNext()) {
$docs[] = $doc;
}
```
How to Automate Expiry Control?
Documents with expired dates should not be shown as current. Instead of manual checking, we use two automation options, reducing error risk by 90% and cutting monthly document check time by 85%.
Option 1 — Filter in query:
'>=PROPERTY_VALID_TO' => date('d.m.Y')
Option 2 — Automatic deactivation via agent.
Create a Bitrix agent (table b_agent) that daily checks documents with expired dates and sets ACTIVE = N. Register via \CAgent::AddAgent():
Code example: Agent registration
```php
\CAgent::AddAgent(
'\Local\QualityDocs\Agent::deactivateExpired();',
'local_quality_docs',
'N',
86400 // once per day
);
```
Bitrix Developer Documentation recommends using CAgent::AddAgent for scheduled tasks.
Bulk Document Binding
If you need to bind one document to hundreds of products, manual binding via the admin interface is inconvenient. Use import via CIBlockElement::Update() with updating the PRODUCTS property. Or create an admin page with product search by filter (category, brand) and bulk binding. Our approach is 2–3 times faster than ready-made modules due to query optimization, and saves up to $1,200 annually for a catalog of 500 products.
For bulk binding all products of a brand to a document:
Code example: Bulk binding by brand
```php
$productIds = [];
$res = \CIBlockElement::GetList(
[],
['IBLOCK_ID' => CATALOG_IBLOCK_ID, 'PROPERTY_BRAND' => $brandId],
false, false, ['ID']
);
while ($row = $res->Fetch()) {
$productIds[] = ['VALUE' => $row['ID']];
}
\CIBlockElement::SetPropertyValueCode(
$docElementId,
'PRODUCTS',
$productIds
);
</details>
## Expiry Notifications
A useful addition: 30 days before document expiration, send a notification to the responsible manager. Implemented via the same agent: find documents with `VALID_TO` in the range today+30 days and send an email via `\CEvent::Send()` with a notification template. This prevents delays and fines — saving up to 2 person-days per month.
## Visual Expiry Indication in Admin Interface
The admin document panel should immediately show which records are expiring. We implement color coding in the infoblock element list: green — document is current, yellow — expires within 30 days, red — expired. Use the `OnIBlockElementListGetResultRows` event handler to add a CSS class to the row based on `VALID_TO` value. The content manager sees the status of all documents on one screen without manual search or filtering. This speeds up monthly document check 5 times compared to viewing each element manually. The list supports CSV export: the responsible employee downloads a table with documents and dates, passes it to the legal team, and receives confirmation of updates without additional queries.
## Steps to Implement
1. Create QUALITY_DOCS infoblock with required properties.
2. Configure document types and properties.
3. Modify product card template to display linked documents.
4. Implement deactivation agent for expired documents.
5. Set up bulk binding page (optional).
6. Add email notifications for upcoming expirations.
## Что входит в работу
| Stage | Result | Time |
|---|---|---|
| Create quality documents infoblock | QUALITY_DOCS with required properties | 2–3 h |
| Modify product card | Display current documents with links | 3–4 h |
| Deactivation agent | Automatic daily deactivation | 2–3 h |
| Bulk binding page (optional) | Admin interface with filters | 4–6 h |
| Expiry notifications (optional) | Emails 30 days before expiry | 2–3 h |
We provide full documentation: schema description, agent code, query examples. The work includes access to the repository, a 1-hour training session for content managers, and 30 days of support after launch. Estimate your project for free — contact us, and we'll offer a turnkey solution in 5–10 business days. Our proven method guarantees compliance with regulations and is trusted by over 50 clients. Additionally, our solution integrates with CommerceML document exchange for automatic updates and can be linked with Bitrix24 document workflow for approval processes.
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.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
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?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- 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.
