Price and Availability Subscription

What this solution does

A product card marked 'out of stock' represents a lost sale. A customer arrives with funds but receives a refusal, and the store loses the ability to bring them back. The same occurs with customers who find the current price too high: they leave to compare prices elsewhere and do not return.

The module obtains permission to send notifications to these user groups and automatically writes to them as soon as the item becomes available or the price changes.

REPORT 'NOTIFICATIONS SENT' — THE CORE VALUE OF THE SOLUTION

Each sent notification receives a unique identifier. Clicks from the email are tracked, and orders for the specific item are linked to that notification. The report displays the complete chain of events: how many people subscribed, how many notifications were sent, how many customers returned, and the total sum of their purchases. Data is available per product for a selected period with an option to export to Excel.

Order accounting is strict: an order is credited only if it is a new order from the email recipient on the same site, contains the item from the email (or its trade offer), and is placed within the attribution window. Cancelled orders are excluded from revenue, amounts in different currencies are not summed, and undelivered emails are counted separately from delivered ones. Attributing the entire store revenue to a single email is not reporting but self-promotion. Therefore, the figures in this table are reliable: the solution pays for itself with the first returned order, and this is confirmed by actual numbers, not promises.

Financial data in the report is visible only to those to whom the store already shows it: an employee with limited order access sees revenue only for their own sites and statuses.

The report also includes a list of the most anticipated items—the priority stock to replenish first so that emails are sent automatically.

BUTTON INSTEAD OF A DEAD END

Where the text currently reads 'out of stock', a 'notify when available' button appears. For any product, a 'track price' feature is available: the system records the price at the moment of subscription and sends a notification only when the price drops below a specified threshold. Comparison occurs in the currency selected by the user at the time of subscription. If the product's currency changes, the recalculation is performed using the store's exchange rate; if no rate is available, the tracking resets, preventing false notifications about price drops. Authenticated users have their email address automatically filled in, while guests enter their email manually if the store allows guest subscriptions.

Buttons and notifications strictly respect catalog access rights. It is impossible to subscribe to a product that is not visible to the buyer due to permission restrictions, unpublished status, belonging to another site, or being a hidden product offer. No notifications are sent for such items.

THREE CHANNELS: EMAIL, TELEGRAM, MAX

Email works immediately: three email events with ready-made templates are edited just like any other store emails. Telegram and MAX are connected via a bot: the buyer clicks a button, enters a chat with the bot, and the subscription is linked to that chat. Unsubscribing is done by sending a command to the bot. Any channel can be disabled in settings. Changes to external APIs without prior notice must not stop the notification system.

To work with Telegram, the module settings require specifying a proxy server of type HTTP or SOCKS5 with a username and password. Most Russian servers lack direct access to Telegram, and without proper proxy configuration, the channel appears in the interface only as a static image.

Email Address Confirmation

The subscription becomes active only after clicking the link sent in the email. This requirement applies to authorized buyers as well: the standard user profile in Bitrix does not perform automatic email verification. An address is considered confirmed only after its owner has verified it once through this module. Without this step, any visitor could subscribe a third-party address, leading to spam complaints and degrading the deliverability of all outgoing messages from the store, including order notifications.

Limits on confirmation emails:

- No more than five emails per hour to a single address.

- No more than ten emails per hour from a single source.

- No more than once per hour for a single subscription.

- A maximum of 200 active subscriptions per address and per buyer.

The system does not send ten emails per day.

During synchronization with 1C, product stock levels may appear and disappear multiple times, and prices may fluctuate. The silence window setting defines how frequently a single user can be notified about a specific product. The price drop threshold is set in both percentage and monetary terms; the system triggers a notification if the stricter of the two conditions is met. A price drop of one ruble is considered too frequent and may lead to unsubscribes.

Unsubscribing is done with a single click on the link in the email. The link works without logging into the website, using a one-time token. This is a technical requirement to ensure email delivery: mail services track user complaints rather than excuses.

The opt-out is final. The 'follow again' button in a personal account or a new subscription to the same address will not restore the mailing. Emails will only be sent after the address owner reconfirms consent via the link. The same mechanism applies to the /stop command in messengers and the withdrawal of consent.

The buyer's personal account includes a dedicated page showing tracked items, the price at the time of subscription, the current price, and the time of the next notification. Buttons for 'unsubscribe' and 'follow again' are available. The 'follow again' button is hidden for subscriptions where the user has voluntarily opted out.

Data collection and processing comply with the requirements of Federal Law No. 152-FZ.

When a subscription is created, the system records the date, email address, the exact consent text the user viewed, and the request IP address. Consent is recorded for the recipient only at the moment of confirmation, not before. The consent text is configured in the module settings and displayed directly next to the email input field.

LOAD

Availability and price checks are performed by a background agent in batches on a loop. Catalog events ensure a fast response, but only a small batch of notifications is sent per item. This is critical because the 1C exchange updates stock levels for thousands of items simultaneously; if the module were to send mass emails during this process, the data exchange would halt.

WHAT THE MODULE DOES NOT DO

The system sends nothing without an explicit request: one event triggers exactly one email, without follow-up offers or recommendations for similar products. The module does not replace product cards or modify the system core. It does not reserve items or accept prepayments; a separate solution named "Preorder and Made-to-Order" handles these tasks. Together, these two solutions cover all scenarios regarding out-of-stock items. The system does not become a bot storefront: Telegram and MAX serve solely as notification delivery channels, not as a store within a messenger.

SCOPE LIMITATIONS

The module tracks only item availability and price changes. Subscriptions for size returns, specific warehouses, or product groups are not available in this version. Price comparison is made against the value recorded at the time of subscription, not against a monthly history.

REQUIREMENTS

The Price and Availability Subscription module operates within 1C-Bitrix: Site Management when the Trade Catalog and Information Blocks modules are installed. The system requires PHP version 8.2 or newer. Supported database systems include MySQL 5.7+, MariaDB 10.3+, or PostgreSQL. When using PostgreSQL, the main system module must be version 23.900.900 or newer. Price verification and notification dispatch are handled by background agents; running these agents via cron is recommended for stable operation. Integration with Telegram and MAX requires a dedicated store bot; if the Telegram service is unavailable, a proxy server must be used.

If “Price and Availability Subscription” is required, General iT can help with installation, configuration and a technical check after integration.