Create your account
An account is created for the organisation, then invited members join it.
Guides, module documentation, integrations and answers for restaurants, partners and integrators.
This documentation is public. It is not the internal technical documentation of the platform.
DOCUMENTATION CENTER™
Documentation Center
Getting started with taevio.
Guides
Discover the module
Frequently asked questions
The path followed by a new establishment, from account to first service.
An account is created for the organisation, then invited members join it.
Each establishment carries its own opening hours, rooms and configuration.
Access is granted role by role, with no shared account.
Menus, items, allergens and prices are prepared before the first service.
Reservations, floor plan and orders are used together from day one.
The exact steps depend on the establishment configuration and the subscribed plan.
The operational core: reservations, tables, orders and kitchen.
Recognising a guest and respecting confirmed preferences.
Assistants that support the team, always under human supervision.
Phone, email, chat, QR code, SMS and WhatsApp in one history.
Payments, invoicing, subscriptions and coupons.
Connecting taevio. to the tools already used by the establishment.
Task-based walkthroughs for the daily operation of an establishment.
Create, move, confirm and close a reservation with its full history.
Rooms, tables and capacities are described before assignment.
An order moves through explicit states from opening to payment.
Preparation is followed live, with no paper ticket.
Recognition, preferences and history are used with consent.
Reports describe the activity of an establishment over a period.
Guides describe the platform behaviour, not a contractual commitment.
The public API is being prepared.
The public API is not available yet. No endpoint, key or contract is published at this stage.
The public API is not published yet.
The first scope will cover reservations, orders and guests.
Access will be authenticated and scoped per establishment.
Integrators can contact the team to prepare a connection.
Answers about this public documentation.
Restaurants, partners and integrators. It is not the internal technical documentation.
Content is reviewed and republished as the platform evolves.
Documentation follows the platform languages: Portuguese, French and English.
The support level depends on the subscribed plan.
The public API is being prepared; the section above describes its status.
The taevio. team answers product, integration and contractual questions.
Our team supports restaurants, partners and integrators.