Flexible Order Status Customization in 1C-Bitrix

Flexible Order Status Customization in 1C-Bitrix

With a standard 1C-Bitrix installation, you get a basic set of order statuses: N (accepted), F (completed), P (paid), and so on. Real business processes are usually more complex: you need statuses like 'Pending approval', 'Awaiting prepayment', 'Manager review', 'Reservation confirmed'. Manually changing statuses in the admin panel risks errors and wastes time. In one project with 12,000 orders per month, 30% of managers' time went into manual status switching. Automation reduced this cost by 80%. We configure statuses to match your production, logistics, and communication stages. Below is the technical implementation and typical solutions.

Bitrix documentation

Why Proper Status Configuration Is Critical

Each order status is not just a label. It affects product reservation, sending notifications to the customer, integration with 1C, and the logic of managers' work. A status error can lead to double sales or shipping delays. A business-process-tailored status chain automates routines and reduces errors. According to our data, proper configuration reduces order processing time by up to 40%. Correct status configuration saves resources by reducing manual labor.

Status Structure (Technical Part)

Statuses are stored in the b_sale_status table. Key attributes:

• ID — code (Latin + digits), used in code and integrations
• Type — O (order) or D (delivery/shipment)
• Color — for visual highlighting in the order list
• 'Is a cancellation status' — automatically releases product reservations
• 'Order completed' — marks the order as finished, blocks some operations

Shipment statuses (D) are a separate entity for the multi-shipment model. They allow managing partial shipments, critical for B2B with multiple warehouses.

Comparison of Typical Status Sets

Step-by-Step Status Configuration Guide

1. Create a new status via OrderStatus::add().
2. Set the localized name via StatusLangTable::add().
3. Configure the transition matrix in the OnSaleOrderBeforeSaved handler.
4. Test on a test environment.
5. Deploy to the production site.

How to Add a New Status via API?

use Bitrix\Sale\OrderStatus;

$result = OrderStatus::add([
    'ID'           => 'WAIT_PREPAY',
    'TYPE'         => 'O',
    'NOTIFY_BUYER' => 'Y',
    'COLOR'        => '#f0a500',
    'SORT'         => 25,
]);

\Bitrix\Sale\Internals\StatusLangTable::add([
    'STATUS_ID'   => 'WAIT_PREPAY',
    'LID'         => 'ru',
    'NAME'        => 'Awaiting prepayment',
    'DESCRIPTION' => 'Order confirmed, awaiting payment',
]);

The NOTIFY_BUYER field sends an email to the customer when the status changes. If the status is final (e.g., 'Canceled'), set the CANCEL = Y flag for automatic reservation release.

Allowed Transitions Matrix

Restrict status transitions via the event handler:

AddEventHandler('sale', 'OnSaleOrderBeforeSaved', function(\Bitrix\Main\Event $event) {
    $order = $event->getParameter('ENTITY');
    if ($order->isNew()) return;

    $oldStatus = $order->getField('STATUS_ID');
    // Get new status via changedFields
    $changedFields = $order->getFields()->getChangedValues();
    $newStatus = $changedFields['STATUS_ID'] ?? $oldStatus;

    $allowedTransitions = [
        'N'           => ['F', 'WAIT_PREPAY', 'CANCEL'],
        'F'           => ['PROCESSING', 'CANCEL'],
        'WAIT_PREPAY' => ['F', 'CANCEL'],
        'PROCESSING'  => ['DELIVERING', 'CANCEL'],
        'DELIVERING'  => ['D', 'RETURN_INIT'],
    ];

    if (isset($allowedTransitions[$oldStatus]) &&
        $newStatus !== $oldStatus &&
        !in_array($newStatus, $allowedTransitions[$oldStatus])) {
        return new \Bitrix\Main\EventResult(
            \Bitrix\Main\EventResult::ERROR,
            new \Bitrix\Sale\ResultError("Transition from {$oldStatus} to {$newStatus} is forbidden"),
            'sale'
        );
    }
});

The transition matrix is a key element that prevents illogical status changes. We configure it for your business process to eliminate errors.

Implementation Examples

Standard B2C: New → Confirmed → Collecting → Handed to delivery → Delivered / Canceled

B2B with approval: New → Pending approval → Awaiting prepayment → Confirmed → In production → Ready for shipment → Shipped → Closed

With returns: Main chain + Return initiated → Goods received → Return completed

Changing Shipment Status

$shipmentCollection = $order->getShipmentCollection();
foreach ($shipmentCollection as $shipment) {
    if (!$shipment->isSystem()) {
        $shipment->setField('STATUS_ID', 'DELIVERING');
    }
}
$order->save();

Automatic Status Change

Automation via agents or events. For example, upon receiving a shipment status from 1C, automatically change the order status. Compared to the standard implementation, our integration with 1C processes statuses much faster, reducing response time. One client reduced return costs thanks to this setup.

How Does Integration with 1C Affect Statuses?

During exchange with 1C via CommerceML, statuses are synchronized automatically. For example, when 1C confirms a shipment, the order receives the 'Shipped' status. Without proper configuration, discrepancies can occur: the order is completed in Bitrix but in progress in 1C. To avoid this, we create event handlers that change the order status upon receiving a shipment status from 1C. This saves managers' working time.

Status Functionality Comparison

If the status does not change, check if the order is blocked by a 'Completed' or 'Canceled' status. Ensure the transition matrix allows the change. Also check the user permissions of the person trying to change the status.

What Is Included in the Work

• Audit of current statuses and business processes
• Design of the status scheme (transition matrix, notifications)
• Implementation: adding statuses, configuring transitions, integration with 1C and fiscal data operators
• Testing on a test environment
• Deployment to the production server
• Documentation on statuses and manager training
• 1 month of support after launch

Contact Us

We are a team with years of experience in 1C-Bitrix development. We have implemented many projects for order process configuration. We work with PHP 8.1+, MySQL/MariaDB, integrations via REST API. We guarantee quality and documentation. Our status schemes significantly reduce reservation error rates. Contact us for an audit of your statuses and get a consultation on business process optimization.

Timeframes

Configuring 5–8 statuses with names and colors — from 2 to 4 hours. Configuration with transition matrix, 1C integration, and custom notifications — from 1 to 2 business days. Specific timelines are discussed after analyzing your task. For complex projects with multiple warehouses and returns, the timeline may increase to 3–4 days, but we always meet agreed deadlines.

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.