Custom 1C-Bitrix Checkout: Flexible Logic, Integrations, Timelines

Custom 1C-Bitrix Checkout Development

The standard bitrix:sale.order.ajax component, despite its flexible settings, has rigid architectural limitations: the checkout form relies on server-side rendering with AJAX updates rather than a reactive interface. Implementing complex conditional logic (e.g., real-time delivery cost calculation or dynamic fields based on product types) without rewriting the component is nearly impossible. In our practice (over 50 1C-Bitrix projects in 10+ years), we have encountered projects where customizing the standard checkout took more time than building a custom one from scratch. Therefore, a custom checkout either involves deep modification of the standard component or building a new one on top of the sale module API.

Why Custom Checkout?

Typical problems solved by a custom checkout:

• Rigid field logic. The standard component cannot dynamically change field sets based on user selection — only through order property settings and CSS toggles. A custom checkout allows rules like: when "Legal entity" is selected, show INN, KPP, and bank account; when delivery method "Russian Post" is selected, hide address fields and show a list of parcel lockers via CDEK or Boxberry API; when the cart contains items from the "Oversized" category, automatically remove "Courier delivery" from available options.

• Delivery cost calculation only at the delivery step. The standard component calculates delivery cost after the user selects an option. A custom checkout can show the delivery price immediately when the address is entered. For example, using DaData (address standardization) and CDEK API: upon address input, a request is sent to DaData for coordinates, then the coordinates are passed to CDEK API /v2/calculator/tariff with weight parameters from the cart. The result is displayed to the user before they choose a delivery method — they see the price during address entry. This requires a proxy controller on the Bitrix side and proper caching of results by key {postal_code}_{weight_kg}.

• Order splitting by suppliers. Marketplaces often face scenarios where one order contains items from different suppliers with different delivery conditions. The standard checkout does not support multiple shipments from different suppliers in one order. We solve this with a custom architecture described below.

How Custom Checkout Works

A custom checkout is built on two levels:

• Server side — a PHP controller that receives form data via AJAX, validates it (payer type, required fields from b_sale_order_props_variant), creates an order using \Bitrix\Sale\Order::create(), calculates delivery via \Bitrix\Sale\Delivery\Services\Manager::getById(), applies discounts and coupons via \Bitrix\Sale\DiscountCouponsManager, and returns JSON with results or errors.
• Client side — a React/Vue component that manages form state, shows/hides fields based on user choices, and displays updated delivery cost without page reload.

Example of programmatic order creation:

$order = \Bitrix\Sale\Order::create('s1', $userId);
$order->setPersonTypeId($personTypeId);

$basket = \Bitrix\Sale\Basket::loadItemsForFUser(
    \Bitrix\Sale\Fuser::getId(), 's1'
);
$order->setBasket($basket);

$propertyCollection = $order->getPropertyCollection();
$propName = $propertyCollection->getItemByOrderPropertyCode('NAME');
$propName->setValue('Ivan Ivanov');

$shipmentCollection = $order->getShipmentCollection();
$shipment = $shipmentCollection->createItem();
$service = \Bitrix\Sale\Delivery\Services\Manager::getById($deliveryId);
$shipment->setFields([
    'DELIVERY_ID' => $deliveryId,
    'DELIVERY_NAME' => $service['NAME'],
    'CURRENCY' => 'RUB',
]);

$result = $order->save();

Implementing Conditional Field Logic

Conditional logic is implemented on the server via event handlers of the sale module: OnSaleComponentOrderMakeOrder, OnSaleDeliveryServiceCalculate. On the client side — through the component's state machine. We follow official 1C-Bitrix documentation for correct API usage (see Wikipedia: 1C-Bitrix).

Standard vs Custom Checkout Comparison

Custom checkout loads on average 40% faster on the first request thanks to reactive interface and asynchronous data loading. This reduces server load and improves UX, leading to a 15–25% decrease in cart abandonment.

Our Work Process

1. Analysis — audit of the current checkout, requirements gathering, agreeing on field logic and integrations.
2. Design — database schema (if new highload blocks are needed), API architecture, interface prototype.
3. Implementation — writing the server controller, frontend component, integration with payment systems and delivery services.
4. Testing — scenarios: anonymous user, authorized user, legal entity, individual, different delivery/payment combinations. Automated tests with PHPUnit and Jest.
5. Deployment — rollout to production, monitoring in the first days.

What You Get

Upon project completion, you receive:

• API and checkout architecture documentation.
• Access to the code repository.
• Deployment and configuration instructions.
• 2-hour online training for your developers.
• 2 months of free support after delivery.

Estimated Timelines

Basic implementation (one payer type, 2–3 delivery services, 1–2 payment systems) — from 2 to 3 weeks. Complex projects with non-standard business logic, many integrations, or order splitting by suppliers — up to 2 months. The cost is calculated individually after an audit.

Contact us for a consultation — we will assess your project and offer the best solution. Order a custom checkout to increase conversion and improve user experience.

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.