SleekView Kanban for EventON
EventON stores every booking as an evo_bookings post with statuses like evo_pending, evo_completed, evo_attended, and evo_cancelled. SleekView Kanban reads those rows and renders one card per booking, grouped by status into columns you drag between to update the source.
♾️ Lifetime License available
Read EventON bookings as a board, not a long admin list
EventON writes every booking as a post. Each row lives in evo_bookings with a post_status like evo_pending, evo_completed, evo_attended, or evo_cancelled, plus booking meta keys for guest name, event ID, ticket variation, and price. The default Bookings screen shows those rows as a list filtered per event, with status as a column label and check-in on a separate ticket screen.
SleekView Kanban reads the same evo_bookings posts and groups them by status into columns. The board shows Pending, Completed, Attended, and Cancelled with a count at the top of each column and a card per booking. Cards carry guest name, event title, ticket variation, and the booking total from the linked WooCommerce order when EventON is wired to Woo through the RSVP addon. The front of the card holds the fields organisers actually need to move the row forward.
Dragging writes back to the source row. Moving a card from Pending to Completed flips post_status to evo_completed and triggers the configured EventON email, moving to Attended writes the attendance meta and the timestamp, and moving to Cancelled reverses the linked Woo order through the standard hook. Group bookings count as one card with a guest count on the meta line so the organiser sees the headcount without opening the row.
Workflow
From evo_bookings to a kanban board in four steps
Connect SleekView to EventON
Pick the status column to group by
Choose what shows on each card
Enable drag to update status
Sample board
Sample EventON bookings board
Comparison
Default EventON bookings vs SleekView Kanban
Default EventON bookings list
- Bookings screen is a list sorted by date with status as a column label not a grouping
- Attendance and check-in live in a separate ticket screen on the EventON admin
- No way to drag a booking from Pending to Completed without opening the row first
- Group bookings show as a single line with the guest count hidden behind a click
- Custom statuses from EventON addons are not surfaced anywhere in the bookings UI
SleekView Kanban
-
Groups
evo_bookingsposts on one board by the livepost_statusvalue -
Drag to Completed flips
post_statustoevo_completedand sends the booking email - Drag to Attended writes the attendance meta and the timestamp on the booking row
- Group bookings show guest count on the card meta so headcounts are visible
- Audit log captures every drag with user, previous status, and time for clean reconciliation
Features
What SleekView Kanban gives you for EventON
Booking cards on the board
One card per evo_bookings row with guest name, event title, ticket variation, and total, plus the guest count for group bookings so the headcount sits on the card not behind a row click.
Drag updates the source row
Each drag writes back to post_status, the attendance meta, or the linked Woo order, so the EventON Bookings screen and the linked Woo order reflect the same state the board shows.
Role-scoped views
Save boards per role so the organiser sees Pending and Completed, door staff see Completed and Attended, and finance gets a focused view on Cancelled bookings only.
Audience
Who runs EventON bookings on a board
Event organisers
Approve pending bookings in batches, watch completed counts rise across the week, and clear cancellations without switching between screens.
On-site door staff
Open the board on a tablet, scan the booking code, drag the card to Attended. The EventON ticket screen reads the same attendance meta on the next refresh.
Finance teams
Work the Cancelled column at the end of the day to reverse linked Woo orders and clear refund tickets in a single pass instead of jumping between screens.
The bigger picture
EventON bookings live a life, give them a board
An EventON booking moves through several distinct states. A guest fills the RSVP form and a row appears in evo_bookings as evo_pending. The organiser or the payment gateway flips the post_status to evo_completed, the door scan writes the attendance meta, and a cancellation either reverses the linked Woo order or moves the row to evo_cancelled.
The default reading surface is still a list per event, with status as a column label and attendance on a different ticket screen, so an organiser running three events at once spends most of the time switching tabs. SleekView Kanban reads the same evo_bookings posts and lays them out as Pending, Completed, Attended, and Cancelled with counts at the top and door-ready cards in each column. Approving a batch is a group drag.
Marking attendance is a drag at the door. Cancelling a group booking refunds the linked Woo order in the same drop. The EventON Bookings screen, the ticket screen, and the linked Woo order all reflect the change because SleekView writes to the source row, not to a parallel state.
Questions
Common questions about SleekView Kanban for EventON
Yes. SleekView reads evo_bookings regardless of which EventON addon created the row. RSVP-only events show no order total on the card and Ticket events show the linked Woo order total. Both group into the same board grouped by post_status.
Yes. Dropping a card on Completed sets post_status to evo_completed through the WordPress post update API, so the EventON Bookings screen and the configured emails behave exactly as they would if the change had been made from the row itself.
Yes. When the booking has a linked Woo order, dropping the card on Cancelled reverses the order through the standard WooCommerce refund hook. Stock and emails behave as if the refund had been issued from the orders screen, with the audit log recording the change.
Yes. SleekView reads distinct values from the grouping column at render time, so any custom post_status registered by an addon appears next to the built-in EventON ones. You can hide a column from the view without removing the status from the database.
Yes. A group booking is one row in evo_bookings with a guest count meta, so it shows as one card with the guest count on the meta line. Dragging the card moves the whole party at once, which mirrors how EventON itself treats the booking.
Yes. SleekView saved views support filters per event ID, category, or organiser, so a venue with three live events can run three boards. Counts at the top of each column reflect the filter, not the global total, which keeps the screen honest about scope.
Cards show the EventON booking code and the QR ticket ID when the addon is installed. Scanning the code with a handheld scanner navigates to the card, and dragging it to Attended writes the same attendance meta the EventON ticket screen writes, so the totals match across views.
Yes. Every drag writes a row to the SleekView activity log with the booking ID, the previous status, the new status, the user, and the time. Filtering by event and by date gives a clean record of who confirmed, who checked in, and who cancelled, which makes postmortem questions a single search.
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