What this solution does
The r_keeper menu synchronization module provides periodic data export from the rKeeper system via the UCS Delivery API to the trade catalog of the 1C-Bitrix: Site Management platform. This solution is designed for food delivery websites and restaurants that manage their assortment in rKeeper, enabling automatic maintenance of current dishes, prices, and stock levels without manual entry.
The module operates using a Bitrix agent with a configurable polling interval. The system requests the current menu through the UCS Delivery API and synchronizes it with the catalog information block: creating missing sections and products, and updating existing ones. Element identification is performed using GUIDs from rKeeper (XML_ID), which prevents duplicate creation during repeated runs. Exports can also be triggered manually via a button in the settings. The module functions correctly both with built-in hits and when agents are moved to the system cron scheduler, requiring no additional server configuration.
The following data is exported to the catalog:
— Menu categories, which form a nested structure of information block sections;
— Dishes, created as catalog products with the transfer of name, description, and price;
— Dish images: files are downloaded to the server, cached, and not re-downloaded unless the source data changes.
The "Rkeeper" module synchronizes the menu from the r_keeper system to the information system. Nutritional data (calories, energy value, proteins, fats, carbohydrates), weight, and measurement units are transferred to configurable information block properties. When a dish is in the r_keeper stop-list, its stock quantity is set to zero; once removed from the stop-list, the stock is automatically restored. Modifiers (ingredients) are exported only when the corresponding option is enabled.
The modifiers directory is maintained in a Highload block. The modifiers themselves are exported as trade offers into a separate information block and linked to dishes via the CML2_LINK mechanism. The offer price is calculated as the sum of the base dish price and the selected modifier price. The creation of the Highload block, the property directory, and the links between information blocks occurs automatically without altering any existing trade catalog link configuration.
The module offers flexible data control settings. Prices are recorded in the selected price type and can optionally be duplicated in an information block property. Categories and individual dishes can be excluded from export by specifying their GUID. An option to deactivate items removed from the menu is active: products and offers missing from r_keeper are automatically unpublished. Symbolic codes are generated using transliteration with mandatory uniqueness checks. Protection against parallel execution is implemented, ensuring that the background agent and manual synchronization do not conflict.
The settings page displays an operation log with rotation tracking and statistics for the last export, categorized by status: added, updated, or deactivated.
Connection setup requires entering the client_id, client_secret, and restaurant ID issued by UCS. API addresses can be overridden if necessary. The catalog configuration allows selection of the information block, price type, currency, and property codes to match your template. Synchronization settings let you define the agent interval, enable logging, and trigger manual execution.
Required components include the Information Blocks (iblock), Trade Catalog (catalog), and Highload Blocks (highloadblock) modules. An active UCS Delivery API account with access to the restaurant menu is also required.
Order transmission to rKeeper is handled by a separate solution named rKeeper: orders. The modules operate independently.
General iT can connect “Rkeeper (r_keeper) - menu synchronization”, install and configure the module, and make sure the integration works correctly.