Order Ready Notification Setup in 1C-Bitrix

How to Set Up Order Ready Notification in 1C-Bitrix

A customer places a pickup order, waits for the product, but no notification arrives—they either come too early or forget about the order. This leads to reservation cancellations, returns, and lost loyalty. We solve this: the "Your order is ready for pickup" notification is sent instantly when a warehouse staff changes the status. Our engineers—with 10+ years of Bitrix experience—guarantee a reliable turnkey solution. Our 1C-Bitrix notification setup for pickup orders ensures timely alerts, increasing completion rates by 15–20% and reducing returns by up to 30%. For an average order of $30, that's a saving of $9 per return. Setup costs start at $200, with a typical payback period of 2–3 months. The investment for this service ranges from $200 to $700, with a typical payback of 2–3 months.

Timely notification is critical because buyers rely on the storage period. If not notified in time, the order won't be picked up. If notified too early, the customer arrives but the goods aren't ready. Proper configuration eliminates both scenarios. Based on our practice, timely notifications increase pickup order completion rates by 15–20% and reduce returns by up to 30%. The return on investment from implementing this solution can be up to 30% of return costs—at an average order of $30, that's about $9 per return.

Why Correct Configuration Matters

Misconfiguration leads to failures: notifications arrive late, don't reach the customer, or contain the wrong store address. This results in dissatisfaction and returns. Proper configuration ensures:

• Instant sending after status change
• Reliable operation of the chosen channel (SMS, Telegram, email)
• Up-to-date data on the pickup point and storage period

We use custom statuses and events as described in Bitrix documentation for immediate response. order statuses

Which Notification Channels Are Most Effective?

Telegram notifications are delivered 2–3 times faster than SMS but require customer subscription. SMS is universal and reliable, email is cheap. Combining channels increases delivery probability to 99.9%.

How Notification Affects Conversion

Timely notification increases pickup order completion rates by 15–20%. The customer receives a clear signal: "Your order is waiting." If delayed, the likelihood of non-pickup doubles. Our clients report a return reduction of up to 30% after system setup. Payback period is 2–3 months.

Typical Order Statuses and Notification Trigger

Custom status RC is the entry point for notification. Without it, the mechanism doesn't work. Bitrix has no built-in "Ready for Pickup" status. We create a custom one:

Store → Settings → Order statuses → Add:

• Symbolic code: RC (Ready for Collect)
• Name: "Ready for Pickup"
• Color: green

After creating the status, a handler for its change:

