Both. SleekView reads LearnDash WooCommerce tables and the status column at the database level, so whichever tier you run the board still builds. Paid add-ons that add custom fields or extra status values are picked up automatically because SleekView scans the live schema on render.

SleekView calls the WooCommerce and LearnDash WooCommerce update functions, which fire the same hooks the admin uses on a manual status change. Any custom listener you have on learndash_woocommerce_order_completed runs exactly as if you had edited the order from the WC admin.

Yes. Card layouts are per board. Your orders board can show customer, course, total, and date. A per course board can show course, order count, and revenue. Each board remembers its own card template so the team does not reconfigure when switching context at all.

Yes. SleekView respects every WordPress capability check WooCommerce and LearnDash register. A user who can view but not edit orders can drag a card to inspect, but the writeback only fires for users with the same capabilities the WC order edit screen would enforce on a manual save.

Add the new status value in WooCommerce the way you normally would, by registering a custom order status. SleekView picks it up on the next board load because columns are derived from the distinct status values present on order rows, not from a hard coded enum at all.

No. SleekView paginates cards per column instead of loading every order up front. The board fetches counts via an indexed status query, and each column loads a window of cards on demand, so even a WC site with hundreds of thousands of orders stays responsive on hosting setups.

Yes. Any WC or LearnDash related table with a status like column is a valid board. The subscription table grouped by status, the refund queue, and the course progress meta all work the same way as the main orders board once you point SleekView at the right table to group cards on.

It stays in sync because there is no separate database. SleekView reads the same orders table the WooCommerce admin reads. Changes on the kanban appear in the orders list immediately, and edits from either admin appear on the next board refresh without cron sync.