Yes. SleekView reads the FooEvents attendee meta on WooCommerce order items directly through the same code path the FooEvents check-in screen 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 FooEvents attendee 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.

Yes. Dropping a card into Refunded 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 FooEvents custom attendee field you configured on the WooCommerce product and lets you choose it for the card front. The value matches what shows in the check-in screen because SleekView reads the same meta the screen reads, not a copied version.

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

Yes. Saved kanban views are scoped per role and per capability, so door staff can see Paid and Checked in only, finance can see Refunded, and the organiser sees all four columns. The underlying FooEvents attendee data does not change, only what each role reads on the board.

Yes. SleekView reads the distinct values present in WooCommerceEventsStatus and renders one kanban column per value. If you registered a custom status through a FooEvents snippet or a third party add-on, that value shows as a column next to the built-in ones with no extra configuration.

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