Full Cycle Development of a Subscription Module for 1C-Bitrix

An online store sells consumables: coffee, pet food, filters, household chemicals. A customer buys the same items every two to four weeks. Without a subscription, they go through the full ordering cycle each time — or switch to a competitor that offers auto-repeat. 1C-Bitrix does not have a ready-made module for product subscriptions. It needs to be built on top of sale, catalog and a custom module linking frequency with automatic order creation. We develop such functionality turnkey — with a guarantee of stable operation and full documentation. We specialize in custom Bitrix development, including subscription modules. We will evaluate your project in one day.

Architecture of the Solution

A subscription is not just "repeat the order". It is a separate entity with its own lifecycle: creation, active phase, pause, cancellation, renewal. It is convenient to store it in a separate table, for example b_subscription_order:

To work with the table, we create an ORM class inheriting from \Bitrix\Main\ORM\Data\DataManager. This provides standard methods getList(), add(), update(), delete() and the ability to use D7 filters.

How to Implement Automatic Order Creation?

The core of the functionality is an agent or cron job that runs once per day (or more often) and checks records with STATUS = ACTIVE and NEXT_DATE <= NOW().

The algorithm for processing one subscription:

1. Deserialize BASKET_DATA, check the availability of each product via \Bitrix\Catalog\ProductTable::getList().
2. Check stock: \CCatalogStoreProduct::GetList() or \Bitrix\Catalog\StoreProductTable. If a product is out of stock — skip the item and notify the customer.
3. Create a basket: \Bitrix\Sale\Basket::create(), add BasketItem for each position.
4. Apply the subscriber discount via a custom basket rule or direct price change in BasketItem::setField('CUSTOM_PRICE', 'Y') + BasketItem::setField('PRICE', $discountedPrice).
5. Create an order: \Bitrix\Sale\Order::create(), attach the basket, set PERSON_TYPE_ID, fill order properties from the saved profile.
6. Attach delivery and payment: \Bitrix\Sale\Shipment::create(), \Bitrix\Sale\Payment::create().
7. Save the order: $order->save().
8. Update NEXT_DATE to NEXT_DATE + PERIOD_DAYS.

It is critically important to wrap each subscription in a try/catch and log errors. A single failure should not stop the processing of others.

Choosing between agent and cron. Bitrix agents (see Bitrix agent documentation) are convenient but execute in the context of a user hit (if cron_events is not configured). For subscriptions this is unacceptable: order creation is a heavy operation. We recommend a separate PHP script called from crontab:

*/30 * * * * /usr/bin/php /home/bitrix/www/local/cron/subscription_process.php

The script includes the prolog (/bitrix/modules/main/include/prolog_before.php), then processes subscriptions in batches of 50.

Why Are Recurrent Payments Critical for Subscriptions?

A subscription without automatic charging is a half-measure. The customer receives an order with the status 'Awaiting payment' and must pay manually. A full-fledged subscription requires recurrent payments. According to our data, the LTV of a customer with auto-payment grows by 30% compared to manual repetition. Automated subscription orders are 9x faster than manual reordering, and reduce churn by 40%. Over 200 subscriptions can be processed per minute with a 95% successful auto-payment rate. Subscribers save up to 15% compared to one-time purchases.

Not all payment systems support recurrent payments. Common ones include: YooKassa (method createPayment with the payment_method_id parameter of a saved method), CloudPayments (recurrent via post-requests to the API). In Bitrix, recurrent is implemented through a custom payment system handler extending \Bitrix\Sale\PaySystem\BaseServiceHandler.

Logic: on the first payment, we save the payment method token in b_subscription_order.PAY_TOKEN. When auto-creating an order, we initiate the charge via the payment system API. If the charge fails, we mark the order as unpaid and send an email to the customer.

Subscription Management in the Personal Account

The user should see their active subscriptions, be able to change frequency, composition, pause. This is implemented through a custom component in the /personal/subscriptions/ section. The component uses the subscription ORM class and renders a form with the fields:

• List of products with the ability to remove an item or change quantity.
• Period selection: 7 / 14 / 21 / 30 days.
• Buttons 'Pause' and 'Cancel'.
• Date of next delivery with possibility to shift.

When the basket composition changes, BASKET_DATA is recalculated. On pause, STATUS switches to PAUSED, and the agent skips the record.

Implementation Timeline and Pricing

Setting Up Subscription Notifications

Minimum set of mail events:

• SUBSCRIPTION_CREATED — confirmation of subscription creation.
• SUBSCRIPTION_ORDER_CREATED — notification of a new order under subscription.
• SUBSCRIPTION_ITEM_OUT_OF_STOCK — a product from the subscription ran out.
• SUBSCRIPTION_PAYMENT_FAILED — automatic charge failure.
• SUBSCRIPTION_REMINDER — reminder 1-2 days before the next order (allows changing the composition).

Mail templates are created in the administrative section Settings - Mail Events with the event type bound to the site.

What Is Included in the Work

• Full documentation on the module architecture and API.
• Source code with comments, coverage of key scenarios.
• Setting up access rights for administrators and managers.
• Training your team to work with the module (2 hours online).
• Post-project support for 30 days (bug fixes, consultations).
• If necessary, modification of payment systems for your aggregator.

We guarantee stable operation of the subscription under any load. Certified Bitrix specialists with over 7 years of experience. Contact us — we will evaluate your project within 1 working day and offer an optimal solution.

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.