What this solution does
The r_keeper Order Status Exchange module provides automatic synchronization of order statuses between the r_k Delivery system and an online store built on the 1C-Bitrix platform. When an order status changes in r_k Delivery, the system sends a webhook that the module intercepts, verifies, and uses to update the order status in the customer's personal account. The client sees real-time information about the order progress: accepted, preparing, courier en route, or delivered. This solution is optimized for food delivery websites and restaurants that accept orders online and process them in rKeeper.
The operation relies on an event-driven model: every time an order status changes in r_k Delivery, a request is sent to the module. The system verifies the request authenticity, locates the corresponding order in the store using the order number from the r_keeper Order Sending connections table, and assigns the new status. If an order is cancelled in rKeeper, the status is automatically updated to Cancelled on the website as well. All events are logged in the history table. The module does not use API requests to rKeeper, requires no agent or cron job configuration, and updates the status instantly upon receiving the notification.
The built-in reference list supports the following r_k Delivery statuses: new, confirmed, sent to kitchen, preparing, prepared, assembly, assembled, with courier, en route, delivered, cancelled.
The module synchronizes order statuses between the rKeeper system and the online store. For each rKeeper status, you can map a corresponding store order status or select the option to leave it unchanged. A separate setting handles unknown statuses that are not present in the reference list.
A quick creation button allows generating standard store statuses RA–RG and RC, such as Order Received, Preparing, Courier on the way, Delivered, and Cancelled. These statuses are included in the default mapping, ensuring the module works immediately after creation.
ORDER STATUS IN THE PERSONAL CABINET
The customer order card displays a widget with a progress bar showing the stages: received, confirmed, preparing, being assembled, on the way, delivered. Cancelled orders show a separate status of Cancelled. The status updates manually via the Update button or automatically at a specified interval. The widget is visible only to the order owner or administrator. The sale.personal.order.detail component integrates into the standard order page without template modification. Enabling or disabling the widget is done manually.
SECURITY
Token verification is mandatory via the X-Token header or Authorization: Bearer header. Order status changes are impossible without a valid token.
The module ensures secure exchange of order statuses between the r_keeper system and the website. X-Signature verification is optional: it can be based on a fixed value or an HMAC signature of the request body using sha256, sha1, or md5 algorithms. Access is restricted to IP addresses listed in the r_keeper whitelist. The system is configured to accept events only from a single restaurant identified by the restaurantId GUID; requests from other locations are automatically rejected.
Control and auditing are performed via a webhook history table that records rKeeper order numbers, website order numbers, status, and event date. The log of status reception and changes is stored in a directory outside the website root and is inaccessible via HTTP. All rejected requests are logged with the specific reason for rejection: invalid token, signature error, IP mismatch, or request from an external restaurant.
Configuration includes generating a ready-to-use URL for the r_k Delivery template, setting the token and signature, managing the IP whitelist, and specifying the restaurant GUID. The module supports mapping rKeeper statuses to store statuses, including the creation of missing statuses. The personal account interface allows enabling the widget, configuring the order card path, and setting the auto-refresh interval. Detailed logging can also be enabled.
Required dependencies include the Internet Store module (sale) and the r_keeper - Order Sending module (goldencode.rkeeperorders), which provides the link table for matching rKeeper orders with website orders. Access to notification templates in r_k Delivery via the api channel is also required.
The r_keeper module handles only order status exchange. Menu export is performed by a separate solution named r_keeper menu synchronization.
When needed, General iT can implement “Rkeeper (r_keeper) - Order Status Exchange”, configure the module and verify it against the current website setup.