Custom software · for restaurants, cafés and hospitality groups

Restaurant reservation system. Restaurant online ordering system

A restaurant reservation system takes bookings and holds tables. An online ordering system takes orders for pickup and delivery. Marketplaces do both for a commission, with your guests in their database. Amazing Soft, based in Bucharest since 2016, builds systems that run on your domain, with your guest list. The system is yours, not a marketplace’s. Our hospitality portfolio includes websites for Belviso and La Hambar. A single restaurant with standard service should buy a product.

The problem. The marketplace owns the guest relationship

A restaurant can depend on several outside systems: a reservations marketplace, delivery apps, a booking widget on the website and a point-of-sale system from another vendor. Each has its own fee, login and copy of your guest records. The marketplace knows who ate with you on Friday; you do not. The delivery app sets the commission and owns the customer relationship. You ask for a deposit on large Saturday bookings, a regular’s usual table or a tasting menu ordered two days ahead. You are told it is not possible, or it is on the roadmap.

Build or buy. Seven questions about your restaurant

A reservation product or marketplace is the right answer for most restaurants. These questions help you decide whether one fits or you have outgrown it. Count how many times the “Build your own” answer describes your restaurant.

A product or marketplace is enoughBuild your own
How many restaurants?One.Several, or one with multiple rooms, a terrace and a private dining room, each with its own rules.
How do you take bookings?Walk-ins and a website widget.Deposits for large parties, menus ordered in advance, events, a waiting list that texts guests and a regular’s usual table.
Where do online orders come from?You accept delivery apps and their commission.Orders come through your domain, for pickup or delivery by your drivers or a courier, without a commission per order.
Who owns the guest list?You accept that it lives in the marketplace.Visits, preferences, allergies, spending and consent records must be yours and usable for your own messages.
What else does the system need to connect to?Nothing.Your point-of-sale system, kitchen screens, accounting, payment provider and website.
What does the guest see?The marketplace’s page, with your competitors one tap away.Your booking and ordering process, on your domain and in your brand.
How long will you use it?A season or two.Years, through new openings and menu changes.

Three or more “Build your own” answers: a system of your own is worth a conversation. Fewer: use the product and keep this page for later.

Say you run restaurants and cafés. How shared reservations would work

Say you run two restaurants and a café under the same name, with a general manager and a head of reservations. Bookings would come through a marketplace, by phone and through a website widget, leaving three lists that never agree. Online orders would come through two delivery apps, each with its own tablet in the kitchen. Nobody would know which guests had visited all three venues.

Your own system would start with one guest list and one floor plan per venue. Guests would book on your domain, choosing a venue, date, party size and time. Tables of six or more would pay a deposit. The tasting menu would need to be chosen two days ahead. The head of reservations would see all three venues on one screen and move a table by dragging it. If a table of four canceled, the waiting list would receive a message, and the first to answer would get it.

Online ordering would run on the same domain. Guests would see a menu with photos and allergens, pickup slots by venue and delivery by your own driver or a courier you choose. Orders would print in the kitchen and appear in the point-of-sale system. Guests would receive a message when their order was ready. There would be no marketplace commission per order.

After service, the manager would see covers, no-shows, deposits kept, orders by venue and returning guests. A loyalty program, staff scheduling and inventory would stay outside the first version. They would come later or remain in products that already handle them well.

What the system must do. Six things

01

Take a booking on a phone

The guest enters the venue, date, party size, time, name and phone number. No account is needed for the first booking.

02

Know the floor plan

Tables, rooms and the terrace have defined capacities, seating durations and rules for joining tables. The system offers only what actually fits.

03

Require a deposit when it matters

Deposit rules depend on party size, day or event. Deposits are taken online and kept or refunded under your rules.

04

Take orders without a marketplace commission

Pickup and delivery orders come through your domain, from a menu you control, and reach the kitchen and point-of-sale system.

05

Keep the guest's history

Visits across venues, preferences, allergies, spending and consent records remain yours and exportable, handled under your country’s data protection rules.

06

Report without a spreadsheet

Reports show covers by service, no-show rates, deposits, orders by channel and returning guests.

Build the part that is yours. Connect the rest

Nobody should rebuild payments, messaging or a point-of-sale system from scratch. Your own system handles the floor plan, booking rules, guest list and ordering process. It connects to the other services you use.

Who this suits. Restaurants with specific service requirements

Restaurant groups, restaurants with several rooms or a busy events calendar, cafés and bakeries taking pickup orders, and hotels with restaurants open to the public. We work with businesses in the UK, the US and Canada. A single restaurant with walk-ins and a booking widget should use a product.

If you need the website itself, with a menu and a Reserve button leading to your existing system, see our websites service.

For a guesthouse project, see website for a guesthouse.

How we work. Test during your restaurant's service

We look at how bookings and orders are actually handled at the host stand and in the kitchen. We prototype the system using situations from your own evenings and test it with your head of reservations. Then we build it in versions. The first version runs in one venue before it runs in all of them.

Our custom software service covers web applications, customer portals and system integrations, with details of what we deliver and how.

When not to build. Four cases

01

One restaurant, walk-ins and a booking widget

A product handles this well and costs less than any custom system.

02

You need it before the season starts next month

Your own system is built in versions over months.

03

The marketplace brings you guests

If most bookings come from its audience, keep it. Add your own system alongside it rather than replacing it.

04

Nobody owns it

A system needs one person at the restaurant who decides what changes. Without that person, use the product.

Questions. Short answers

A reservation system takes bookings, assigns tables and reminds guests. A marketplace does the same on its own site, for a fee or commission, and keeps guests in its database. Your own system runs on your domain, follows your rules and keeps the guest list yours. Many restaurants use both: the marketplace for new guests and their own system for repeat guests.

Yes. Orders come through your domain, for pickup or delivery by your drivers or a courier you choose. You pay the payment provider’s card fee and the courier. You do not pay a marketplace a percentage of every order.

We do not publish prices because two systems with the same screens can differ several times over in cost. The price depends on the number of venues, deposits and payments, online ordering, and connections to other systems. After the free 30-minute consultation, you receive the written proposal with a fixed price.

It can, where your point-of-sale and kitchen systems provide the necessary interface. We check that interface during the consultation.

Yes. Many restaurants keep the marketplace for new guests and use their own system for repeat guests and online orders. Where the marketplace provides an interface, its bookings can also appear on your floor plan.

You do. The data is stored on servers in the European Union by default, or in the region you request. You receive a data processing agreement in English. Consent stays with the guest record, and the full list is exportable at any time.

Who we are. Your development team in Bucharest

Amazing Soft SRL is a software company in Bucharest, Romania, founded in 2016. We work remotely with companies in the UK, the US and Canada, in English. Our data processing agreement is published on our legal page. Our time zone is EET, which overlaps most of the UK working day and the morning on the North American East Coast. The price is set after consultation, in the written proposal with a fixed price.

What we have built. Websites for Belviso and La Hambar

Belviso
A restaurant in Bucharest’s Old Town. Its website includes the menu and a booking page leading to the restaurant’s own reservation system. See this work →

La Hambar
A fine dining restaurant serving modern Romanian cuisine. Its website has been available in two languages since 2022 and includes the menu and a booking page leading to the restaurant’s own reservation system. See this work →

These portfolio projects are websites, not the reservation systems themselves.

Tell us how your restaurants run. Written proposal with a fixed price

We reply on the channel you wrote on to arrange the free 30-minute consultation. Afterward, you receive the written proposal with a fixed price. If the proposal suits you, we sign the contract and start work.