Stepwise Order Checkout Customization for 1C-Bitrix

When a Bitrix project already has a standard order component, but you need to add a step for selecting delivery time or a conditional jump for self-pickup — the standard logic breaks?

Clients lose conversions, and developers go into weeks of fixes. We are a team with 10+ years of experience developing on Bitrix and over 50 successful projects — we configure stepwise order checkout from scratch or modify the existing one. We configure the number of steps, order, AJAX switching, and additional fields. Evaluate your project in 1 day — just write to us. According to statistics, a properly configured stepwise checkout increases conversion by 1.3 times compared to a single-page form, by reducing cognitive load on the user. We solve tasks of any complexity: from adding one field to complex logic with conditional transitions, integration with 1C, and fiscalization.

How stepwise mode works

The component bitrix:sale.order.ajax with parameter DELIVERY_MODE = SPLIT_DELIVERY splits the checkout into steps. In the .default template folder, there are order_ajax.php and files step_*.php. Switching between steps is done by the JavaScript function orderAjax.gotoStep(). It sends the current step's data to the server and receives the next step's markup. It is important to preserve the structure of JS variables: arOrderAjaxFields, arDeliveryList, arPaySystemList. If these objects are not filled correctly — AJAX switching will break.

How to add a new step to the stepwise checkout?

The default template supports 3 steps. To add a new one (e.g., "Delivery time selection" or "Gift wrapping"), follow this algorithm:

1. Create a copy of the template in /local/components/bitrix/sale.order.ajax/templates/.
2. Add a file step_delivery_time.php with the step markup.
3. Register the step in the JavaScript array orderAjax.steps.
4. In the handler OnSaleComponentOrderMakeOrder, save the additional step data in order properties.

BX.message({STEP_DELIVERY_TIME: 'Select delivery time'});
orderAjax.steps.push('STEP_DELIVERY_TIME');

On the server, in the method initStep, we check if the step is present in the data.

Reasons for breaking the standard component with custom steps

The main reason is incompatibility with the expected data structure. Each step must return JSON with fields HTML, TITLE, DATA. If the format is broken, orderAjax does not update the step. The second reason is lack of handling new fields in the checkValid function. We always add validation for each custom field. According to official Bitrix documentation, copying the template to /local is the first step to preserve changes during core updates.

Configuring conditional step transitions

If self-pickup requires skipping the address step, this is implemented via a JS event:

BX.addCustomEvent('onSaleOrderAjaxStepChange', function(currentStep, nextStep) {
    if (currentStep === 'DELIVERY' && selectedDeliveryIsPickup()) {
        orderAjax.gotoStep('PAYMENT');
        return false;
    }
});

On the server, we remove the mandatory requirement for address fields for self-pickup — via a condition in OnSalePropertyValueCheck.

How to speed up AJAX switching between steps?

AJAX switching is already asynchronous, but speed can be increased by tagged caching for delivery and payment lists. Use Bitrix\Main\Data\Cache with tags sale_delivery and sale_pay_system. Also disable unnecessary GetList calls in the epilogue. With proper configuration, a step switches in 200–400 ms — 3 times faster than a full page reload.

Comparison: stepwise vs single-page checkout

What is included in the work

• Documentation: technical specification with step descriptions, state diagram, operation manual.
• Access: configuring component access rights, roles for operators.
• Training: a session for administrators on managing custom steps.
• Support: 1-year warranty service, consultations on modifications.

Stages of work

Timeline and guarantees

Configuration based on the standard component — 1–3 working days. Adding non-standard steps — 2–5 days. The cost is determined after analysis of your project and fixed in the contract. Our clients save up to 40% of time on modifications compared to DIY customization. All work comes with a 1-year warranty. The team is a certified 1C-Bitrix partner with over 10 years of experience and more than 50 implemented online stores. We use only licensed software.

Typical technical mistakes when customizing

