✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for Vik Booking

Vik Booking keeps reservations in custom database tables. SleekView Kanban reads those tables directly, groups bookings by status, and lets staff drag cards between pending, confirmed, checked-in, and cancelled to update the underlying reservation record.

♾️ Lifetime License available

SleekView Kanban board for Vik Booking

Vik Booking reservations as cards, not table rows

Vik Booking stores reservations in its own custom database tables, with the vikbooking_orders table holding the booking ID, guest name, total, dates, and status. The status column tracks pending, confirmed, checked-in, and cancelled as the four core states the plugin supports across its hotel and venue setups out of the box.

SleekView Kanban points at vikbooking_orders and renders one card per reservation. Cards group into four columns by status, and drag-and-drop updates the status column directly through the WordPress REST API endpoint that Vik Booking exposes for its own admin screens. The change is immediate, single source of truth, and respects existing role checks.

Card fronts show guest name, dates, and room or service. Filter the board by service, by room, or by arrival window, save filtered views as URLs, and pin different boards to the front desk and the housekeeping office. Status writes inherit the plugin's role mapping, so no extra permission setup is required for staff.

Workflow

Vik Booking to kanban in four moves

1

Pick Vik Booking as the data source

Pick Vik Booking from the SleekView source picker. The connection reads the vikbooking_orders table directly, surfaces every column the plugin uses, and stays live without any extra credentials or developer setup, because the plugin already runs inside the same WordPress install.
2

Group cards by reservation status

Set status as the kanban column field. SleekView reads the distinct values and renders four columns: pending, confirmed, checked-in, and cancelled. Each column can be renamed for display, reordered to fit the team's flow, and recolored to match the front desk visual language.
3

Lay out the card content

Drag the guest name and the check-in date into the card front. Add the room name as the second line and the total amount as the third. The card editor previews live Vik Booking data so you can confirm long guest names and long room names do not break the layout before going live.
4

Drag to update the reservation row

When a staff member drags a card from pending to confirmed, SleekView writes the new value to the status column via the Vik Booking REST endpoint. The plugin reads the new value on its next render, and the front desk sees the reservation in the right state without any second sync layer.

Sample board

Vik Booking reservations grouped by status

Pending requests stack on the left, confirmed arrivals sit in the middle, checked-in guests slide in next, and cancelled bookings sit on the right for occupancy reporting.
Pending
24
Three-night stay request
Guest Lucia Brand, 12-15 Jun
Double room with breakfast
Guest Mateo Rios, 13 Jun
Family suite request
Guest Ana Holst, 14-18 Jun
Confirmed
51
Standard double, two nights
Guest Ines Vega, 17-19 Jun
Junior suite with breakfast
Guest Olaf Reim, 18 Jun
Family room four nights
Guest Mira Tomas, 20-24 Jun
Checked-in
19
Long stay in deluxe suite
Guest Eli Ros, room 401
Standard double room stay
Guest Sven Vera, room 207
Honeymoon suite stay
Guest Lana Falk, room 510
Cancelled
10
Cancelled within policy window
Guest Ivana Vrba, refunded
Late cancellation with fee
Guest Karl Holm, fee charged
No-show on arrival night
Guest Yara Mira, flagged

Comparison

Vik Booking admin list vs SleekView Kanban

Vik Booking orders list

  • Default Vik Booking screen is a list of reservations with small status text in a sortable column
  • Status changes require clicking into the reservation, picking a state, and saving the row
  • No live count of reservations sitting in each state across upcoming arrivals and stays
  • Bulk actions cover delete and trash but not status transitions across many reservations at once
  • Filters do not persist across reloads, so front desk redoes the same scoping every morning

SleekView Kanban

  • Drag a card and the status column in vikbooking_orders updates in one move
  • Column counts double as a live occupancy gauge visible from across the front desk area
  • Filter on room or service and save the result as its own URL for per-team kanban boards
  • Cards surface guest, dates, and room together so triage takes one glance per row, not several
  • Inherits Vik Booking role and capability mapping, no extra permission layer to maintain

Features

What SleekView Kanban gives you for Vik Booking

Status columns mapped to Vik Booking states

