How to add a 'Wishlist' button to the product card in Bitrix?

We develop a component vendor:wishlist.button that sends an AJAX request. The component accepts the product ID and action (add/remove). On the catalog page, button states are initialized with one request returning an array of product IDs in the wishlist. JavaScript marks the buttons without additional requests.

Is it possible to create multiple wishlists?

Yes, the module supports multiple lists, e.g., 'Want to buy', 'Gifts', 'Favorites'. Users can manage lists via their personal account. Each list has its own name and can be made public.

What are public wishlists and how to share them?

A public list is accessible via a unique link generated when the option is enabled. Any visitor can view the list and add items to their cart but cannot edit the list. This is convenient for gift registries.

Why not use the standard sale module for wishlists?

The sale module uses delayed items, which are technically part of the cart. This mixes logic, prevents multiple lists, and lacks guest support. A dedicated wishlist module resolves these issues and adds features like public lists and price drop notifications.

How to add a 'Wishlist' button to the product card in Bitrix?

We develop a component vendor:wishlist.button that sends an AJAX request. The component accepts the product ID and action (add/remove). On the catalog page, button states are initialized with one request returning an array of product IDs in the wishlist. JavaScript marks the buttons without additional requests.

Is it possible to create multiple wishlists?

Yes, the module supports multiple lists, e.g., 'Want to buy', 'Gifts', 'Favorites'. Users can manage lists via their personal account. Each list has its own name and can be made public.

What are public wishlists and how to share them?

A public list is accessible via a unique link generated when the option is enabled. Any visitor can view the list and add items to their cart but cannot edit the list. This is convenient for gift registries.

Why not use the standard sale module for wishlists?

The sale module uses delayed items, which are technically part of the cart. This mixes logic, prevents multiple lists, and lacks guest support. A dedicated wishlist module resolves these issues and adds features like public lists and price drop notifications.

Custom Wishlist Module for 1C-Bitrix Development

Q: How does guest wishlist synchronization work with an authorized user?

Upon login, the OnAfterUserLogin event triggers. The module finds the anonymous list by session, transfers items to the user's main list with duplicate checking, then deletes the anonymous list. If the user has no lists, the anonymous list is reassigned to the user's ID.

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 suppo

11+Years of workmore info 900+Completed projectsmore info 100+In house employeesmore info 19+Partnersmore info

Services we offer

Showing 1 of 1All 1626 services

Custom Wishlist Module for 1C-Bitrix Development

Medium

~1-2 weeks

Our competencies:

Free consultation

Book a free consultation if you have any questions. A dedicated specialist will advise you.

Cost calculation

If you know what exactly you need to develop, or you already have a ready-made technical task.

Frequently Asked Questions

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'):

Field	Type	Purpose
ID	int auto_increment	Primary key
USER_ID	int	User ID (NULL for guests)
SESSION_ID	varchar(64)	Guest session hash
TITLE	varchar(255)	List name
IS_PUBLIC	tinyint(1)	Shareable via link
PUBLIC_HASH	varchar(32)	Unique hash for public URL
CREATED_AT	datetime	—

Table b_wishlist_item:

Field	Type	Purpose
ID	int auto_increment	—
LIST_ID	int	FK to `b_wishlist`
PRODUCT_ID	int	ID of product offer
ELEMENT_ID	int	ID of infoblock element (parent product)
ADDED_AT	datetime	—
NOTE	text	User's personal note for the 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:

The agent runs once daily, iterating over unique PRODUCT_ID from b_wishlist_item.
For each, it gets the current price via \CCatalogProduct::GetByID() or Price::getList().
Compares with the price stored in the LAST_PRICE field (added to the b_wishlist_item table).
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.

Development Timelines

Scope	Features	Timeline
Basic	Single list, DB storage, AJAX button, header counter	4–5 days
Standard	+ Guest/user merge, wishlist page in personal account, multiple lists	7–10 days
Extended	+ Public lists, price drop notifications, list export	12–15 days

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

1C Bitrix presentation 1C Bitrix24 presentation 1C Enterprise presentation