Setting Up Quality Document Binding in 1C-Bitrix

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 flexib

Our competencies:

Frequently Asked Questions

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.