Yes, as long as the data is stored in wp_postmeta or a queryable custom table. Most variation-price plugins use wp_postmeta keys like _role_price_ or _tier_prices; SleekView exposes those as columns and edits them inline. Custom-table extensions can be pointed at as a joinable source.

Yes. SleekView writes through WooCommerce's variation CRUD where supported, so woocommerce_product_set_price and related save hooks fire per row. Listeners that rebuild a price index, refresh search, or recalculate role-based prices see every change.

Yes. Filter to the relevant sale (by campaign tag, category, or sale-end date), select all, and inline-edit _sale_price_dates_to. Each row writes through CRUD so sale-status transitions fire as expected.

Yes. subscription_variation from WooCommerce Subscriptions follows the same post-type structure. Recurring-price meta (_subscription_price, _subscription_period) is surfaceable as columns alongside one-off price meta.

Yes, by filtering on _sale_price_dates_from and _sale_price_dates_to within a window. A saved view like "Sales overlapping this campaign" gives the promotions team an audit before they schedule a new sale on the same SKUs.

Yes, if the multi-currency plugin stores per-currency prices in wp_postmeta. Each currency key becomes a column, so a price view shows USD, EUR, GBP side by side per variation. Inline edits write back through the same meta keys the multi-currency plugin reads.

Queries hit indexed columns on wp_posts and the indexed meta_key + post_id path on wp_postmeta. Pagination is keyset where possible. Heavy aggregate columns (lifetime sales per variation) are opt-in per view to keep default lists fast.

Yes. Each saved view exports as CSV from its current filter and column set. Useful for sharing a sale audit with finance or sending a tier-price snapshot to a wholesale buyer.