Yes. SleekView reads the FooEvents Bookings slot meta on WooCommerce order items directly through the same code path the bookings calendar uses, so the workflow does not need any extra configuration beyond pointing SleekView at the order item meta and choosing the check-in flag.

Yes. Dropping a card into Checked in writes Checked In to WooCommerceEventsStatus on the slot booking record, including the timestamp. The default check-in screen reads the same key, so the board and the screen show identical numbers without a separate sync step at the end of the day.

Yes. Dropping a card into Cancelled triggers the refund flow on the parent WooCommerce order through the same hook the order screen uses, so receipts and emails behave exactly as if the refund was issued from the order. SleekView records the drag in the audit log for review.

Yes. SleekView reads any custom slot field you configured on the FooEvents Bookings product page and lets you choose it for the card front. The value matches what shows in the bookings calendar because SleekView reads the same meta the calendar reads, not a copy stored separately.

Yes. The board can show every FooEvents Bookings slot record across every bookable product on the store, or be filtered to a single product ID for one venue's calendar. The grouping field stays the combined check-in and order status, only the filter changes per saved view for each role.

Yes. Saved kanban views are scoped per role and per capability, so reception staff can see Booked and Checked in only, finance can see Cancelled, and the venue owner sees all four columns. The underlying slot booking data does not change, only what each role reads on the board.

Yes. SleekView reads the live order item meta on every load, so the next time a customer reschedules a slot through the WooCommerce account screen and the slot date or time meta changes the board reflects the new values on the next refresh. There is no separate index to rebuild for slots.

No. SleekView paginates inside each column and loads card detail on demand, so a store with several thousand slot bookings renders the column counts immediately and streams card content as you scroll. Filters and saved views reduce the working set before the board even renders on screen.