Order Scenarios

What this solution does

Order processing in an online store often requires performing numerous identical operations: changing the status after payment, selecting a delivery service based on the city, modifying the payment method for legal entities, or marking an order for the warehouse. Manual execution of these tasks by managers leads to errors, slowed workflows, and inconsistent processes. Built-in Bitrix tools either do not support such rules or require a programmer for every change.

The Order Scenarios module automates logic of the type "if the order meets conditions, perform actions." Rules are created in the admin panel using a visual builder labeled "When / If / Then." After an order is saved—on the site, in the admin panel, or during 1C exchange—the module checks all scenarios in the background and applies the matching ones.

Rule configuration is safe: any scenario can be tested on a real order with detailed verification of each condition. The test mode, enabled after installation, runs scenarios on the live order stream without making changes. Every trigger is logged with specific details of what was changed.

Capabilities

The "When / If / Then" builder operates without programming. It supports grouping conditions using "AND," "OR," "NOT" logic with nesting capabilities, and allows restricting scenario actions to specific sites.

The despi.orderutils module (Order Scenarios) enables automation configuration based on conditions related to the order itself, its properties, individual payments, and shipments.

Conditions can check the order status, payer type, flags for 'paid' and 'cancelled', as well as the payment and delivery services used. All data types are supported for order properties: string, number, flag, list, date, location, and file, including multiple values. Each type has its own comparison rules.

Specific conditions apply to payments and shipments using logic such as 'any', 'all', or 'none' of them.

Scenarios can change the order status, select a payment system for unpaid payments (applying the selection to all or only the first one), and change the delivery service for unshipped items with an optional cost recalculation.

When setting an order property value, the editor automatically adapts to the property type. Scenario execution can be triggered automatically upon saving the order (for any save action, only on creation, or only on modification) or manually by order number.

The execution policy defines the order of rule chains, the frequency of triggering (once per order or on every change), and the behavior of stopping the check of remaining rules after one rule is triggered.

Scenario validation displays the result of each condition with the actual value, shows changes in the format 'was → is', and applies actions only after confirmation.

Test mode allows scenarios to run on real orders without saving them, logging in the journal what changes would have been made.

The execution log records the result, changes made, and the reason for each trigger. Filters are available by order, scenario, result, and date, along with automatic cleanup of old records.

Execution is secure: the background queue does not slow down or disrupt the order checkout process. Protection against infinite loops is implemented, and in case of an error, the order is not partially modified. The queue agent status is displayed in settings.

Profiles are independent sets of scenarios with their own settings and logs. Profiles are activated with a single click.

The scenario list is organized as convenient cards. Features include drag-and-drop reordering, color tagging, copying scenarios, and marking those with errors.

General iT can handle the implementation of “Order Scenarios”, from installation to configuration and compatibility checks.