What this solution does
The r_keeper order submission module transfers online store orders to the rKeeper system via the UCS Delivery API and a built-in delivery service. It includes delivery cost calculation and delivery zone verification based on the address. This solution is designed for food delivery websites built on the 1C-Bitrix: Site Management platform integrated with a restaurant in rKeeper.
Order transmission supports two configurable stages. The 'at checkout' stage creates an order in rKeeper before the website order is saved; if rKeeper rejects the order, the checkout process is blocked and the customer sees the reason for rejection. The 'after payment' stage sends the order to the restaurant only after payment confirmation.
Cancelling an order in the store automatically triggers the cancellation of the corresponding order in rKeeper, with a configurable reason for rejection. The link between the 'website order' and the 'rKeeper order' is stored in a dedicated module table, which prevents duplicate submissions and allows cancellation based on this established link.
The cart contents are transmitted as rKeeper dishes identified by their GUID. Trade offers acting as modifiers are transmitted as dish modifiers. The cart item name always corresponds to the product name, not the specific trade offer.
The following data is transmitted: guest name, phone number, and email address, order comment, number of guests, delivery time (date and time specified; if not selected, the mode is set to 'as soon as possible'), and the delivery address.
The address is determined via UCS suggestions (city, street, house, postal code, coordinates) and transmitted with details: apartment, floor, entrance, intercom. The restaurant for delivery is automatically selected based on the address coordinates. Website payment methods are mapped to rKeeper payment types (cash, card, online) using payment system IDs. Pickup services are configured separately; such orders are transmitted to rKeeper as pickup without an address.
The 'rKeeper Delivery (UCS)' service calculates the cost via the UCS Delivery API based on the address and cart contents. The price is displayed to the customer immediately during order checkout, before clicking the 'Place Order' button. Delivery zone validation occurs before saving the order: the address is recognized via UCS suggestions, and the serving restaurant is identified by coordinates. Checkout is blocked if the address is outside the delivery zone or the order total is below the minimum, with a clear message displayed. Orders without an address, such as pickup, do not undergo zone validation. API unavailability does not block order placement. The website displays an address selection window with auto-suggestions and a 'delivery by time' option; selected values are saved as order properties.
A paid order that fails to transfer to rKeeper is marked as problematic in the admin panel with a specified reason. The administrator receives an email with a link to the order, while the customer receives an email and a popup window on the website after returning from the payment system. A file-based log with rotation is maintained, and the latest entries are accessible on the settings page.
Connection setup requires entering client_id, client_secret, and the restaurant ID. API addresses can be overridden if necessary. Order configuration includes setting the sending stage, delivery zone validation, cancellation conditions and reasons, and an email address for error notifications. It is required to map order properties (name, phone, email, city, address, apartment, floor, entrance, intercom, delivery date and time) to your site codes, and to specify IDs for pickup services and payment systems. Log recording can be enabled.
The module requires the Information Blocks (iblock) and Online Store (sale) components to be installed. An UCS Delivery API account with rights to receive restaurant orders is required. The rKeeper menu catalog is populated by a separate solution named rKeeper: menu export; these modules operate independently.
If “Rkeeper (r_keeper) - Order Sending” fits the task, General iT can install the module, configure it and verify the result in the project.