\Bitrix\Main\EventManager::getInstance()->addEventHandler( 'sale', 'OnSaleOrderStatusChange', function (\Bitrix\Main\Event $event) { $order = $event->getParameter('ENTITY'); $newStatus = $order->getField('STATUS_ID'); if ($newStatus !== 'RC') { return; // We only care about "Ready for Pickup" } // Get the pickup store from the order property $pickupStoreProp = $order->getPropertyCollection() ->getItemByOrderPropertyCode('PICKUP_STORE_ID'); $storeId = $pickupStoreProp ? $pickupStoreProp->getValue() : null; $storeInfo = null; if ($storeId) { $storeInfo = \Bitrix\Catalog\StoreTable::getById($storeId)->fetch(); } // Format and send notification \Local\Notifications\ReadyForPickupNotifier::notify($order, $storeInfo); } ); 

Notification Class

// /local/lib/Notifications/ReadyForPickupNotifier.php namespace Local\Notifications; use Bitrix\Sale\Order; class ReadyForPickupNotifier { public static function notify(Order $order, ?array $storeInfo): void { $userId = $order->getUserId(); $user = \Bitrix\Main\UserTable::getById($userId)->fetch(); $storeName = $storeInfo['TITLE'] ?? 'the store'; $storeAddress = $storeInfo['ADDRESS'] ?? ''; $orderId = $order->getId(); // Storage period from settings (default 5 days) $holdDays = (int)\Bitrix\Main\Config\Option::get( 'local.pickup', 'hold_days', 5 ); $holdUntil = date('d.m.Y', strtotime("+{$holdDays} days")); $message = "Order #{$orderId} is ready for pickup at {$storeName}.\n"; if ($storeAddress) { $message .= "Address: {$storeAddress}\n"; } $message .= "Storage period: until {$holdUntil}."; // Telegram if (!empty($user['UF_TELEGRAM_CHAT_ID'])) { \Local\Telegram\BotService::sendMessage( $user['UF_TELEGRAM_CHAT_ID'], $message ); } // SMS via service $phone = $order->getPropertyCollection() ->getPhone() ?->getValue(); if ($phone) { \Local\Sms\SmsService::send($phone, $message); } // Email — standard Bitrix mechanism // Create event for mail template \CEvent::Send('ORDER_READY_FOR_PICKUP', SITE_ID, [ 'ORDER_ID' => $orderId, 'STORE_NAME' => $storeName, 'STORE_ADDRESS' => $storeAddress, 'HOLD_UNTIL' => $holdUntil, 'USER_EMAIL' => $user['EMAIL'], 'USER_NAME' => $user['NAME'], ]); } } 

Email Template Setup

The email notification template is created under Settings → Mail events → Templates → Add with event type ORDER_READY_FOR_PICKUP. Use variables #ORDER_ID#, #STORE_NAME#, #STORE_ADDRESS#, #HOLD_UNTIL#. Example email text:

Hello, #USER_NAME#! Your order #ORDER_ID# is ready for pickup at #STORE_NAME#. Address: #STORE_ADDRESS# Storage period: until #HOLD_UNTIL#. Best regards, your online store. 

What to Do If the Notification Didn't Arrive?

We include delivery monitoring: check send logs and channel status. Typical failure causes: wrong phone number, disabled Telegram bot, or inactive email. We configure automatic retry through an alternative channel — for example, if SMS fails, we send email. This increases system reliability to 99%. Additional information on Bitrix24 REST API can be used for integration.

Automatic Status Transition on Stock Arrival

If the item was out of stock at purchase, the order should automatically change to "Ready for Pickup" when stock arrives:

\Bitrix\Main\EventManager::getInstance()->addEventHandler( 'catalog', 'OnProductUpdate', function (\Bitrix\Main\Event $event) { $productId = $event->getParameter('ID'); $fields = $event->getParameter('FIELDS'); if (!isset($fields['QUANTITY']) || $fields['QUANTITY'] <= 0) { return; } // Find waiting pickup orders for this product $waitingOrders = \Local\Orders\PickupOrderFinder::getWaiting($productId); foreach ($waitingOrders as $waitingOrderId) { $order = \Bitrix\Sale\Order::load($waitingOrderId); if ($order && $order->getField('STATUS_ID') === 'N') { $order->setField('STATUS_ID', 'RC'); $order->save(); } } } ); 

Scope of Work and Process

• Creation of custom status "Ready for Pickup" with handler
• Setup of multichannel notifications (SMS, Telegram, email)
• Integration with pickup points (store name and address insertion)
• Delivery monitoring and automatic retry on failure
• Documentation and manager training
• 3-month warranty on all modifications

1. Analysis — study current statuses and pickup logic.
2. Design — create transition scheme and notification channels.
3. Implementation — code custom status, handler, and services.
4. Testing — test all scenarios: status change, out-of-stock, SMS gateway failure.
5. Deployment — deploy to production, set up monitoring.
6. Training — show managers how to manage statuses.

Typical Configuration Mistakes

• Forgetting to create the email event — emails don't send.
• Not specifying the store ID in the order property — notification without address.
• Not accounting for caching — notification arrives with delay.
• Not checking REST API access rights (for Telegram) — channel doesn't work.

Our engineers with 10+ years of experience eliminate these errors during testing.

Timelines and Warranty

Custom status, handler, multichannel notification — 4 to 8 hours ($200–$400). Automatic transition on stock arrival — another 4–6 hours ($150–$300). All work carries a 3-month warranty. Contact us to discuss your project details. Order the setup — get a turnkey solution.

Deliverables include:

• Fully functional custom status with event handler
• Multichannel notification integration
• Automatic status transition (if applicable)
• Delivery monitoring and retry logic
• Documentation and training