Setting Up Age Verification (18+) on 1C-Bitrix

When launching an online store selling alcohol, tobacco, or medications, we faced strict requirements from 54-FZ and Article 14.17 of the Administrative Code — verifying the buyer's age. Missing verification can result in fines up to 500,000 ₽ and site blocking. Bitrix doesn't provide a ready-made mechanism, so we design and implement it turnkey. Over the years, we have completed more than 50 such integrations — from a simple modal window to full identification via Gosuslugi. Our approach works 3 times faster than typical implementation thanks to ready-made modules and a polished scheme.

Federal Law № 171-FZ and Article 14.17 of the Code of Administrative Offenses of the Russian Federation directly require sellers of alcohol and tobacco to verify the buyer's age. Quoting: "Retail sale to minors entails imposition of an administrative fine." Hence, the verification system is not a luxury but a mandatory condition.

How to Choose the Verification Level?

The first question: which verification level to choose? There are three, and each requires a different approach.

Level 1 is fastest. The buyer self-confirms age, result stored in cookie age_verified=1 with a 30-day lifetime. Legally weak protection, but sufficient for some goods (e.g., energy drinks).

Level 2 — user enters date of birth, system checks (today - birthdate) >= 18 years. Trivially bypassable but shifts legal responsibility to the buyer.

Level 3 is most reliable. We integrated with 171-FZ via ESIA REST API. Verification using passport data is our standard for alcohol and tobacco.

Why You Cannot Rely Solely on Cookies?

Cookies expire and can be cleared. Therefore we add checks on multiple fronts:

• OnPageStart — check cookie and display modal.
• OnBeforeProlog in the bitrix:catalog component — restrict access to age-limited sections.
• OnSaleBasketItemAdd — block adding product to cart without confirmation.

Handler code in init.php:

AddEventHandler('main', 'OnPageStart', function() {
    global $APPLICATION;
    if (!isset($_COOKIE['age_verified'])) {
        $APPLICATION->AddHeadScript('/local/js/age-verify.js');
        $APPLICATION->SetAdditionalCSS('/local/css/age-verify.css');
    }
});

// age-verify.js — set cookie on confirmation
document.cookie = 'age_verified=1; max-age=' + (86400 * 30) + '; path=/; SameSite=Lax';

Restriction at Category Level

Verification may not be required for the whole site. In the section infoblock, a property UF_AGE_RESTRICTED (checkbox) is created. The handler checks not only the cookie presence but also whether the current page belongs to a restricted category.

// OnBeforeProlog in bitrix:catalog
$sectionId = $arParams['SECTION_ID'];
$section = CIBlockSection::GetByID($sectionId)->Fetch();
if ($section['UF_AGE_RESTRICTED'] && !isset($_COOKIE['age_verified'])) {
    LocalRedirect('/age-check/?back=' . urlencode($REQUEST_URI));
}

Verification on Add to Cart

Even if the buyer passed verification on entry, the cookie may have expired. The OnSaleBasketItemAdd handler checks for an up-to-date confirmation:

AddEventHandler('sale', 'OnSaleBasketItemAdd', function(&$arFields) {
    $productId = $arFields['PRODUCT_ID'];
    if (isAgeRestrictedProduct($productId) && !isAgeVerified()) {
        return new CDBResult(false, 'Confirm your age to add this product');
    }
});

Storing Verification Status for Authorized Users

For authorized users, the verification result is stored in the profile — UF fields UF_AGE_VERIFIED (Yes/No) and UF_BIRTH_DATE (date). On next login, the cookie is set automatically without re-verification. This boosts conversion: according to our data, 40% of buyers do not return when forced to re-verify.

How to Set Up Verification for Authorized Users?

UF fields UF_AGE_VERIFIED and UF_BIRTH_DATE are added to the user profile. On successful verification, they are filled, and on subsequent login, the cookie is set automatically without repeating the process. We also configure automatic cookie renewal via agents if the user remains logged in.

Typical Mistakes and How to Avoid Them

Here's what we've encountered with clients: storing status only in a cookie (easily circumvented), lack of verification at the cart level (products go out without verification), improper handling of cookie expiry (users cannot complete checkout), ignoring authorized users (re-verification reduces conversion). We've learned to avoid these mistakes over 10+ years of working with Bitrix.

What Is Included in the Work

• Requirements analysis and verification level selection.
• Scheme design and prototyping.
• Development of modal windows, handlers, restrictions.
• Integration with ESIA or other services (if needed).
• Testing all scenarios: entry, cart, cookie expiry.
• Operational documentation and team training.
• Monitoring setup and post-launch support.

Process Timeline

We guarantee the system will pass any inspection by the Federal Service for Alcohol Regulation. Contact us — get a consultation and preliminary estimate in 1 day. Order verification setup and avoid the risk of fines.

Additionally, we connect Bitrix24 REST API for synchronization with CRM and external systems. The cost is calculated individually based on integration scope and complexity.

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.

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']]]]

sudo apt install redis-server
sudo systemctl enable redis

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?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. 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.