SleekView Kanban for HotelDruid
SleekView Kanban reads HotelDruid's reservation table, groups every booking by its reservation status, and lets you drag a card from New to Confirmed, Checked-in, Checked-out, or Cancelled with the change written back to the HotelDruid database.
♾️ Lifetime License available
HotelDruid's planner hides today's actual stages
HotelDruid stores reservations in a normalised set of tables: a prenota row for each reservation with its own tipo_prenotazione status and linked rows for guest, room, and rate data. The plugin's planner view shows a Gantt-style grid of nights, which is great for seeing occupancy but unhelpful for triage. You cannot see at a glance how many new requests are waiting on confirmation, how many guests still need to be checked in today, and how many checkouts are done.
SleekView Kanban reads the same HotelDruid tables, treats the reservation status as the natural axis to group by, and renders one column per value. Cards show the guest name, the room and rate, the check-in and check-out nights, the guest count, and the total. Filters can scope the board to a single property, room type, or arrival night so each role in the operation sees exactly what they need to act on.
Drag a card from New to Confirmed and SleekView writes the new status back through HotelDruid's reservation update path. Drag to Checked-in when the guest arrives and the room status updates in the planner. Drag to Cancelled and the cancellation flow runs, freeing inventory. Every write follows the same path HotelDruid's own admin uses, so reporting stays accurate.
Workflow
Build a HotelDruid kanban in four steps
Connect HotelDruid
Pick the reservation status field
Choose card fields and property filter
Enable drag-to-update writeback
Sample board
Sample HotelDruid reservations board
Comparison
HotelDruid planner vs SleekView Kanban
Default HotelDruid planner
- Gantt planner shows occupancy but hides reservation stage
- Status changes require opening each reservation form to edit
- No quick view of today's arrivals versus pending confirmations
- Multi-property filters exist but do not surface workload counts
- Cancelled reservations are visually indistinguishable on the planner
SleekView Kanban
- Group by HotelDruid's reservation status column on the reservations table
- Drag from New to Confirmed and the confirmation email fires
- Cards show guest, room, rate, check-in, check-out, and total
- Per-column counts reveal arrivals, in-house, and departures at a glance
- Custom status values your workflow plugins register render as columns
Features
What SleekView Kanban gives you for HotelDruid
Status-axis board
New, Confirmed, Checked-in, Checked-out, and Cancelled each get a column with a live count. Any custom status added through HotelDruid hooks or your own code appears the moment a reservation lands in it, so the board mirrors the real workflow.
Drag updates the reservation
Card writes go through HotelDruid's reservation update path, the same code your front-desk staff already use. Confirmation emails, inventory updates, and any third-party hooks fire exactly as if the change had been made in the planner directly.
Per-property pipelines
Save a board per property, room type, or arrival night. Front-desk staff at each property see only their own reservations, while a head-office board can drop the filter and show every property's workload on one screen.
Audience
Operations the board makes legible
Front-desk arrivals view
Run a board scoped to today's arrivals. Drag confirmed reservations to Checked-in as guests arrive, and the count of remaining arrivals at the top of the column gives the front desk a live progress bar.
Housekeeping departure queue
Run a board scoped to today's departures. Drag a reservation to Checked-out only after housekeeping has cleared the room, giving the planner a real-time view of room readiness without manual phone calls.
Confirmation queue
The New column is your unconfirmed pipeline. Work it down to zero each morning by calling or emailing the guest and dragging to Confirmed, or to Cancelled if they back out. The board doubles as a checklist.
The bigger picture
A property runs on stages, not a Gantt grid
HotelDruid's planner is excellent at showing you what rooms are sold on what nights. It is much less helpful at showing you what stage each reservation is in right now. A new reservation needs confirmation.
A confirmed reservation needs check-in. A checked-in guest needs to be marked checked-out when they leave. A cancelled reservation may need a refund and follow-up.
Those four verbs are the entire front-desk workflow, and the Gantt view buries them behind colours and icons that staff have to learn. A kanban turns the same data into four columns of cards, with a count on each so today's workload is obvious. The front desk sees that there are ten new requests still waiting and works them down.
Housekeeping sees that there are eight checkouts done and four still to confirm. Multi-property operators see four boards side by side on one screen. Drag becomes the verb that moves the work forward, and because the writes go through HotelDruid's own update path, the planner stays in perfect sync.
Questions
Common questions about SleekView Kanban for HotelDruid
The status values HotelDruid uses on the reservation table: New, Confirmed, Checked-in, Checked-out, and Cancelled. Any custom status registered through HotelDruid hooks or your own code appears as its own column the moment a reservation lands in it, with no manual configuration.
 Yes. SleekView writes through HotelDruid's reservation update path, which is the same code the planner uses when you change a status manually. Confirmation emails, inventory updates, and any third-party hooks fire normally.
 Yes. Save a board per property with a filter on the property column and SleekView only loads reservations in scope. Drags update only those records, so multi-property operators can give each front desk its own focused screen.
 It complements. The planner remains the right tool for seeing occupancy by night and by room, while the kanban is the right tool for seeing reservation stage. Most teams pin the kanban on a back-office monitor and keep the planner open for ad-hoc queries.
 Cancelling through SleekView calls the same hooks HotelDruid's planner uses, so room inventory is freed for the night range of the reservation. Any third-party channel manager integration listening to cancellations fires normally.
 Yes. Any field HotelDruid stores against the reservation can be added to the card, including guest email, phone, rate code, breakfast option, and any custom meta added by your own code. PII can be hidden for staff that do not need it.
 Yes. A reservation with multiple rooms renders as one card with each room listed in the meta. Filters scoped to a single room type only show reservations that include at least one room of that type, which keeps front-desk boards focused.
 Yes. SleekView reconciles state on a short interval, so a reservation confirmed through the portal or cancelled by an automated job moves to the new column on the next refresh. Optimistic drags revert with a clear message if they collide.
 Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout