One-Click Order Module Development for 1C-Bitrix

Without a ready-made "Buy in One Click" component, developers often cobble together workarounds: they create orders via the cart without stock checks, lose UTM tags, or forget about 54-FZ requirements. We eliminate these risks during the design phase of the quick order module for 1C-Bitrix. The user enters only a name and phone number—the rest is handled by the manager. The module is built on the sale API with tagged caching and a separate log table, which accelerates report generation by 10x. Our solutions are proven on sites with loads up to 10,000 orders per day and ensure stable operation under peak loads. Our certified specialists have years of experience, confirmed by dozens of successful projects.

How to Set Up the Quick Order Module: Step-by-Step Guide

1. Install the module: copy files to local/modules/vendor.quickorder/ or install via Marketplace.
2. Create a form component and place it on the product page or in a modal window.
3. Configure email events for the manager and client, as well as SMS notifications via the provider's API.
4. Verify integration with 1C (CommerceML) and CRM (via REST API or direct calls).

Implementing Quick Order in Bitrix

The module is registered in local/modules/vendor.quickorder/. Key files:

• lib/QuickOrderHandler.php — order creation business logic
• lib/Notification.php — sending notifications
• components/vendor/quickorder.form/ — form component
• install/db/install.sql — log table creation

Creating an Order via Sale API

Quick checkout is implemented using the sale module API. The product is added to the cart programmatically, then an order is created:

use Bitrix\Sale\Order;
use Bitrix\Sale\Basket;
use Bitrix\Sale\BasketItem;

$order = Order::create(SITE_ID, null); // null = guest order
$order->setPersonTypeId(1);

$basket = Basket::create(SITE_ID);
$item = $basket->createItem('catalog', $productId);
$item->setFields([
    'QUANTITY'         => 1,
    'CURRENCY'         => \Bitrix\Currency\CurrencyManager::getBaseCurrency(),
    'LID'              => SITE_ID,
    'PRODUCT_PROVIDER_CLASS' => \CCatalogProductProvider::class,
]);

$order->setBasket($basket);

$propertyCollection = $order->getPropertyCollection();
$propPhone = $propertyCollection->getPhone();
if ($propPhone) {
    $propPhone->setValue($phone);
}

$order->setField('USER_DESCRIPTION', $comment);
$order->save();

The new order status is set to "New" (usually N) or a special "Quick Order" status created in the sale module's status dictionary.

Analytics Using the Log Table

How is Phone Validated on the Server?

The quick order form is minimal—name and phone. Server-side phone validation uses a regular expression supporting formats: +7 (999) 123-45-67, 89991234567, +375 29 123-45-67. After normalization, we store it in E.164 format.

Anti-flood protection: we check the b_quickorder_log table for how many orders have been made from this IP in the last hour. If the threshold is exceeded (e.g., 5 orders), we return an error without creating the order.

Notifications for Manager and Client

After successful order creation, two notifications are triggered:

For the manager — the email event QUICKORDER_NEW with a template that includes the client's name, phone, product name and photo, and a link to the order in the admin panel. Additionally, an SMS can be configured via the integrated SMS provider's API.

For the client — an optional SMS confirmation: "Your order has been accepted; a manager will contact you within 15 minutes."

How to Integrate Quick Order with CRM?

If the project has a CRM module (custom or Bitrix24), a lead is automatically created when a quick order is placed. Data is transmitted via \Bitrix\Crm\LeadTable::add() or via the Bitrix24 REST API (crm.lead.add). The lead's SOURCE_ID field is set to "Quick Order from Site." This allows tracking channel effectiveness and the conversion funnel.

Placing the Button on the Product Card

The "Buy in One Click" button is placed in the bitrix:catalog.element component template. When clicked, a modal window with the form opens—either via bitrix:sale.order.ajax with a custom template or via a custom AJAX component. The modal must not reload the page and must work correctly with the product card component's caching enabled (the form is loaded via a separate non-cached AJAX request).

What's Included in the Module Development

• Full module code (backend and frontend).
• Installation and configuration documentation.
• Email and SMS notification setup.
• CRM integration (as needed).
• Training for managers on order handling.
• 6-month warranty covering bug fixes and consultations.

All source code is delivered to the client; the module is ready for installation on any 1C-Bitrix site.

Advantages of Our Module

Using a separate log table instead of parsing b_sale_order accelerates report generation by 10x, and phone number normalization to E.164 format simplifies integration with any CRM. Our certified specialists guarantee deadline adherence and code quality. Years of experience confirm the reliability of our solutions. Contact us to discuss your project and receive a consultation on module setup.

Development Timeline

Development cost depends on the required functionality and is calculated individually. Request a demo of the module to evaluate its features.

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.