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
| Criterion |
'File' Property |
Separate Infoblock |
| Implementation simplicity |
High |
Medium |
| Reusability |
No |
Yes |
| Mass update convenience |
Low (edit each product) |
High (change certificate in one place) — 5x faster |
| Loading via CommerceML |
Yes |
Yes (with additional exchange setup) |
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?
- Analysis of current catalog structure — determine which products need certificates, assess data volume.
- Storage scheme design — choose the option (property or separate infoblock), set up access rights.
- Template development — modify
catalog.element or catalog.item, add certificate output block with mobile version considerations.
- Document import/upload — help fill certificates via CommerceML or CSV, verify binding correctness.
- Testing — check on different browsers and devices, ensure links work and files open.
- Documentation and training — describe the process of adding new certificates, hand over instructions to your content manager.
Timelines and How to Start
| Stage |
Time |
| Analysis and design |
from 2 hours |
| Template development |
2–4 hours |
| Filling and testing |
from 1 day (depends on product count) |
| Full turnkey setup |
1–3 days |
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.
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.