SUMO Subscriptions for WooCommerce stores subscription plans, renewal schedules, billing intervals, suspended states, and cancellation reasons on a mix of wp_posts rows (for the subscription post type) and wp_postmeta keys like _sumo_subscription_status, _sumo_billing_interval, and _sumo_cancellation_reason. The default plugin admin lists subscriptions as a flat WordPress table, which works for routine renewals but breaks down when revenue ops needs to triage failed payments, cancellation reasons, and pause requests every morning.

SleekView Feedback reads the same SUMO Subscriptions postmeta and post type rows and renders each subscription as a card on a feedback board. Cards show the subscriber email, the plan name, the next renewal date, the lifetime revenue to date, and a status pill mapped to the SUMO subscription state. The board sorts by lifetime value votes, so the most valuable subscribers at risk float to the top instead of being lost in the default alphabetical or date sorted lists.

Upvotes write the new value back to a meta SleekView keeps next to the existing SUMO fields, which means scheduled retention reports and any downstream revenue dashboard see the same priority signal. SUMO Subscriptions keeps owning the actual billing cron, the renewal API calls, and the cancellation flow, while SleekView adds the missing board view revenue and support teams use to triage and save accounts.

Subscription businesses live and die on the difference between failed payments that get recovered and ones that quietly become cancellations. The default SUMO admin list sorts subscriptions by created date, which is great for accounting and useless for retention. A feedback board sorted by lifetime value votes the team actually placed today fixes that.

The most valuable subscribers at risk float to the top, status pills make the difference between paused, failed payment, and cancelled obvious at a glance, and the cancellation reason becomes a filterable category instead of buried in a meta field nobody reads. Because votes write back to the same SUMO meta the rest of the plugin already uses, nothing forks. SUMO Subscriptions keeps owning every billing cron, every renewal API call, every cancellation flow, and every email template your store depends on.

The board simply gives retention and support a single shared queue where the conversation about which subscribers to call first is grounded in real lifetime value, not on whoever happens to have the latest spreadsheet export open at the moment.