✨ 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 for FooEvents: tickets and attendees as tables

FooEvents bolts onto WooCommerce so each ticket is a customer order line backed by attendee meta. SleekView turns that scattered structure into a cross-event grid that door staff and finance can both work from.

♾️ Lifetime License available

SleekView table view for FooEvents

Tickets, attendees, and orders side by side

FooEvents stores each event as a WooCommerce product, and every ticket as an attendee record tied back to the order line item. The ticket meta lives on order item meta, the attendee details live on a separate post type, and the dashboard splits the operational picture across the WooCommerce orders screen and the FooEvents check-in tools. The data is correct; the workflow is fragmented.

SleekView reads the FooEvents attendee records and joins back the WooCommerce order ID, the event product, and the line-level meta into a single grid. Custom registration fields written by FooEvents Custom Attendee Fields promote into named columns. The check-in cell is editable and writes to the same WooCommerceEventsStatus meta key the FooEvents check-in app uses, so the badge generator and email tools stay aligned.

For multi-event days the difference is concrete: instead of clicking from the orders screen to the FooEvents Check-Ins page and back, door staff hold a phone-friendly grid filtered to today, search by name or email across every event, and tap the check-in cell. Saved views split the screen between door staff, finance, and customer support without any of them needing to learn the FooEvents post structure.

Workflow

From scattered FooEvents data to one attendee grid

1

Connect to attendees

Create a SleekView against the FooEvents attendee post type. Native fields like name, email, and event link are detected, alongside the FooEvents meta keys for ticket type, order ID, and check-in status.
2

Join orders and events

Add the WooCommerce order join to surface order total, gateway, and customer details. Joining the event product brings in start time and venue meta so each row carries the operational context door staff need.
3

Pin role-based views

Save Door staff (today, check-in column, search), Finance (paid versus refunded by event), and Customer support (search by email, see all events for one buyer).
4

Check in and export

Toggle check-in cells on a phone or tablet at the door. Bulk update statuses when a session moves. Export per-event or per-ticket views as CSV for badge printing, vendor handoffs, and finance reconciliation.

Sample columns

A typical FooEvents attendee view

Attendees from every event in one grid with ticket type, order, and check-in status visible.
Source: WordPress posts/postmeta + WooCommerce order items
Attendee Event Ticket Type Order Check-in Status
Anna Reuter Founder Workshop VIP #1042 Checked-in Paid
Tobi Marx Founder Workshop Standard #1043 Pending Paid
Jana Pfeiffer Spring Summit Early Bird #1044 Pending Paid
Felix Wenger Founder Workshop Standard #1045 No-show Refunded

Comparison

Default FooEvents admin vs SleekView

Default FooEvents admin

  • Attendee data split across orders, products, and FooEvents screens
  • Check-ins handled in a separate Check-Ins panel, not the order list
  • Custom attendee fields hidden behind each ticket record
  • Cross-event lookups require switching between order pages
  • No saved views for door staff, finance, or support

SleekView

  • Cross-event attendee table with event, ticket type, and order on one row
  • Inline check-in toggle that writes the same FooEvents status meta
  • Show custom attendee fields (meal, t-shirt, accessibility) as columns
  • Save views per role like Door staff, Finance, or Refund queue
  • Filter by event, ticket type, or order status in one click

Features

What SleekView gives you for FooEvents

All attendees in one grid

Pull every FooEvents attendee for every event into one screen. Order ID, event, ticket type, and custom registration fields land on the same row, so the answer to a support ticket is one search away.

Filter by today's events

A saved view scoped to today's WooCommerce event products gives door staff exactly the rows they need. Pair with a check-in filter to triage the no-shows in the last hour of the event.

Inline check-in

Toggle the check-in cell on a phone or tablet. The cell writes to WooCommerceEventsStatus, the same meta key the FooEvents Check-Ins app uses, so the badge tool and email reminders stay consistent.

Audience

Who uses SleekView for FooEvents

Door staff

Run check-in from a phone using a grid filtered to today and a single editable check-in column. Searching by name or email crosses every event in the system, which matters at venues running multiple sessions back to back.

Finance

Reconcile FooEvents revenue against WooCommerce orders without leaving the grid. A saved view per event with order total, gateway, and refund status replaces the export-and-pivot workflow.

Customer support

Find every ticket attached to an email address when a buyer writes in about a name change or refund. The support view shows the buyer's full footprint across events, not just one order.

The bigger picture

Why FooEvents teams need a grid the dashboard does not ship

FooEvents made a sensible architectural choice when it built on WooCommerce: every ticket is an order line, every order is a real customer record, and refunds use the same machinery the rest of the store uses. The cost of that choice shows up on event day, when the operational picture is fragmented across WooCommerce orders, the FooEvents Check-Ins page, and the attendee post type. Door staff want one screen with name, ticket, event, and a tappable check-in column.

Finance wants paid versus refunded by event without an export. Customer support wants every ticket attached to an email when a buyer writes in. None of those rituals are unreasonable, and none of them require new data; they require the existing FooEvents and WooCommerce data to live on the same row.

Treating attendees as a real cross-event grid finishes the workflow that the dashboard left unfinished. Saved views become the role's rituals, the check-in cell removes the trip to a second screen, and the team spends the day talking to attendees instead of clicking between admin tabs.

Questions

Common questions about SleekView for FooEvents

Yes. The attendee post type and the order item meta written by FooEvents are both readable. Native fields like attendee name, email, and event link are detected automatically, and custom fields from FooEvents Custom Attendee Fields promote to columns once registered.

 

Yes. The check-in cell is editable and writes to the same status meta the FooEvents Check-Ins app reads, so a check-in done from the grid shows up in the badge tool and any post check-in email triggers the same way.

 

Yes. FooEvents is built on WooCommerce, so the order ID, payment status, and customer details live on the order. Joining the WooCommerce order onto the attendee row surfaces order total and gateway for the support and finance views.

 

Yes. The event product ID lives on every attendee row, so per-event filters and saved views work the same way as any other column. Door staff working a single event save a view scoped to that product and reopen it on the day.

 

Yes. Any custom fields registered through FooEvents Custom Attendee Fields, Meta Box, or ACF on the attendee CPT can be promoted to columns. Once promoted, the field is filterable and exports cleanly to CSV.

 

Yes. Any filtered view exports to CSV with the columns you have configured. The usual workflow is one saved view per event for badge printing and another per ticket type for vendor handoffs like meals or shirts.

 

Yes. Both add-ons store their data as additional meta on the attendee record, so booking slot, seat, and table fields can be promoted to columns. Filtering by slot or seat is the same operation as filtering by ticket type.

 

The FooEvents Check-Ins app is purpose-built for scanning tickets and that workflow stays the right tool for high-volume scan lines. SleekView covers the surrounding admin work — cross-event lookups, role-based saved views, finance reconciliation — that the check-in app does not try to solve.

 

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