✨ 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 Pinpoint Booking System

SleekView Kanban reads the Pinpoint dopbsp_reservations table, groups every reservation by its status, and lets you drag a card from Pending Approval to Approved, Paid, or Cancelled with the new status written straight back to Pinpoint.

♾️ Lifetime License available

SleekView Kanban board for Pinpoint Booking System

Pinpoint reservations get buried in the calendar grid

Pinpoint Booking System stores every reservation as a row in dopbsp_reservations with a status column whose values are approved, pending, paid, cancelled, or rejected. The admin shows those reservations on a calendar grid, which is great for spotting an open weekend but hopeless for tracking which of last week's pending requests still owe you an answer or which approved bookings have actually paid.

SleekView Kanban reads the same dopbsp_reservations table and treats the status field as the natural axis to group by. Each card surfaces the guest name, the calendar or property name, the check-in date, the nights count, and the total. Counts at the top of every column update live as you drag, so the pending stack and the unpaid stack read as outstanding work rather than as numbers buried in a report.

Drag a card from Pending to Approved and SleekView calls the same Pinpoint update path the admin dropdown uses, which fires the approval email, the iCal export refresh, and any webhook you have hooked into the lifecycle. Drag to Cancelled and the linked payment record stays consistent because the write goes through the plugin's own functions, not a raw SQL update. Multi-calendar accounts can scope a board per calendar so each property manager only writes to their own rows.

Workflow

Build a Pinpoint kanban in four steps

1

Connect Pinpoint Booking System

Point SleekView at the Pinpoint data source. It discovers the dopbsp_reservations table, the linked calendar definitions, and any custom form fields you collect at booking time without manual mapping or CSV exports.
2

Pick the reservation status column

Choose Pinpoint's status field as the group-by axis. SleekView builds one column per distinct value, so Approved, Pending, Paid, Cancelled, and Rejected each become their own stack with a live count.
3

Choose what shows on each card

Pick the fields door staff and the owner actually scan: guest name, calendar, check-in, nights, and total. SleekView formats dates and currency and resolves the calendar IDs into readable names automatically.
4

Enable drag-and-drop status writes

Turn on writeback so dragging a card calls Pinpoint's update functions. Approval emails, iCal pushes, and any webhooks fire as if you had clicked the status dropdown, with optional confirmation on destructive drags like Cancelled.

Sample board

Sample Pinpoint Booking System reservations board

A live preview of how your Pinpoint reservations group into status columns, with cards showing guest, calendar, check-in date, nights, and total.
Pending
14
Cottage A, check-in Apr 12
Helena Voss, 3 nights
Studio loft, check-in Apr 18
Marco Bianchi, 240.00 EUR
Cabin 7, check-in May 02
Aiko Tanaka, 5 nights
Approved
38
Cottage B, check-in Apr 14
Daniel Park, deposit paid
Lake house, check-in May 09
Priya Shah, 6 nights
Studio loft, check-in May 16
Olivia Reed, 320.00 EUR
Paid
92
Cabin 7, check-in Apr 04
Karim Hassan, 480.00 EUR
Cottage A, check-in Apr 21
Felix Mueller, 7 nights
Lake house, check-in Apr 28
Lena Kowalski, 910.00 EUR
Cancelled
11
Studio loft, check-in Apr 10
Guest cancelled, refund issued
Cottage B, check-in Apr 24
Late cancel fee kept, 120.00 EUR
Cabin 7, check-in May 11
Owner cancelled, weather

Comparison

Pinpoint calendar view vs SleekView Kanban

Default Pinpoint admin

  • Calendar grid shows availability well but hides which reservations need a decision today
  • Status changes require opening each reservation and editing a dropdown one by one
  • No glance count of how many pending requests are sitting in the queue right now
  • Switching between approved and unpaid stacks means re-filtering the calendar view
  • Bulk approvals are not exposed in the default admin so you click through one record at a time

SleekView Kanban

  • Groups Pinpoint status values into one column per stage with live counts at the top
  • Drag from pending to approved writes through Pinpoint's own update path
  • Cards show guest, calendar, check-in date, nights, and total in a single readable tile
  • Approval emails, iCal exports, and webhooks fire exactly as the calendar dropdown would
  • Per-calendar saved views give each property manager a focused board for their rows

