Reven Help
How can we help?
Find a feature, setting or instruction. Results include only approved customer-facing materials.
Reven assistant · beta
Ask about a setting or feature
The assistant answers only from verified public articles and always shows its sources.
Your question is used only to prepare this response and is not stored by this feature. Do not include passwords, tokens or card data.
Featured articles
13 articles
Reven solution specification and access scope
Reven is a modular platform for service businesses and restaurants. It combines the sale and operation of vouchers, deposits, waitlists, bookings, loyalty programmes and coupons and, for restaurants, a shared menu, Ordering, KDS, Kiosk and POS.
Read article →Getting started with Reven
The safest order is to confirm the scope, configure shared business data, prepare one module, test it from both the customer and staff perspectives, and only then publish the link.
Read article →Reven configuration map
This table answers “where do I change this?” Item visibility depends on the active module and the user's role.
Read article →Booking — services, specialists and appointments
Booking lets a customer choose a service, specialist and available time. The business manages appointments in the dashboard together with deposit information and waitlist requests.
Read article →Deposits — prepayment configuration and operation
A deposit is a prepayment associated with a planned service or reservation. Reven provides a public payment page, quick links created by staff, a deposit list, statuses, operation history and controlled refunds.
Read article →Loyalty and coupons — customer retention and campaigns
Loyalty is an ongoing customer relationship programme, while a coupon is a separate, limited campaign. Both products can be scanned through the shared staff screen, but they have different balances, rules and histories.
Read article →Restaurant Commerce — Menu, Ordering, KDS, Kiosk and POS
Reven Ordering, KDS, Kiosk and POS use one menu, the same pricing rules and a shared order record. As a result, an item that is sold out or changed in the menu should not require a manual edit in every channel.
Read article →Reven for beauty and services — recommended implementation path
For a salon, clinic or service business, the main operating axis is the service offer, specialist availability and protection of reservations. The modules are shared with the rest of the platform; this guide shows only the recommended combination.
Read article →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.
Read article →Reven glossary
This glossary explains the names of modules, statuses and operations used in the Reven dashboard, implementation materials and support conversations.
Read article →Reven platform — profile, payments, team and shared settings
The Reven dashboard is contextual: its menu depends on the active products, selected business and permissions of the signed-in user. A user with access to multiple businesses can switch context; before every financial operation, they should check the name of the current business.
Read article →Vouchers — sale, issue and redemption
The module covers public sales, manual issuing, delivery, balance checks, redemption, voiding and operation history. Every voucher has a code, status, initial value, remaining balance, redemption rules and a snapshot of the offer at the time of purchase.
Read article →Waitlist — collecting and handling requests
Waitlist collects requests from people for whom no place or time is currently available. It is not a confirmed booking. The business contacts the customer and changes the request status in the dashboard.
Read article →