Wishlist in 1C-Bitrix: Custom Favorites or Delayed Products?

Here's a typical scenario: an online store owner on Bitrix asks for a "save for later" feature, but it turns out the standard delayed items mechanism in the cart doesn't work—when trying to place an order, the favorites are cleared. Or users complain that after login the list disappears. We've encountered this dozens of times and developed two proven approaches. Our experience: over 10 years of 1C-Bitrix development, 60+ projects with wishlist, 12-month guarantee on each. On average, working with a custom table is 3 times faster for catalogs with 10,000 products.

Why Delayed Products in the Cart Are Not Always the Solution?

The built-in sale module allows marking a product with the DELAY = Y flag. Technically, this is just a record in the b_sale_basket table:

$basket = \Bitrix\Sale\Basket::loadItemsForFUser(
    \Bitrix\Sale\Fuser::getId()
);
$item = $basket->createItem('catalog', $productId);
$item->setFields([
    'QUANTITY' => 1,
    'DELAY'    => 'Y',
    'NAME'     => $productName,
    'PRICE'    => $price,
    'CURRENCY' => 'RUB',
]);
$basket->save();

The bitrix:sale.basket.basket component with the parameter SHOW_DELAY = Y displays these items. Downside: delayed items are part of the cart. When the cart is cleared (e.g., after checkout), all delayed items are lost. There is also no separation between "in cart" and "wishlist" at the interface level. A full wishlist requires a separate entity.

Case Study: From Delayed to Custom

We had a client with a 15,000-product catalog who initially used delayed items. Users complained that items disappeared after purchase. We migrated to a custom table. The load time for the favorites page dropped from 2.5 seconds to 0.8 seconds, and user complaints ceased. The project took 2 days.

How to Build a Full-Fledged Wishlist on a Custom Table?

For storage independent of session and synchronization across devices, we use a separate table. Example DDL:

CREATE TABLE user_favorite_products (
    ID INT UNSIGNED AUTO_INCREMENT PRIMARY KEY,
    USER_ID INT NOT NULL,
    PRODUCT_ID INT NOT NULL,
    DATE_ADD DATETIME DEFAULT CURRENT_TIMESTAMP,
    UNIQUE KEY uk_user_product (USER_ID, PRODUCT_ID)
);

An ORM class via \Bitrix\Main\ORM\Data\DataManager allows standard add, delete, getList methods. Add/delete via AJAX controller:

class Favorite extends \Bitrix\Main\Engine\Controller
{
    public function addAction(int $productId): array
    {
        $result = FavoriteTable::add([
            'USER_ID' => \Bitrix\Main\Engine\CurrentUser::get()->getId(),
            'PRODUCT_ID' => $productId,
        ]);
        return $result->isSuccess() ? ['status' => 'ok'] : ['error' => $result->getErrors()];
    }
}

How to Synchronize Favorites for Unauthenticated Users?

Unauthenticated users don't need a database record. We store an array of product IDs in localStorage:

1. On click "add to favorites" — add/remove ID from the array and update localStorage.
2. On page load, check authentication: if guest, read from localStorage and display favorite icons.
3. On login, send accumulated IDs to the server via AJAX, which inserts them into the table. This prevents data loss.
4. After sync, clear localStorage to avoid duplicates.

Comparison of Approaches

A custom table gives full control: you can add fields (color, size), group lists, display favorites separately from cart. This is especially important for large catalogs with 10,000+ items. According to our measurements, a query to a custom table runs 3 times faster than a select from b_sale_basket with the DELAY=Y filter.

How to Integrate Wishlist with an Existing Catalog?

During integration, we adapt the catalog component template: add a "Favorites" button with state (active/inactive) and a counter. We use the OnBuildGlobalMenu event to add a section to the personal account. For caching, we use tagged cache with the favorite tag. A typical mistake is forgetting the unique index on USER_ID+PRODUCT_ID, leading to duplicate entries on repeated clicks. Also handle the case where a guest is already logged in on another tab—sync could lose data. Use localStorage for guests, not the session, otherwise the list won't survive a page reload.

What's Included in the Work

• Technical specification with logic and interface description.
• Development of the "Favorites" button component with states and counter.
• Server controller for add/delete.
• Guest storage (localStorage) and synchronization on login.
• Integration into the existing catalog with template adaptation.
• Documentation and instructions for content manager.
• Access to the code repository.
• 12-month code guarantee.

Stages of Work

Cost and Timeline

Timelines depend on the chosen approach. Standard delayed items: from 2 to 4 hours. Custom wishlist with synchronization: from 1 to 2 working days. Complex integrations (e.g., synchronization with a mobile app) are discussed separately. Cost is calculated individually after analyzing your project. Get a consultation — we'll analyze your case for free. Order a turnkey wishlist implementation. This saves time on development from scratch and avoids typical mistakes.

For architecture study, we recommend Bitrix ORM documentation and Wikipedia on Web Storage API.

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.