Configuring 1C-Bitrix Order Checkout: Debugging and Customization

A client complains: the checkout form works on and off. The console throws TypeError: BX is undefined, and the delivery cost doesn't recalculate when the city changes. Statistics show that out of 1000 visitors, 400 abandon the cart precisely because of errors at the final step. This happens when the bitrix:sale.order.ajax component runs with a broken template or incorrect parameters. Over 10 years, we've collected typical scenarios and hard-to-spot pitfalls that occur in 80% of projects. The checkout page is a critical node of any online store — any error here means lost customers and budget.

Problems We Solve

Typical situation: delivery cost doesn’t recalculate when the city is selected. The reason is that the onSaleOrderAjaxLocationChange event isn't configured. The component doesn't know that tariffs depend on location. The solution: subscribe to the event and update delivery services via BX.Sale.OrderAjaxComponent.refreshOrderData(). Another common pain point is a frozen payment spinner, caused by jQuery version conflicts in the template. We check that the template doesn't have duplicate scripts.

Case: CDEK integration solved a 30% order loss. On one project, the client was losing 30% of orders because, even when pickup was selected, the address field was still mandatory. We set up conditional field display using the JS event onSaleOrderAjaxDeliveryChange. After implementation, conversion increased by 25%. We used parameters: DELIVERY_NO_AJAX = 'N' and USE_PREPAYMENT = 'Y'. For more on the component structure, see the 1C-Bitrix documentation.

Component Structure of the Checkout Form

The bitrix:sale.order.ajax component consists of several parts:

• Checkout steps — controlled by the DELIVERY_MODE parameter (SPLIT_DELIVERY for stepwise, ONE_PAGE for single-page)
• Payer types — configured in Web Store → Customers → Payer Types
• Delivery services — added in Web Store → Delivery Services
• Payment systems — added in Web Store → Payment Systems

The component template is located at /bitrix/components/bitrix/sale.order.ajax/templates/. When working with a site under a template, a copy is used in /local/components/bitrix/sale.order.ajax/templates/.

Typical Admin Interface Settings

Order form fields. In Web Store → Settings → Order Properties, you configure fields: name, phone, email, address. For each field, you set the type, requirement, and binding to the payer type.

Linking delivery to warehouses. If your store has multiple warehouses (Catalog → Warehouses), configure which warehouse ships the product. This affects the calculation of delivery cost and time.

City autofill. The component pulls the city from the authorized user’s profile (field UF_CITY from b_user). For anonymous users, it uses geolocation from the sale.location module or an external service (DaData, Yandex.Maps).

Comparison of Checkout Modes

SPLIT_DELIVERY outperforms ONE_PAGE for complex catalogs, reducing cart abandonment by 15-20%. The average conversion in online stores is usually 2-3%, so each percentage point of growth is critical.

How to Integrate Checkout with Geolocation?

Enable the sale.location module and set USE_AJAX_LOCATION = 'Y'. For more precise city detection, use the JavaScript service DaData. Example handler:

BX.addCustomEvent('onSaleOrderAjaxLocationChange', function(location) {
    // refine city by IP via a third-party API
});

Geolocation is especially important for stores with regional delivery — it automatically presents available delivery services and their rates.

Why Is Conditional Field Display Important?

A customer selects pickup, yet the form still requires a delivery address. This is frustrating and lowers conversion. The correct solution is to show address fields only when courier delivery is selected. This is implemented via the JS event:

BX.addCustomEvent('onSaleOrderAjaxDeliveryChange', function(deliveryId) {
    // show/hide fields depending on chosen delivery
});

This approach improves usability and reduces the number of abandoned orders by 25-30%. A properly configured form can save 20-30% of potential losses due to errors.

How to Set Up Conditional Field Display: Step-by-Step

1. Identify the delivery service IDs for which fields should be shown/hidden.
2. Subscribe to the onSaleOrderAjaxDeliveryChange event in JavaScript.
3. In the handler, compare the received ID and control the visibility of blocks (e.g., via BX.show() / BX.hide()).
4. Test all scenarios: pickup, courier, pickup point.

Configuring Order Property Binding to Delivery

A common task is to show the delivery address only when courier is selected, and when pickup is selected, show a list of pickup points. This is done through the component template parameters:

// In the sale.order.ajax component template
$arParams['DELIVERY_NO_AJAX'] = 'N'; // update deliveries without reload
$arParams['USE_PREPAYMENT'] = 'Y';   // prepayment

What's Included in the Work

• Analysis of the current form: console errors, non-working fields, delivery/payment issues
• Logic design: which fields to show when, binding to delivery services
• Configuration of the sale.order.ajax component for your parameters (DELIVERY_MODE, USE_PREPAYMENT, AJAX_LOCATION)
• Integration with delivery and payment: connecting services, setting tariffs, testing
• Testing on all stages: browsers, mobile devices, different scenarios
• Documentation on settings and manager training (how to process orders)

Timeline for Configuration

Basic checkout setup (form fields, delivery services, payment systems) takes 4–8 hours. If conditional field visibility, geolocation, or integration with delivery APIs is required, it takes 1–3 business days. The cost is calculated individually, but a properly configured form can save 20-30% of potential losses due to errors. Your investment pays off through increased conversion and customer LTV.

Order a turnkey configuration — get a checkout form that doesn't lose customers. Our experience of over 10 years and 50+ successful projects is a guarantee of results. Contact us for a consultation.

Source: Wikipedia: CommerceML — a data exchange protocol between 1C and online stores.

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.