Setting up 1C-Bitrix order processing

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Our competencies:
Development stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1175
  • image_bitrix-bitrix-24-1c_fixper_448_0.png
    Website development for FIXPER company
    811
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    564
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    747
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    655
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    976

Configuring Order Checkout in 1C-Bitrix

The checkout page in Bitrix is managed by the bitrix:sale.order.ajax component. Most often, clients come to us with one of three problems: the delivery address autocomplete is not working, the delivery cost is calculated incorrectly when the city is changed, or the form fails to submit with no error in the console.

Structure of the Order Checkout Component

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

  • Checkout steps — controlled via the DELIVERY_MODE parameter (SPLIT_DELIVERY for step-by-step, ONE_PAGE for single-page)
  • Payer profiles — configured in Online Store → Buyers → Payer Types
  • Delivery services — connected in Online Store → Delivery Services
  • Payment systemsOnline Store → Payment Systems

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

Standard Configuration via the Admin Interface

Order form fields. In Online Store → Settings → Order Properties, configure the fields the buyer fills in during checkout: full name, phone, email, address. For each field, you set the type, whether it is required, and its association with the payer type.

Linking delivery to warehouses. If the store has multiple warehouses (Catalog → Warehouses), configure at checkout which warehouse the item ships from. This affects delivery cost and lead time calculations.

City autocomplete. The component can pull the city from the authenticated user's profile — the UF_CITY field from b_user. For anonymous users — via geolocation from the sale.location module or an external service (DaData, Yandex Maps).

Configuring Order Property Binding to Delivery

A common task is to show the delivery address only when courier delivery is selected, and to show a list of pickup points for click-and-collect. This is configured via component parameters in the template:

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

For conditional field display — via JS events from the component:

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

Configuration Timeline

Basic checkout configuration (form fields, delivery services, payment systems) — 4–8 hours. If conditional field visibility, geolocation, or API integration with delivery services is required — 1–3 working days.