• Template not copied to /local — changes will be lost during core update.
• New step not added to orderAjax.steps — "Next" button does not appear.
• Event onSaleOrderAjaxStepChange not handled for conditional transition — user gets stuck on a step.
• Fiscalization (Federal Law 54-FZ) not considered when changing steps — receipts do not pass. We configure data transfer to ATOL Online or similar.

Before starting work, we check compliance with requirements from Wikipedia: 1C-Bitrix and AJAX.

Contact us — we will evaluate your project in 1 day. Get a consultation and a roadmap. Write to us — we will configure stepwise order checkout for your tasks.

How does 1C-Bitrix cart customization solve conversion loss?

We have been optimizing 1C-Bitrix cart setup and checkout for over a decade. In that time, a common pain emerged: the standard sale.order.ajax loses 10–15% of buyers at each step. Three steps, and a third of those who already added a product leave. Not because they changed their minds — the interface stumbles.

sale.order.ajax throws a 500 error if even one delivery handler is misconfigured. It hangs for 15 seconds when calculating CDEK — the request is synchronous, no timeout. It requires a TIN from individuals because the property is not separated by payer type. Each such case is direct losses that the system does not compensate.

Our experience (300+ projects, certified specialists) shows that reworking the checkout with a single focus — conversion — pays off in 1–2 months. Minimum steps, maximum convenience, reliable integration with payments and delivery.

Why does one-step checkout increase conversion?

All fields on one page. Logical grouping, no unnecessary transitions:

• Contact details — name, phone, email. Three fields. Not five, not ten, not "enter date of birth for loyalty program".
• Delivery — select city → see methods with prices and terms. AJAX calculation via CDEK, Boxberry, Russian Post APIs. Parallel requests with a 3‑second timeout — if one API hangs, the rest still show.
• Payment — methods are filtered by selected delivery. Cash on delivery for pickup? We don't show it.
• Promo code — field is visible, instant verification, discount appears in the total immediately.
• Total — dynamic recalculation on any change. Change quantity → subtotal → delivery cost → total. No page reload.

Under the hood:

• Full AJAX — no reloads. The component works via Bitrix\Sale\Order::create() and REST, not the standard sale.order.ajax.
• Real-time validation: not "fill the field correctly" but "phone: +1 (__) -". inputmask mask + server-side check.
• Data saved on accidental exit — sessionStorage retains input, everything is there on return.
• Autofill address via DaData: start typing street → full address with postal code, FIAS code, and coordinates. Fewer errors on the courier side.
• Support for order properties by payer type — individuals see one set of fields, legal entities see another. Toggle in the form.

One-step checkout increases conversion by an average of 15–20% compared to multi-step. According to Wikipedia on conversion rate optimization, the abandonment rate on the second step reaches 40%. Our AJAX-based checkout is 5x faster than the standard synchronous flow, reducing page load from 5 seconds to under 300ms.

How to recover abandoned carts?

Saving. Authorized users — cart in b_sale_basket, accessible from any device. Guests — cookie with TTL 30 days. FUSER_ID linked to cookie, cart does not disappear after an hour. Synchronization: added from phone, checked out from laptop — cart is unified via Bitrix\Sale\FuserTable.

Return. Email series: 3 emails. After 1 hour — reminder. After 24 hours — "your item is running out". After 72 hours — personal promo code for 5–10%. Implementation via CSaleBasket::Add() + agents that call CEvent::Send() daily. Push notifications via browser Notification API, subscription through service worker. Retargeting — cart data goes to Yandex.Direct via eCommerce events.

Abandonment analytics. At which step do they leave? If at delivery selection — price shock. If at payment — card declined, 3D-Secure fails. Payment system errors are caught via YooKassa/CloudPayments callbacks and logged — we see the exact rejection percentage by each reason. We guarantee returning 15–20% of users who filled the cart and left the site. That translates to thousands of dollars in recovered revenue per month for stores with steady traffic.

Guest checkout: eliminate mandatory registration

"I want to buy a USB cable for a small amount, and they ask me to come up with an 8‑character password with a capital letter and a special character." Mandatory registration kills 25–30% of conversion on small orders.

