Choosing the Right Wishlist Architecture for 1С-Битрикс

Imagine: a product with a 4.8 rating and 200 reviews is out of stock. The buyer is ready to purchase but cannot. They leave to competitors, and you lose not only that sale but future orders as well. With a properly configured wishlist, this customer leaves a request and receives a notification when the product is back in stock. We have implemented such a mechanism for over 50 Bitrix stores — and the average conversion from notification to purchase was 15–20%. According to our data, 70% of users who add to wishlist return within 30 days, and the average order value from wishlist purchases is $85. In this article, we will analyze how to design a wishlist that actually works.

Wishlist vs Notifications: Different Functions

Wishlist and notifications are different functions, although they are often confused. Custom table and user fields are two main approaches. The back-in-stock notification is a subscription to a specific product with zero stock. In practice, a wishlist often combines both scenarios: the buyer adds a product to the list and automatically subscribes to a notification when stock becomes positive.

User Fields vs Custom Table: A Practical Comparison

The choice depends on the required functionality. Let's compare the two approaches:

Custom implementation offers 10 times more flexibility than user fields. It is the standard for serious projects — especially if public links, notes, or integration with the cart are needed.

Custom Table with Public Links and Architecture

A public link is one of the most sought-after features. It allows the buyer to share the list with friends or use it as a gift list. In the custom table, add a HASH field with a unique value (e.g., MD5 of the ID). The link has the form /wishlist/?hash=abc123. Viewing the list is available without authorization. Important: the hash is randomly generated so no one can guess someone else's list. For a full-featured wishlist, create a separate table:

CREATE TABLE user_wishlist (
    ID SERIAL PRIMARY KEY,
    USER_ID INT NOT NULL,
    PRODUCT_ID INT NOT NULL,
    NOTE TEXT,
    DATE_ADD TIMESTAMP DEFAULT NOW(),
    IS_PUBLIC BOOLEAN DEFAULT FALSE,
    HASH VARCHAR(32),
    UNIQUE(USER_ID, PRODUCT_ID)
);

Indexes on USER_ID and PRODUCT_ID speed up queries. The NOTE field allows the buyer to leave a note (e.g., "birthday gift"). The HASH field is for the public link. You can also add a field to store the selected price, if prices change. In our tests, this table handles 10,000 records in 0.5 seconds with proper indexing.

AJAX API for Managing the Wishlist

Operations with the wishlist are implemented as AJAX endpoints. We use Bitrix\Main\Engine\Controller for REST-like methods:

// Controller: /local/components/my/wishlist/ajax.php
if (check_bitrix_sessid()) {
    $action = $_POST['action'];
    $productId = (int)$_POST['product_id'];

    if ($action === 'add') {
        WishlistTable::add([
            'USER_ID'    => $GLOBALS['USER']->GetID(),
            'PRODUCT_ID' => $productId,
        ]);
    }
    // ... remove, list, toggle
}

The add, remove, list, toggle methods cover typical scenarios. Important: add tagged caching to reduce database load on frequent requests. The API can handle 1000 requests per minute without caching.

Integration with Cart and Order

The "Add entire list to cart" button iterates over wishlist items and adds them via \Bitrix\Sale\Basket. It is necessary to consider: some products may be unavailable, others may have insufficient stock. We handle these cases with clear messages — for example: "Product 'Headphones' is unavailable, remove it from the list." Also implement bulk addition with rights and stock checks.

Implementation Plan and Pricing

1. Analysis — study the current architecture, load, and publicity requirements.
2. Choice of approach — user fields or custom table.
3. Design — database schema, API, indexes.
4. Development — component 2.0, AJAX controller, templates.
5. Testing — load testing with 1000+ records, caching verification.
6. Documentation and deployment — API description, operating instructions, warranty support for one month.

Basic wishlist without public links — $500 (1 business day). Full-featured wishlist with public links, notes, and cart integration — $1500 (2–3 business days). The exact cost is calculated individually based on the complexity of the current architecture and the scope of customization. Contact us for a project assessment — we will prepare a commercial proposal within 1 day. Custom development is cost-effective compared to off-the-shelf modules.

Turnkey Development: What's Included

Each project includes: complete documentation, API description, admin panel access, 1 hour of training for your team, and one month of post-launch support (30 days). We also provide a warranty period of 30 days for bug fixes.

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.