SUMO uses a custom post type for subscriptions with renewal and billing data attached as postmeta on each record. SleekView reads the CPT and its postmeta together, promoting meta keys to typed columns. The CPT name and meta key prefixes are detected automatically so configuration stays minimal even on sites that have customized SUMO's storage.

Cancellations route through SUMO's normal cancellation actions because they need to update related WooCommerce orders, fire SUMO hooks for downstream automations and update billing cycle state correctly. SleekView surfaces the cancellation queue and lets you mark internal notes per subscription, but the cancellation action itself runs through SUMO so cancellation emails, refund handling and post-cancellation hooks all fire as configured.

Yes. Related meta keys from SUMO Reward Points (point balance, last accrual, redemption history) can be promoted as their own columns alongside subscription state. A common pattern is showing point balance in the subscription grid so retention can spot high-engagement customers at a glance and prioritize save-play outreach for the ones with significant unspent points.

Yes. Filter to upcoming renewals — say next 30 days, status active — and export the slice as CSV with the columns retention needs (customer email, next payment date, billing cycle, last note). The export honors per-role column masking so PII stays hidden where it should. Common pattern: weekly CSV export for the retention team's outreach queue, monthly summary export for finance.

Yes, with per-site or network-wide views. Single-store networks usually want per-site grids so each site's retention team sees only their own subscriptions. Multi-store retention functions can configure a network-wide aggregated view, useful when the same customer might have subscriptions across multiple sites in the network.

No. SleekView only loads on its own admin screens. The storefront, customer subscription dashboards, checkout and renewal cron jobs never trigger SleekView queries. Admin grid queries use indexed columns and pagination, so even subscription bases in the tens of thousands stay responsive.

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

SleekView itself does not send emails — it surfaces the queue. The standard pattern is to use the saved view's CSV export as input to your email tool (or to a recovery automation that pulls the same query), or to wire SUMO's existing renewal-warning hooks against the same data. Keeping the email layer in your existing tooling means SleekView does not become a deliverability surface, which is the right separation of concerns.