Reven for restaurants — recommended implementation path

A restaurant uses the same modules as other businesses, but its operational centre is the shared menu and order pipeline. Do not create separate menus for the website, Kiosk and POS when they sell the same assortment.

Recommended set

1. Ordering + Menu — categories, products, prices, images, SKUs, modifiers, labels, pickup and delivery.
2. Orders + KDS — acceptance, promised time, preparation, ready state and completion.
3. Kiosk or POS — an additional channel using the same menu.
4. Loyalty and coupons — returning guests and promotional campaigns.
5. Vouchers — gift sales and optional payment/benefit in an order.

Configuration order

First create the location, menu, categories and preparation stations. Then add items, prices, SKUs, images and modifier groups. Set 15-minute capacity, base lead time, delivery zones, fees and order minimums. Publish the menu only after testing the basket for pickup, dine-in and every active delivery zone.

Choose the order-acceptance mode. Automatic acceptance reduces staff work but requires up-to-date availability and capacity. Manual mode lets staff confirm every paid order and provide a promised time.

Kiosk and devices

Test Kiosk on the target screen with the real connection, scanner, terminal and printer. Reven monitors device and job state, but the production terminal/fiscal driver must be part of the agreed implementation. For an ambiguous payment result, staff must not retry the charge without checking the provider reference.

A complete feature description is available in Restaurant Commerce. Record the customer scope in the solution specification.