YITH WooCommerce Subscriptions uses WooCommerce order tables plus subscription meta with the _ywsbs_ prefix. SleekView reads both — the parent order data for customer information, totals and currency, and the subscription meta for status, billing schedule, period and trial flags. The combined view treats each subscription as one row with all fields accessible.

Cancellations route through YITH's normal cancellation actions because they need to update related WooCommerce orders, fire YITH hooks for downstream automations and stop the renewal scheduler correctly. SleekView shows the cancellation queue and lets you mark internal retention notes, but the cancellation itself runs through YITH so cancellation emails, scheduler updates and refund handling fire as configured.

Yes. Related YITH Membership meta keys (membership level, access expiry, plan tier) can be promoted as their own columns alongside subscription state. A common pattern is showing membership level in the subscription grid so retention can spot high-tier customers at a glance and prioritize save-play outreach for them. Membership and subscription queries also share the same saved-view system.

Yes. Modern YITH versions write to High-Performance Order Storage which SleekView reads natively. Sites still on legacy CPT order storage are also supported — SleekView checks which layer is active and reads accordingly. Migrations from CPT to HPOS happen transparently from SleekView's perspective; column promotions and saved views carry over without reconfiguration after the migration completes.

No. SleekView only loads on its own admin screens. Storefront pages, checkout flows, cart, customer subscription dashboards and renewal cron jobs never trigger SleekView queries. Even in admin, the grid uses indexed columns and pagination — subscription bases in the tens of thousands stay responsive without any tuning.

Yes. Saved views can be scoped private to one user or shared by capability. Common patterns include a shared "Trials ending" view for the conversion team, a shared "Failed payments" view for recovery and private analyst views for one-off questions. Sharing respects per-role row scoping so a shared view never bypasses anyone's read permissions.

Variable subscription products with different billing tiers store the chosen tier in subscription meta, and SleekView promotes that as a filterable column. Group by product plus billing tier to see how customers distribute across pricing variants. Useful when running A/B price tests or evaluating whether to retire a tier with declining subscriber count.

Yes. Each subscription row links back to the parent order and to its renewal order chain. A subscription's renewal history (which renewals succeeded, which failed, which were retried) reads in a side panel without leaving the grid. This matters for support conversations where the question is "what actually happened on this customer's last three renewals" — answering takes seconds rather than tab-juggling between order and subscription edit screens.