reservation system for
your business

Handle payments received in person on the spot too – mark a reservation as paid, generate an accounting document, and print it directly on a POS printer, or accept a card payment right away through a connected payment terminal.

The cash register feature lets you mark a reservation as paid directly in the administration, even when the payment took place outside the online payment gateway, for example in cash at reception. The system can then issue a corresponding accounting document for the payment received this way, respecting the configured document numbering, and so on.

For card payments, the system can also be connected to a payment terminal (SumUp, GP Tom, Comgate), which means a payment request can be sent to the terminal directly with a button in the reservation detail, and after a successful payment the system automatically marks the reservation as paid, creates the payment and document, and sends the customer a confirmation by e-mail, just like with payment via the online gateway.

A reservation in the reenio system doesn't have to mean just a booked slot in a calendar – it can also mean a ticket. It's just a different way of looking at what you're offering customers, what they're buying, and how the whole process then unfolds.

Every reservation carries everything you'd expect from a ticket – a unique code, a QR code for quick check-in, and information about the time and exactly what it can be used for. From this perspective, selling tickets is a fundamental way of using the reservation system. A ticket is often understood as a document that, for example, matches the visual identity of an event and also contains additional information. All of this can also be provided in the reenio system, where you can create your own design for the reservation confirmation = the look and content of the ticket.

The customer receives their ticket by e-mail right after payment, can save it to their Apple or Google Wallet, and you simply scan it with the mobile app at the entrance. If you want to sell tickets for events, it's really nothing more than a reservation with online payment and a custom confirmation design.

Tailor the reservation system to your business – whether you run a sports facility, a beauty salon, a rental business, or organize educational courses, the system can flexibly respond to the various needs and ideas linked to your particular type of business. Of course, it's still a universal cloud system rather than a custom-built solution, so some very specific ideas about how it should work or look might not actually be achievable.

The system offers a wide range of settings that make it easier to tailor booking to your specific customers and business. The foundation of this flexibility is the different event types (Full single event, Intervals, Full sequence, Any time, Multi-day, Coupon, Seat reservation), from which you can choose the most suitable one – from one-off workshops, through hourly rentals of sports facilities, to multi-day stays or selling event tickets.

Building on this foundation is a whole range of further settings that let you fine-tune the process further: custom booking forms for collecting specific data, various types of prices and discounts, online payments and payment by credit, reservation approval, waiting lists, collision protection between resources, or automated communication using system and custom messages. Thanks to user roles, you can also involve your whole team with correctly set permissions, and connect the reservation system to other systems as needed via the API or webhooks.

So the system grows together with your business – from a simple setup with minimal configuration, all the way to a comprehensive solution using most of the available features at once.

Collect the documents you need from customers directly during the booking process – consents, confirmations, photos, or other files, which you'll always have on hand for a specific reservation or customer. Similarly, you can also store documents for a specific customer and have a complete profile with their history.

The storage feature lets customers upload, and the system store, files linked to a specific reservation or customer profile. Typical uses include various confirmations, powers of attorney, photos, or copies of documents needed to provide the service – anything that makes communication and the delivery of the service itself easier, because you already have the documents available at the time of booking.

File uploads are added to the booking form using custom forms as a separate form field. A file can also be collected during the customer registration process, through a similar extension of the registration form. Another option is managing files directly in the administration, where you can typically work with them within a specific customer's detail page.

Run your reservation system in compliance with current legislation without having to track every change in this area yourself – we continuously add features that make it easier to meet your obligations. Of course, in this respect the reservation system is just a tool; legislative requirements and processes must always be grounded in the reality of your business, including outside the online world.

For example, as part of GDPR, the reenio system lets you set up automatic deletion of personal data after a chosen period, or keeps track of customer requests to have their personal data deleted. You can also define your own consents that go beyond the defined legitimate interest, and use them as the basis for, for example, sending marketing communications only to customers who have given direct consent for that.

In response to ongoing changes in legislation and amendments to laws, new features have appeared in the reenio system to make it easier to meet the requirements of the so-called "button law", the requirement for easy withdrawal from a contract, or the ability to report illegal content on the reservation page.

Give customers the ability to choose a specific spot directly on a map of a hall, restaurant, or car park – whether for the entire event, or just a selected time period.

This event type lets you create a map of specific places and other elements, from which the customer chooses for themselves where they want to sit, stand, park a car, and so on. There are then two ways to book: either for the whole event at once (a classic ticket sale for an event with a specific seat), or for any time period, where the customer chooses a specific time from and to together with a place (e.g. booking a table in a restaurant or a parking spot). It's suitable for concerts, balls, theatres, cinemas, restaurants, room rentals, shared offices, or parking spaces.

A strong feature of this event type is also its pricing, where the price depends on the category of the place on the map, to which price variants or conditional prices can also be added. Combined with generating a separate reservation code for each booked place, a separate ticket is then always created for each place, labelled with its specific location on the map, so individual attendees can easily be checked in separately.

Unlike other event types, the Coupon event type doesn't force the customer to choose a specific date and time to use the reserved services. The reservation only tells them the period during which they can use the service. That's exactly why this event type isn't suitable for services limited by capacity or a specific time – it doesn't let you set an overall capacity, because it isn't known in advance exactly when the customer will use their reservation.