Features

What SleekView Kanban gives you for Pinpoint Booking System

Group by any Pinpoint status

Use the built-in Pinpoint statuses or any extra value your workflow has added to the status column. SleekView lists every distinct value present in the data and renders one board column per status with counts that update as you drag.

Drag to change reservation status

Move a card from Pending to Approved and SleekView calls the same Pinpoint update functions the admin dropdown uses. Approval emails, iCal refreshes, and any deposit hooks fire so nothing about the lifecycle silently breaks.

Configurable card fields

Pick which reservation fields land on the card front: guest, calendar, check-in date, nights, total, payment method, or any custom form field you collect at booking time. Dates and currency format themselves automatically.

Audience

Workflows the kanban view unlocks for Pinpoint

Daily approval queue

Start each morning on the Pending column, scan the new requests, drag the ones that fit into Approved. The board doubles as your shift checklist and the email fires automatically.

Deposit chasing

Filter to the Approved column to see exactly which reservations still owe a deposit, drag to Paid once the payment link resolves, and let the rest age into a follow-up flag without manually tracking emails.

Multi-property handoffs

Save one board per calendar so each property manager only sees and writes to the rows for their cottage, cabin, or studio. The owner keeps an all-properties board for the daily standup.

The bigger picture

A calendar shows availability, a board shows the work

Pinpoint Booking System is excellent at the question that calendars answer well: is this room free on these nights. It is less useful for the question that runs a small rental operation, which is what do I still owe somebody. Approvals queue up in an email inbox, deposit chasing slips into a spreadsheet, and cancellations come in as phone calls that have to be reflected in three places at once.

The board view changes that by making the only state that matters, the reservation status, the primary axis of the screen. You can see at a glance whether you are caught up on approvals, whether yesterday's approved rooms actually paid, and whether any cancellations need a refund. Cards make individual reservations legible at the level of guest, calendar, dates, and money, which is exactly what owners and front-desk staff need.

Drag is the natural verb for moving something from one stage to the next, and because SleekView writes through Pinpoint's own functions, every drag still triggers the approval emails, the iCal refreshes, and the deposit hooks you already configured. Calendar view and board view stop being a tradeoff and start being two reading surfaces over the same data.

Questions

Common questions about SleekView Kanban for Pinpoint Booking System

Every value Pinpoint writes to the status column: Approved, Pending, Paid, Cancelled, and Rejected. Any custom status you have added through a snippet or an extension appears as its own column the moment a reservation lands in it, with no manual mapping required.

 

Yes. SleekView calls the same Pinpoint update functions the admin dropdown uses, so the row in dopbsp_reservations changes, approval emails fire, iCal exports refresh, and any deposit or webhook hooks you have configured trigger exactly as if you had used the standard interface.

 

SleekView offers an optional confirmation prompt on drags into destructive columns like Cancelled, and any drag can be reverted by dragging back. The actual refund flow still runs through Pinpoint, so any payment integration handles the money side the same way it would from the admin.

 

Yes. SleekView reads reservation state on a short interval and reconciles drags against the live record, so if a colleague has already approved a request on their screen, you see the new state before your drag conflicts. Optimistic updates revert cleanly when a write is rejected.

 

The primary grouping is status, but each card surfaces the calendar name, check-in date, and nights, which gives you the same visibility you would get from the calendar without leaving the board. Saved filters scope a board to a single calendar when a property manager only needs their own.

 

Yes. Pinpoint extensions hook into the same status lifecycle the board writes to, so any payment integration, calendar sync, or notification add-on you have installed continues to run on drags. SleekView never bypasses Pinpoint's own functions, so plugin behaviour stays consistent.

 

Yes. Save a filtered view per calendar and SleekView renders one board per saved view. Column counts and writes are scoped to the rows in that view, so each property manager has a focused screen while the owner can switch to an all-properties board for the standup.

 

Yes. SleekView only loads cards for the columns currently visible and paginates older reservations into a scroll-on-demand tail. Indexing on the status column keeps group counts cheap even for accounts with several years of bookings in the table.

 

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