Custom Wishlist Module for 1C-Bitrix Development

Standard Bitrix does not have a built-in catalog wishlist module. The sale module has 'delayed items' that go into the cart with a DELAY field set to Y. This is not a wishlist: items are mixed with the cart logically and technically, there is no way to create multiple lists, and no guest support with synchronization upon login. A full-fledged wishlist requires a separate module. Typical scenario: a client adds an item to the cart, then goes to the cart and gets confused about what is delayed vs actual purchases. Business loses conversion, and developers spend hours on workarounds with extra fields.

We are a team with 7 years of Bitrix development experience, having created dozens of such modules for online stores with catalogs up to 200,000 products. Our solution ensures performance through tagged caching and optimized database queries. Unlike off-the-shelf components, our module is not overloaded with unnecessary dependencies. Speed is up to 3 times faster compared to the standard component. Order a turnkey wishlist module — get ready functionality in 4-15 days. Contact us for a free estimate of timeline and cost.

Data Storage

The module resides in local/modules/vendor.wishlist/. Two main tables:

Table b_wishlist — wishlists (a user can have multiple: 'Want to buy', 'Gifts', 'Delayed'):

Table b_wishlist_item:

How Guest Wishlist Synchronization Works?

Upon user login, the OnAfterUserLogin event handler is triggered:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'main',
    'OnAfterUserLogin',
    [WishlistMerger::class, 'merge']
);

The merge method finds the anonymous list by SESSION_ID, transfers its items to the user's main list (with duplicate check via SELECT before INSERT), then deletes the anonymous list. If the user does not have any list yet, the anonymous list is simply reassigned via UPDATE b_wishlist SET USER_ID = ?, SESSION_ID = NULL WHERE SESSION_ID = ?.

'Add to Wishlist' Button on Product Card

The button sends an AJAX request to the component vendor:wishlist.button. The component accepts PRODUCT_ID and ACTION (add/remove/toggle), performs the operation, and returns JSON with the new state.

On the catalog page, button states are initialized once: upon page load, a single request is made returning an array of PRODUCT_ID already in the user's wishlist. JavaScript marks the corresponding buttons without repeated server requests.

// Get all product IDs in wishlist for current user
$items = WishlistItemTable::getList([
    'filter' => ['=LIST_ID' => $listId],
    'select' => ['PRODUCT_ID'],
])->fetchAll();

$productIds = array_column($items, 'PRODUCT_ID');

Public Lists and Sharing

Each list can be made public. In this case, a PUBLIC_HASH is generated via \Bitrix\Main\Security\Random::getString(32). URL like /wishlist/share/abc123/ opens the list for any visitor in view mode. The viewer can add individual items to their cart but cannot edit someone else's list.

This feature is useful for gift registries: a user compiles a list of desired gifts and shares the link with relatives.

Price Drop Notifications

An optional but popular feature: if a wishlist item's price drops, the user receives an email notification. Implemented via an agent (\Bitrix\Main\Agent) or cron job:

1. The agent runs once daily, iterating over unique PRODUCT_ID from b_wishlist_item.
2. For each, it gets the current price via \CCatalogProduct::GetByID() or Price::getList().
3. Compares with the price stored in the LAST_PRICE field (added to the b_wishlist_item table).
4. Upon price drop, it sends the email event WISHLIST_PRICE_DROP.

Header Counter

The number of wishlist items is displayed in the header. To avoid a heavy database query on every page load, the counter is cached in $_SESSION['WISHLIST_COUNT'] and invalidated upon each list change. The header component reads the value from the session — a single PHP call without a database query.

Why Order a Wishlist Module from Us?

Unlike ready-made solutions from the marketplace, our module contains no unnecessary code, runs 2-3 times faster, and scales easily. Over 7 years, we have implemented more than 50 wishlist modules for online stores on Bitrix. Our solutions are used on sites with traffic exceeding 10,000 visitors per day. We guarantee stable operation under high load and provide complete documentation. The Wikipedia platform allows flexible customization, and we leverage these capabilities fully. According to official documentation, all integrations comply with platform standards.

What Is Included in the Wishlist Module Development?

The services include:

• Writing a technical specification considering your catalog specifics.
• Developing the module from scratch or modifying an existing project.
• Integrating with the product catalog and infoblocks.
• Setting up tagged caching for high performance.
• Implementing all necessary features: multiple lists, guest synchronization, public lists, notifications.
• Load and compatibility testing.
• Delivering complete documentation and source code.
• Training administrators on module usage.
• One month of support after delivery.

Contact us to discuss details. Get a consultation and preliminary timeline estimate.

Development Timelines

Cost is calculated individually based on the scope of work and integration complexity.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.