This event type, or rather these reservations, are suitable anywhere you want to sell your services (typically in the form of tickets) while it doesn't much matter exactly when customers arrive, or what the limiting capacity is. Typical uses therefore include various exhibitions, zoos, historical sites, or various forms of access passes.

Offer loyal customers a more convenient way to pay for repeat visits – a punch card for a set number of visits or value, or top-up customer credit.

The reenio system offers several ways to let customers pay for reservations based on a previously prepaid value, instead of individual direct payments.

Punch cards work as a special type of coupon with a set number of visits or a gradually drawn-down amount (credit-based punch card). Applying the punch card code adjusts the reservation price accordingly, either by subtracting a defined amount or applying a discount of up to 100%. These codes don't have to be tied to a specific registered customer account, so they can be used easily and flexibly. They can also be restricted to specific events, so you clearly define which offered activities a punch card can be used for and which not.

Customer credit, on the other hand, works as a virtual wallet linked to a registered and logged-in customer account. A customer can top up their credit themselves online via a payment gateway (potentially with a bonus), or you can top it up manually in the administration, for example when paying in cash at reception. A credit wallet can in principle also have an expiration set.

Both solutions can be used effectively together with online payments, where the whole process of purchasing punch cards or credit can be fully automated. There are many possibilities, and it always depends on your specific settings and how you think through how and under what rules these customer-loyalty tools will work for your particular type of business.

Offer customers a classic bank transfer payment option too, for cases where you don't need instant confirmation – ideal for reservations made well in advance.

Bank transfer payment in the reenio system is especially useful where the deadline for mandatory payment of a reservation is three days or more, or where payment isn't a condition for the reservation to be created at all. The advantage of this approach is that everything happens purely within the reservation system and the bank, without needing an online payment gateway set up. Another advantage is lower costs for processing payments. The downside, on the other hand, is that checking, synchronizing, and the speed of payments is more complex.

The system provides the customer with the payment details (account number, amount, variable symbol – also in the form of a popular payment QR code) needed to send the payment, and based on the variable symbol, the payment can then be traced and matched to a specific reservation or, in the case of gift coupons, a purchase. Matching can be done manually directly in the administration, or automatically – you just need to set up your supported bank to send notifications of incoming payments to a unique e-mail address. As soon as such a notification arrives from the bank, the system matches the payment based on the variable symbol and marks the reservation as paid itself.

Bank transfer is usually also available as one of the methods within the online payment gateway, though in that case enabling it is more of a complication, since it combines completely different payment methods into a single solution. As with other payment methods, the system automatically issues and sends the customer the relevant accounting document the moment the payment is matched.

Let the reservation system automatically make sure you never have two reservations overlapping at the same time if they use the same resource. Thanks to collision protection, there's no problem creating a complex range of events and services while still ensuring effective management of reservations for the same time slot.

Resources (service, employee, place) in the reenio system serve not only as the informational basis for the range of events, their filtering, and navigation, but also as an important element in automating the whole reservation process. Thanks to collision protection, the system automatically evaluates whether a reservation can be created at a given time, or whether it would cause a collision due to the resources involved already being booked – for example, if a sauna would be booked at the same time by another reservation, but for a different service.

If you want to make reservations really efficiently, and want to offer your customers different options, services, prices, etc., then collision protection is definitely a feature worth understanding and getting right. For example, if you run a tire shop and car wash with 3 bays, thanks to collision protection you can offer different services (events) across the bays, and if a customer books one service in bay 1, no other reservation for the same time can be created for bay 1. And the reservation system takes care of exactly this automatically.

Collision protection is available for almost all event types. It cannot be used to protect against collisions at the level of individual seats in a seat map.

Don't let customers create reservations online without your say – decide for yourself which reservation to approve. This is useful anywhere a booking request needs to be reviewed first, before you actually assign the customer an event.

The reservation approval feature changes the standard process so that a reservation created by a customer isn't approved right away, but first waits for your approval in the administration. After creating a reservation, the customer is informed that their reservation is awaiting approval, and receives final confirmation (and, if applicable, a prompt for online payment) only once you approve, or alternatively reject, the reservation.

This is useful anywhere you want full control over how events are filled – for example for individual consultations, where you first need to check whether a time slot is suitable, for services that require related preparations to be arranged, or anywhere you want to prevent random or unsuitable reservations.

Don't lose customers just because an event is already fully booked – let them sign up for a waiting list and automatically notify them as soon as a place opens up for them because an earlier customer cancels their reservation.

The waiting list feature lets customers express interest in a reservation even when an event no longer has free capacity. A reservation doesn't get created for them at that point yet – the system simply records their interest, including their details. As soon as the corresponding capacity becomes available (e.g. another customer cancels their reservation), the system automatically picks a waiting-list candidate from the queue based on order and capacity and creates a standard reservation for them with everything that entails – sending a confirmation, a possible payment request, cancellation rules, and so on. If a candidate on the waiting list doesn't get a spot, the system no longer notifies them any further.

This feature is only available for the Full single event type and must first be enabled and configured for the specific event.