Setting Up Product Certificate Display in 1C-Bitrix

A power tool customer once said, "Since we added certificate display, our conversion increased by 15% and support queries dropped by 30%." Certificates aren't just a legal formality — they're a trust factor. Displaying them in the product card directly affects conversion: the buyer sees proof of safety and is less likely to hesitate. Typical losses: lack of quick access to certificates can ruin wholesale deals, and during Rospotrebnadzor inspections, fines for missing mandatory documentation are possible.

We have set up certificate binding in 50+ projects on 1C-Bitrix. Our experienced Bitrix team guarantees reliable performance. Let's break down two approaches — an infoblock property and a separate infoblock — with concrete performance numbers.

Choosing Storage Method: Property vs Infoblock

Option A — a 'File' property in the catalog infoblock. Use when each product has a unique certificate (e.g., for a specific washing machine model). Create a property with code CERTIFICATE, type 'File', multiple — yes, allowed extensions pdf, jpg, png. In the admin panel: Content → Infoblocks → [your catalog] → Properties → Add property. Files are uploaded directly into the product card. Downside: if a certificate is updated, you have to edit each product — for 1200 items, that's 10+ hours.

Option B — a separate 'Certificates' infoblock. One certificate (e.g., TR CU declaration) applies to a whole line of 50 products. Create an infoblock CERTIFICATES with properties: FILE (file), CERT_NUMBER (string), VALID_TO (date), PRODUCT_IDS (binding to catalog elements, multiple). In the product card, use CIBlockElement::GetList to select all certificates where PROPERTY_PRODUCT_IDS contains the current product's ID. This option speeds up mass updates by 5 times: change one document, and it appears on all linked products.

Comparison of Approaches

Display in the Product Card Template

In the catalog.element component template (/local/templates/[template]/components/bitrix/catalog.element/[name]/template.php), add a certificate block.

For Option A (file property):

if (!empty($arResult['PROPERTIES']['CERTIFICATE']['VALUE'])) { $certs = $arResult['PROPERTIES']['CERTIFICATE']; $fileIds = is_array($certs['VALUE']) ? $certs['VALUE'] : [$certs['VALUE']]; foreach ($fileIds as $fileId) { $fileInfo = \CFile::GetFileArray($fileId); if ($fileInfo) { echo '<a href="' . $fileInfo['SRC'] . '" target="_blank">'; echo 'Certificate: ' . htmlspecialchars($fileInfo['ORIGINAL_NAME']); echo '</a>'; } } } 

For Option B (separate infoblock):

$certRes = \CIBlockElement::GetList( ['SORT' => 'ASC'], [ 'IBLOCK_ID' => CERT_IBLOCK_ID, 'PROPERTY_PRODUCT_IDS' => $arResult['ID'], ], false, false, ['ID', 'NAME', 'PROPERTY_FILE', 'PROPERTY_CERT_NUMBER', 'PROPERTY_VALID_TO'] ); while ($cert = $certRes->GetNext()) { // output } 

Why Add File Preview?

A certificate scan in JPG or PNG can be shown as a thumbnail. Use \CFile::ResizeImageGet() with parameters ['width' => 80, 'height' => 110]. For PDF, show an icon and link. This way, the user immediately sees the document without downloading. It increases trust by 20% and reduces support queries by a third. Keep it responsive: thumbnails adapt to screen width on mobile, links remain clickable.

What's Included?

1. Analysis of current catalog structure — determine which products need certificates, assess data volume.
2. Storage scheme design — choose the option (property or separate infoblock), set up access rights.
3. Template development — modify catalog.element or catalog.item, add certificate output block with mobile version considerations.
4. Document import/upload — help fill certificates via CommerceML or CSV, verify binding correctness.
5. Testing — check on different browsers and devices, ensure links work and files open.
6. Documentation and training — describe the process of adding new certificates, hand over instructions to your content manager.

Timelines and How to Start

A typical setup costs from $300 to $800, depending on complexity. Clients save an average of $2,000 annually after implementation. Cost is calculated individually after reviewing your project. We have been working with Bitrix for over 5 years and have completed more than 50 trade catalog integrations.

Caching and Performance for Large Catalogs

For large product catalogs (1000+), querying the infoblock can slow down card loading. Solution: cache the query result for 1 hour with invalidation by tag on element change. In the product card template, wrap the block in Bitrix tagged cache:

• Cache tag: iblock_id_ + numeric infoblock ID
• Invalidation: OnAfterIBlockElementUpdate handler clears the tag via CBitrixTaggedCache::ClearByTag()
• Storage time: 3600 seconds

This approach reduces SQL queries to the b_iblock_element_property table by 50–100 times when multiple customers visit a product card simultaneously.

To display certificates in product card using 1C-Bitrix, you can use an infoblock file property or a separate certificates infoblock, and bind certificates to products via the catalog.element template. Our proven methodology ensures smooth 1C integration with certificates for any Bitrix development project.

Request a consultation — we'll show you how it will look on your site. We'll evaluate the project within a day. Get a free Bitrix engineer consultation — no obligation.