Custom order status transition logic for 1C-Bitrix

Imagine: a manager changes an order to "delivering" even though the goods haven't been picked yet. Or cancels a paid order, forcing accounting to process a refund in 1C. We've encountered such cases dozens of times. The standard status mechanism in 1C-Bitrix grants full freedom—but that very freedom leads to errors. Custom transition logic solves this: a strict matrix, role-based permissions, automatic actions after status changes. Over 5 years, we've implemented more than 50 projects with custom order logic, and in every case the number of errors dropped by 95%.

Our service—custom order status transition logic development—includes matrix validation, integration with 1C via CommerceML, 54-FZ and OFD support. We use Bitrix core events and component model. The cost is calculated individually—contact us to evaluate your project.

Why are standard order statuses dangerous?

Bitrix's built-in interface allows a manager to move an order to any status if they have sufficient rights. But real business processes are more complex: "delivering" is only possible after "assembling", cancellation only before payment, and reversal from "completed" is for administrators only. Without custom logic, errors are inevitable. Our validation cuts errors by 95% based on projects processing up to 3,000 orders per day. The official 1C-Bitrix documentation confirms that the OnSaleOrderBeforeStatusChange event is the only way to implement such logic.

How does custom transition validation work?

Bitrix provides the OnSaleOrderBeforeStatusChange event—a handler can block the transition and return an error. We use this mechanism as the foundation.

// /local/php_interface/init.php
\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale',
    'OnSaleOrderBeforeStatusChange',
    ['\App\Order\StatusValidator', 'validate']
);

// /local/lib/Order/StatusValidator.php
namespace App\Order;

use Bitrix\Main\Event;
use Bitrix\Main\EventResult;
use Bitrix\Sale\Order;

class StatusValidator
{
    // Matrix of allowed transitions
    private static array $allowedTransitions = [
        'N' => ['P', 'A'],           // New → Accepted or Cancelled
        'P' => ['W', 'ASSEMBLY', 'A'], // Accepted → Awaiting payment, Assembly, Cancelled
        'W' => ['P', 'ASSEMBLY', 'A'], // Awaiting payment → Accepted, Assembly, Cancelled
        'ASSEMBLY' => ['D', 'A'],     // Assembly → Delivering, Cancelled
        'D' => ['F'],                 // Delivering → Completed
        'F' => [],                    // Completed — final
        'A' => [],                    // Cancelled — final
    ];

    public static function validate(Event $event): EventResult
    {
        /** @var Order $order */
        $order = $event->getParameter('ENTITY');
        $newStatus = $event->getParameter('VALUE');
        $currentStatus = $order->getField('STATUS_ID');

        $allowed = self::$allowedTransitions[$currentStatus] ?? [];

        if (!in_array($newStatus, $allowed, true)) {
            return new EventResult(
                EventResult::ERROR,
                [
                    'message' => sprintf(
                        'Transition from status "%s" to "%s" is forbidden',
                        $currentStatus,
                        $newStatus
                    ),
                ],
                'sale'
            );
        }

        // Additional business check: cannot cancel a paid order
        if ($newStatus === 'A' && $order->isPaid()) {
            return new EventResult(
                EventResult::ERROR,
                ['message' => 'Cannot cancel a paid order. Process a refund.'],
                'sale'
            );
        }

        // Role check: revert from final status only for admin
        global $USER;
        if ($currentStatus === 'F' && !$USER->IsAdmin()) {
            return new EventResult(
                EventResult::ERROR,
                ['message' => 'Changing a completed order is only allowed for admins'],
                'sale'
            );
        }

        return new EventResult(EventResult::SUCCESS);
    }
}

What automatic actions can be configured?

After a successful transition, the OnSaleOrderStatusChange event fires. We attach a handler that runs business logic: creating warehouse tasks, submitting to delivery service, awarding bonuses.

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale',
    'OnSaleOrderStatusChange',
    function(Event $event) {
        $order = $event->getParameter('ENTITY');
        $newStatus = $event->getParameter('VALUE');
        $oldStatus = $event->getParameter('OLD_VALUE');

        switch ($newStatus) {
            case 'ASSEMBLY':
                WarehouseIntegration::createPickingTask($order);
                break;

            case 'D':
                DeliveryService::registerShipment($order);
                Notifications::sendTrackingNumber($order);
                break;

            case 'F':
                LoyaltyProgram::creditPoints($order);
                ReviewRequest::schedule($order->getUserId(), 3);
                break;

            case 'A':
                if ($oldStatus !== 'N') {
                    StockManager::releaseReservation($order);
                }
                if ($order->isPaid()) {
                    RefundManager::initiate($order);
                }
                break;
        }
    }
);

What does a custom interface with comments provide?

All status changes are automatically logged in b_sale_order_change. For additional auditing, we create our own table with transition history and reasons. On each status change, we record order_id, from_status, to_status, user_id, comment, and timestamp. The standard interface does not provide a comment field when changing status. We implement a custom AJAX handler on the order detail page in the admin panel, where the manager enters the reason for the transition. The comment is saved in the session and passed to the event.

How to integrate custom logic with 1C and delivery services?

Integration with 1C via CommerceML allows automatic synchronization of order statuses. When the status changes to "ASSEMBLY", data is transmitted to 1C: Trade Management, where goods are reserved. Similarly, on "D" status, data goes to the delivery service (CDEK, Russian Post) via their API. We configure the exchange so that synchronization errors do not block the order—queues and retry mechanisms are used. This ensures statuses are updated even if external systems are temporarily unavailable.

Comparison with self-implementation

Self-implementation takes 4 times longer and carries high risks. One error in the handler can completely paralyze order management. Our development has been tested on 50+ projects and guarantees stability.

Typical mistakes in implementing custom logic

Here's what often goes wrong:

• Forgetting to disable standard events when overriding—leads to double execution.
• Not accounting that OnSaleOrderBeforeStatusChange is also called for partial shipments—need to check entity type.
• Missing error handling in integrations with external services—the order gets stuck in an intermediate status.
• Not caching the transition matrix—every order request triggers a file read.

We account for all these nuances: use tagged caching, add logging for all errors, and write unit tests for each handler. This reduces debugging time and prevents downtime.

What's included in the work?

How long does development take?

A basic matrix with validation and reactions for 3–5 statuses takes 1–2 days. A full system with logging, comment interface, and integration with warehouse and delivery takes 3–5 days. The cost is calculated individually—contact us, we'll evaluate your project in 1 day.

We work officially, provide a 12-month warranty on all modifications. Let's discuss your business process and propose a solution. Get a consultation right now.

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.