Seasonal Floor Plans
Summer terrace. Winter hall. Plan both, switch automatically.
Your floor changes with the seasons. Summer means the terrace, the garden, the extra seating outside. Winter means the hall, the booths, tighter spacing inside. If your booking system only knows about "right now," every season change means a scramble to redraw tables — and a risk that online bookings clash with the new layout.
Reservation.Tools stores floor plans as schemas, each with its own start date, end date, name, and table arrangement. You design the summer plan in March and the winter plan in September. Both sit ready.
On the start date, the matching schema becomes active. Every reservation made while it's live is tied to its tables. Online availability, auto-assignment, and the floor-plan views all use the active plan.
For venues that also run themed nights or event layouts, you can keep plans as templates and spin them up on demand. One venue, many configurations, no last-minute panic.
Key benefits
No last-minute redraws
Plan your summer and winter layouts months ahead. The system switches on the right date without a manual step.
Online bookings always match the real floor
The active plan drives availability. Guests never book a table that doesn't exist this season.
Keep templates for events
Save a themed-night or private-event layout as a template. Reuse it without rebuilding from scratch.
Historical accuracy
Past reservations stay linked to the schema they were made under — so reports reflect how the venue actually looked.
Schedule weeks ahead
Start and end dates mean you can line up a whole year of layouts and forget about them until the next design change.
How it works
- 01
Create a schema
Add a new floor plan with a name, start date, and end date.
- 02
Design the layout
Drag tables, group them into areas, upload a background image if you have one.
- 03
Set it as default when needed
Mark a schema as default so it's the one the booking engine uses when no other plan is active.
- 04
Let it activate automatically
On the start date the schema becomes active. Previous one becomes inactive at its end date.
- 05
Or save as a template
For one-off layouts (weddings, private buyouts), keep a schema as a template and activate it only when you need it.
App Store
Google Play
Web AppHave questions?