What this solution does
The module provides integration between an online store built on the 1C-Bitrix platform and the r_keeper system via the UCS Delivery API. The solution fully automates the food and beverage ordering process: the menu from r_keeper is synchronized with the site catalog, orders placed on the site are transmitted to r_keeper, and preparation and delivery statuses are displayed in the customer's personal account.
Menu export to the trade catalog
Categories and dishes are automatically transferred from r_keeper to the catalog information block on a scheduled basis (configurable agent) or via the "Synchronize now" button. Prices are written to the selected catalog price type and, if necessary, duplicated in the information block properties. Attributes are populated including weight, unit of measurement, and nutritional value (calories, energy value, proteins, fats, carbohydrates), along with additional images. Dish images can be uploaded either only for new products or during every synchronization, based on administrator choice.
Dish modifiers, such as add-ons and ingredients, are exported as trade offers. The modifier directory is automatically created by the module and stored in a separate Highload block. The system allows excluding specific categories and dishes by their GUID from r_keeper, and automatically deactivates products that have been removed from the r_keeper menu.
The settings page displays the status and statistics of the last data export, including the count of added, updated, and deactivated items, along with any error messages.
Orders from the website are automatically created in the r_keeper system. Transmitted data includes the order composition, modifiers, buyer contact details, delivery address and information, payment method, and number of guests.
Two order transmission modes are available:
1. At checkout: the order is created in r_keeper first. If the restaurant declines the order, the website checkout process is blocked, and the customer sees a clear reason for the refusal.
2. After payment: the order is saved on the website and sent to r_keeper only after successful payment. If a transmission error occurs, the order is flagged, and both the customer and administrator receive a notification.
Order cancellation in r_keeper is synchronized with order cancellation in the store, including actions performed via the admin panel. A reference list of cancellation reasons is supported.
The delivery zone is verified against the provided address before the order is saved.
The rKeeper Omni Delivery (UCS) service is integrated. Delivery cost and time are calculated via the UCS API based on the address and order composition, and these details are displayed to the customer before they click the Place Order button.
The checkout page includes an address input field with suggestions, utilizing UCS geocoding.
The precise time delivery feature allows customers to select a specific date and time for receipt. Orders are sent to r_keeper with a scheduled time rather than a request for immediate delivery.
The item name in the shopping cart always matches the dish name, not the modifier or promotional offer name.
The system automatically sends notifications to administrators regarding failed order submissions or cancellations.
The module processes incoming webhooks from r_keeper Delivery to track order status changes.
Webhook security is enforced via a mandatory X-Token, an optional X-Signature, an IP address whitelist, and filtering by restaurant.
Mapping between r_keeper statuses and store order statuses is configured in the admin panel. Missing statuses can be created with a single click.
A complete log of all incoming webhook events is maintained. This ensures status data is preserved even if a webhook arrives before the order establishes a connection with r_keeper.
A status widget in the customer account displays a progress bar with stages: order accepted, confirmed, preparing, being collected/ready for pickup, courier en route, and delivered. The widget supports automatic updates and includes a manual refresh button.
Secrets and API tokens are transmitted exclusively over the HTTPS protocol to trusted hosts within UCS Delivery.
The address suggestion endpoint is protected against abuse by three rate limits: one per IP address, one per session, and one global limit for the entire site.
The module log is stored outside the website root directory and is not accessible via the HTTP protocol; logging is disabled by default.
The status widget displays order information only to the order owner.
Access to module settings is restricted to administrators.
Requirements include the 1C-Bitrix: Site Management system with the Information Blocks, Trade Catalog, Highload Blocks, and Online Store modules installed.
PHP version 8.2 or higher is required.
Connection to the UCS Delivery API requires the client_id, client_secret, and restaurant GUID (restaurantId) obtained from the r_keeper system.
For status synchronization, the system supports configuring a webhook template in the r_keeper Delivery service.
This module is designed for restaurants, cafes, bakeries, and ready-meal delivery services that use the r_keeper cash register system and the 1C-Bitrix platform for their product catalog and order processing.
General iT can install “Rkeeper (r_keeper) - menu, orders, statuses”, configure its settings and verify its operation in the existing project.