WooCommerce's wc_orders, wc_order_addresses and wc_orders_meta when HPOS is on (or shop_order with postmeta on legacy stores), plus LearnDash's learndash_user_activity and learndash_user_activity_meta. The buyer's user_id ties them together.

Yes. Subscriptions stores subscriptions as the shop_subscription post type (and optional custom tables in recent versions). SleekView joins the subscription to the parent order and to the learner's activity, so recurring-access course businesses get the same table with subscription status added as a column.

Yes. Select rows and trigger refund through WooCommerce's CRUD. Standard payment-gateway hooks fire, refund emails send and stock adjustments run as if each order had been refunded individually.

Only that SleekView reads the schema WooCommerce is using. With HPOS enabled (default since WooCommerce 8.2) it reads wc_orders directly. On legacy stores it reads the shop_order post type and postmeta. The table looks the same either way.

Filter the joined table to orders with status of completed and learndash_user_activity with no rows for the linked course_id. The result is a row list ready for outreach or for a triggered email sequence.

Yes. Where SleekView writes through each plugin's CRUD layer (order status, course enrolment), the standard hooks fire normally so emails, certificates and stock changes propagate as expected.

No. wc_orders is indexed on status, date_paid and customer_id, and learndash_user_activity is indexed on user_id and activity_started. The join uses indexed columns on both sides, so tables with hundreds of thousands of orders render in well under a second.

Yes. Any filtered table exports to CSV with the same columns the view shows. Useful for revenue reporting, for marketing attribution exports or for sending a course owner their per-course numbers.