SleekView reads every distinct value in the status column and surfaces them as kanban columns. Whether you use the four core states or have added a custom status through the Vik Booking developer hooks, the board renders them automatically and lets you choose which to display today.

Drag updates the reservation row

Every card move writes through the same REST endpoint that Vik Booking exposes for its own admin screens. There is no second data path, no sync layer, no risk of the kanban telling a different story than the orders list. One write, one source of truth, one consistent state.

Per-room or per-service saved boards

Add saved filters on room or on service term, then save each result as its own named board with its own URL. Pin one board per team so the front desk, housekeeping, and the manager office each see the slice of reservations that matters to their role during the day.

Audience

How venues use the Vik Booking kanban

Independent hotel front desk

Reception opens the board first thing, calls every pending reservation to confirm, and drags each one into confirmed as the call ends. Cards slide into checked-in as guests arrive. The team knows which guests are in the building and which are still en route without a second screen.

Housekeeping turn schedule

Housekeeping pins a board filtered to checked-in reservations sorted by room number. As they finish each room they drag the card into a custom turndown-complete column, which gives the manager a live view of how the cleaning schedule is progressing across all floors of the venue today.

Manager occupancy dashboard

The manager pins the full kanban to an office monitor and uses column counts as a live occupancy gauge. When confirmed grows faster than checked-in clears during peak season, they bring in extra staff or open more rooms before the queue at reception starts to build up.

The bigger picture

Why a kanban fits Vik Booking venues

Vik Booking is a comprehensive reservation engine that handles hotels, vacation rentals, and event venues with the same plugin core. The orders list table that ships with the plugin is built for record retrieval, which is the right shape for inspecting a single reservation but the wrong shape for running a busy shift. Reception staff need to triage pending requests, confirm upcoming stays, check guests in, and reconcile cancellations during a single day.

A list sorted by date does not show that flow. A kanban does. The pending column is the queue of requests that need a confirmation call.

The confirmed column is the arrivals coming over the next few days. The checked-in column is the guests in the building right now. The cancelled column is the capacity that has freed up.

Because SleekView writes directly to the same database column the plugin already uses, the kanban is not a parallel system. Every drag goes through the Vik Booking REST endpoint that powers the standard admin screens, so audit logs and capability checks behave the way they always did. Reception works the board, housekeeping works the board, and the manager reads column counts.

The kanban replaces the orders list as the screen that the whole venue team keeps open during a shift.

Questions

Common questions about SleekView Kanban for Vik Booking

Yes. SleekView reads from and writes to the vikbooking_orders table directly through the Vik Booking REST endpoint. Every card move updates the same status column the plugin uses for its own admin screens, so there is only one source of truth for every reservation in the system.

 

Yes. The board titles are display labels that SleekView stores separately from the actual status values. Rename pending to awaiting confirmation or checked-in to in residence, and the kanban uses your language while the underlying data continues to store the standard Vik Booking status values.

 

SleekView Kanban uses the same capability check that Vik Booking applies on its own edit screens. If a user can change a reservation through the plugin's admin, they can drag a card on the board. Users without edit rights see the board in read-only mode with drag handles hidden from view.

 

Yes. The card editor lets you pick any column from the vikbooking_orders table, including the room number, the rate plan, and the guest note field. A common layout shows guest and arrival date on the front, with room and rate on the second line and the note revealed on hover.

 

Yes. Reservations imported by the Vik Booking channel manager land in the same vikbooking_orders table that direct bookings use. The kanban renders them identically and lets you filter by source if you need separate boards for direct, OTA, and walk-in reservations across your front desk team.

 

Each reservation appears as a single card regardless of stay length, with the check-in and check-out dates surfaced in the card meta. If you need a per-night view, save a second board that groups by date instead of status. The same data feeds both views without any duplicate record creation.

 

Yes. SleekView reads every distinct value in the status column, so any custom status you have registered through the Vik Booking developer filters appears automatically as a new kanban column. Choose which columns to display on the active board and hide the rest without losing them from data.

 

The board uses optimistic updates with conflict detection. If two staff members drag the same card within the same second, SleekView resolves the conflict by accepting the first write and showing the second user a notice that the reservation has already moved. They can refresh and retry on the latest state.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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