• Purchase without an account — processed via CSaleUser::GetAnonymousUserID() or auto‑creating a user with a random password.
• After checkout — an email with login details. If they want, they activate the account; if not, they still get the order.
• Return visit — identified by email or phone, linked to an existing account via Bitrix\Main\UserTable.
• Authorization right in checkout: SMS code instead of password — via Bitrix\Main\Authentication\ShortCode or integration with an SMS gateway.

This approach boosts checkout completion from 70% to 85% on average.

Cross-sell: non-intrusive upsells

In the cart

Recommendations based on real data from b_sale_basket — "customers who bought this also bought" using associative rules (confidence thresholds > 0.3). Linked via infoblock property PROPERTY_ACCESSORIES. Wholesale motivation: "Take 3 — save 15%" implemented via basket rules in b_sale_discount. Free delivery threshold: "Add a certain amount and get free shipping". A simple widget that increases average order value by 10–20%.

Management via admin panel

Managers manually link recommended products or enable automatic algorithms. Display rules: category, price range, availability. A/B testing of different strategies — no developer needed.

Promo codes: proper implementation

Promo code UX:

• Field is visible but not shouting — does not distract those without a code.
• Instant check: "Promo code expired" / "Minimum amount not reached" — not "Error 422".
• Discount shown as a separate line in the total.
• Can remove promo code and apply another.

UX optimization: small details that matter

Desktop:

• Progress bar — user sees where they are.
• Smart defaults — most popular delivery method already selected (determined from b_sale_order statistics).
• Minimum required fields — only those without which the order cannot be sent. Middle name? Optional. Comment? Optional.
• Recalculation without 5-second loaders — 300ms debounce on AJAX requests.

Mobile:

• Large buttons — finger does not miss. min-height: 48px per Google guidelines.
• Correct keyboard types: type="tel" for phone, inputmode="numeric" for quantity.
• "Checkout" button fixed at bottom — position: sticky.
• Collapsible sections — screen space on 375px is precious.

Error handling:

• "Check card number" instead of "Payment processing error".
• Auto-scroll to first error — scrollIntoView({ behavior: 'smooth' }).
• "Item out of stock" — handled without losing filled data. Offer an alternative or remove with recalculation.

Integrations

• DaData — address, full name, TIN. Suggestions as you type, FIAS validation.
• Yandex.Maps — select pickup points on the map, geolocation for city detection.
• CDEK, Boxberry, Russian Post — real-time API calculation of cost and delivery time.
• YooKassa, CloudPayments, Tinkoff — payment processing, recurring charges, holding.
• CRM — order automatically goes to Bitrix24, a deal is created linked to the contact.
• Warehouse — real-time stock check via CCatalogStoreProduct::GetList().

Example AJAX request for delivery calculation:

// Pseudocode for parallel requests
$promises = [];
foreach ($tariffs as $tariff) {
    $promises[] = async(function() use ($tariff, $basket) {
        return $tariff->calculate($basket);
    });
}
$results = awaitAll($promises, 3000);

What's included

• Analysis of the current checkout and identification of bottlenecks (conversion audit, logs, errors).
• UX design: prototyping one-step form, approval with the client.
• Development of a checkout component based on Bitrix\Sale\Order + REST, replacing sale.order.ajax.
• Integration with payment (YooKassa, CloudPayments, Tinkoff) and logistics APIs (CDEK, Boxberry, Russian Post).
• Setup of promo codes, cross-sell, abandoned carts.
• Testing on real scenarios: desktop, mobile, tablets.
• Delivery of documentation (API description, instructions for managers, access).
• Employee training on the new cart.
• Post-release support — 2 weeks of monitoring and fixes.

Timelines

Order a cart audit today — see how much conversion is lost at each step. Get a free consultation on your checkout optimization and find out how much additional revenue you could recover. Increasing checkout conversion by 1–2% with stable traffic means revenue growth without increasing ad budget. The fastest ROI in e-commerce.