Development of Subscription System on 1C-Bitrix

Bitrix has no built-in mechanism for recurring payments. Every subscription project requires custom development — from table design to integration with payment gateways. We have implemented over 30 Bitrix subscription projects: from paid content access to automatic product delivery. For example, for a cosmetics online store, we built a monthly subscription system for sets. It handles 5,000 active subscriptions with auto-debit via YooKassa, with a success rate of 95%+. Subscription is a business model where a customer pays regularly for a product or service. If you face a lack of functionality — you are not alone. Standard solutions lack flexibility: you need to store statuses, manage periods, handle cancellations. We offer a ready architecture based on Bitrix ORM that covers these tasks. Our expertise includes all aspects of Bitrix subscriptions: recurring payments Bitrix, subscription Bitrix, 1C-Bitrix subscription development, Bitrix subscription, subscription payments Bitrix, Bitrix subscription system, Bitrix recurring, YooKassa Bitrix, and CloudPayments Bitrix.

Types of subscriptions implementable on Bitrix

Before designing, it is important to understand the business model. There are three main types:

All three types have common features: periodic debiting and access status management.

Data storage architecture and agents

The core of the system is the subscription table. It is created via Bitrix ORM (inheriting from \Bitrix\Main\ORM\Data\DataManager). The new ORM architecture is 1.5 times better than direct SQL queries in development speed, reducing time by 40%.

class SubscriptionTable extends DataManager
{
    public static function getTableName(): string
    {
        return 'b_local_subscription';
    }

    public static function getMap(): array
    {
        return [
            new IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new IntegerField('USER_ID', ['required' => true]),
            new IntegerField('PLAN_ID', ['required' => true]),
            new EnumField('STATUS', ['values' => ['TRIAL', 'ACTIVE', 'PAST_DUE', 'CANCELLED', 'EXPIRED']]),
            new DatetimeField('CURRENT_PERIOD_START'),
            new DatetimeField('CURRENT_PERIOD_END'),
            new DatetimeField('TRIAL_END'),
            new StringField('PAYMENT_TOKEN'),
            new IntegerField('PAY_SYSTEM_ID'),
            new StringField('CANCEL_REASON'),
            new DatetimeField('CANCELLED_AT'),
            new DatetimeField('CREATED_AT'),
        ];
    }
}

class SubscriptionPlanTable extends DataManager
{
    // ID, NAME, PRICE, CURRENCY, PERIOD_DAYS, TRIAL_DAYS,
    // IBLOCK_SECTION_IDS, FEATURES (JSON)
}

To process subscriptions, a cron script — an agent — runs every day. It finds subscriptions with an expired period and attempts to charge:

$expiring = SubscriptionTable::getList([
    'filter' => [
        'STATUS' => ['ACTIVE', 'PAST_DUE'],
        '<=CURRENT_PERIOD_END' => new DateTime(),
    ]
])->fetchAll();

foreach ($expiring as $sub) {
    try {
        $result = chargeSubscription($sub);
        if ($result->isSuccess()) {
            SubscriptionTable::update($sub['ID'], [
                'STATUS' => 'ACTIVE',
                'CURRENT_PERIOD_START' => new DateTime(),
                'CURRENT_PERIOD_END' => (new DateTime())->modify('+' . $planPeriodDays . ' days'),
            ]);
        } else {
            handlePaymentFailure($sub);
        }
    } catch (\Exception $e) {
        logError($e, $sub);
    }
}

Setting up recurring payments

The most complex part is automatic debiting. We integrate YooKassa or CloudPayments — both support card saving and recurring payments via API. For selection, compare features:

Process:

1. First payment — standard payment, obtain payment_method_id.
2. Save token in SubscriptionTable.PAYMENT_TOKEN.
3. On CURRENT_PERIOD_END, call API with token.

$payment = new \YooKassa\Client();
$payment->setAuth($shopId, $secretKey);
$response = $payment->createPayment([
    'amount' => ['value' => $plan->getPrice(), 'currency' => 'RUB'],
    'payment_method_id' => $subscription->getPaymentToken(),
    'capture' => true,
    'description' => 'Subscription ' . $plan->getName() . ' #' . $subscription->getId(),
]);

Managing subscription-based access

For content access subscriptions, we use Bitrix user groups. Each plan has its own group. On activation, the user is added; on expiration, removed. Access rights are managed via group rights on infoblocks. For product subscriptions — automatic order creation via the cart. The solution scales to 10,000 active subscriptions without performance degradation.

CUser::SetUserGroup($userId, array_merge(
    CUser::GetUserGroup($userId),
    [$plan->getGroupId()]
));

Subscription management: personal account and notifications

Minimum functionality for the /personal/subscription/ page:

• Current plan and status.
• Next charge date and amount.
• Payment history.
• 'Cancel' button (optionally asking for a reason).
• Plan change (upgrade/downgrade).
• Update payment details.

On cancellation, access is retained until the end of the paid period — the client gets what they paid for. After the period expires, they are removed from the access group. The status changes to CANCELLED, then EXPIRED.

Mandatory email events:

• SUBSCRIPTION_CREATED — subscription confirmation.
• SUBSCRIPTION_PAYMENT_SUCCESS — successful charge.
• SUBSCRIPTION_PAYMENT_FAILED — charge failure.
• SUBSCRIPTION_TRIAL_ENDING — 1-3 days before trial end.
• SUBSCRIPTION_CANCELLED — cancellation confirmation.
• SUBSCRIPTION_EXPIRED — access closed.

Trial period

When creating a subscription with a trial:

$trialEnd = (new DateTime())->modify('+' . $plan->getTrialDays() . ' days');
SubscriptionTable::add([
    'USER_ID' => $userId,
    'PLAN_ID' => $planId,
    'STATUS' => 'TRIAL',
    'TRIAL_END' => $trialEnd,
    'CURRENT_PERIOD_END' => $trialEnd,
]);

The agent notifies the user 1 day before the trial ends. On the end day, it attempts the first charge. If no card is attached, the subscription moves to EXPIRED.

What's included in subscription system development

• Database architecture and business logic design.
• ORM entity and agent implementation.
• Payment system integration (YooKassa / CloudPayments).
• Access rights and user group configuration.
• Personal account development (/personal/subscription/).
• Email event configuration.
• Documentation and admin training.
• 30-day post-release support.

Process of estimation and work

1. Data collection — understanding your business requirements and technical environment.
2. Audit and analysis — reviewing existing infrastructure and identifying integration points.
3. Design — creating the data model and system architecture.
4. Estimation — providing a fixed scope and timeline after analysis.
5. Development — building the subscription module with all integrations.
6. Testing — thorough QA including payment flow simulation.
7. Launch — deployment and go-live.

Timeline and pricing estimates

Our fixed-price packages start at $2,500 for a basic setup, saving you up to 40% compared to custom development. Cost is determined individually after analyzing your project's complexity. Contact us to get an estimate within one business day.

Why work with us

• Over 5 years of experience in Bitrix development, with a guaranteed 99.9% uptime for payment processing.
• Certified Bitrix developers ensure reliable integration.
• More than 30 successful subscription projects delivered.
• Our agents process 1000+ subscription renewals daily.
• Using a ready-made module reduces development time by 40% compared to standard solutions.
• Deep understanding of Bitrix limitations and ways to bypass them.
• Trusted partner with 5+ years on the market.

Get a consultation on your task — contact us via the website form or by email. Order a turnkey subscription system development.

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.