Live service pause
For when you need to close online reservations on a specific day at a specific time, without touching the calendar or your permanent settings.
The problem it solves
- "I don't want any more lunch reservations today because walk-ins will fill up."
- "Close Sunday dinner, we have a private event."
- "Pause tomorrow's breakfast, the cook is out sick."
The service pause is temporary and per-service: it blocks only the affected slot on a specific date and reopens by itself when the day changes. You don't touch opening_intervals or booking_settings.
How to activate it
In /app/reservas → "Pause online reservations" button (top right corner).
A dialog opens with two options:
Quick shortcuts
If you have services configured (breakfast/lunch/dinner), preset buttons appear based on your real schedule:
Lunch - today Dinner - today Breakfast - tomorrow
Lunch - tomorrow Dinner - tomorrow
One click and the pause is active.
Custom
When you need a different date or service:
- Day: date picker (any future date).
- Service: breakfast, lunch, dinner, all day.
- Reason (optional, internal only): "walk-ins coming", "private event", "no staff".
What the public customer sees
On /r/:slug, when every service for the day is paused:
Fully booked for today. We'll see you without a reservation - drop in whenever.
[Call the restaurant - +34 ...]
If only lunch is paused, dinner slots still appear normally.
Service pause vs extended closure
| Service pause | Global toggle (/app/local) | |
|---|---|---|
| Where it activates | /app/reservas | Live service |
| Scope | Per day and service | The whole site, indefinitely |
| Expires | Yes, when the day changes | No, you have to resume manually |
| Use case | We're not taking lunch today; tomorrow we are | Vacation, renovation, extended closure |
The two coexist. To "close lunch today" use a pause; to "we're closed two weeks in August" use the global toggle.
The team can still create internal reservations
The pause only blocks the public channel (web + embed). The backoffice can still:
- Create manual reservations.
- Register walk-ins.
- Move existing reservations between tables.
Resume
You have two places:
Banner in /app/reservas
If a pause is active today, an amber banner shows at the top:
Online reservations paused today: lunch, dinner. [Resume]
List of active pauses
Below the "Pause" button there's a section with every active pause (today and future), each with its own Resume button.
Automatic resume
If you do nothing, the pause expires by itself when the day changes. At 00:00 the next day, online reservations come back without intervention.
Confirmed reservations are not cancelled
A pause only blocks new reservations. If Javier already has a reservation for lunch today at 14:00:
- His reservation stays on the calendar.
- He gets the confirmation and reminder.
- It's not cancelled or modified.
The pause is forward-looking only.
Real-life case: chaotic Friday
It's 18:00 on Friday. 50 people are coming with no reservation because of an event in the square, the dining room is full.
- You open
/app/reservas. - Click Pause online reservations → shortcut Dinner - today.
- The website no longer accepts new dinner bookings. Walk-ins come in without digital pressure.
- At 22:00 you resume (banner) or you go home: tomorrow at 00:00 it reopens by itself.
Pinche can do it too
If you have Pinche, just type:
"Close dinner reservations for today"
Pinche asks for confirmation and executes. To resume: "reopen dinner".