SUMO Subscriptions is a long-running WooCommerce subscriptions plugin from FantasticPlugins. Every subscription lives as a custom post in wp_posts with post_type set to sumosubscriptions, and the working state sits in wp_postmeta: subscription status (active, on hold, cancelled, expired, pending), next payment date, billing cycle (daily, weekly, monthly, yearly), trial expiry, and the linked WooCommerce order. The plugin's default admin lists subscriptions as posts, which is fine for individual edits but a poor surface for the daily retention question: how many trials are ending in 48 hours, which active subscribers are paused this week, and how does the renewal forecast look next week.

SleekView Kanban reads the sumosubscriptions rows joined to their postmeta and groups subscriptions by status. The board renders one column per canonical SUMO value: Active, On Hold, Cancelled, Expired. A virtual Trial Ending column surfaces subscriptions whose _sumo_trial_end meta falls in the next 48 hours, so the success team has a dedicated column for the conversion outreach. Each card shows the subscriber name, the plan title, the billing cycle, the next payment date, and a small trial badge for active trials.

Drag a card from On Hold back to Active and SleekView updates the _sumo_status postmeta on the subscription post, fires the SUMO state-change hook, and the next-payment scheduler picks up the change. Cancellations drag from Active to Cancelled and the same hook fires the cancellation email, the access revocation, and the dunning cleanup. The SUMO renewal scheduler, payment gateway integration, and downloadable-product access logic all keep running because SleekView reads and writes the same postmeta SUMO already uses.

Retention work is fundamentally status-keyed. Subscribers move between Active, On Hold, Trialing, Cancelled, and Expired, and the success of the work is measured by the deltas between those states. The default SUMO admin treats every subscription as a post with status filters on a paginated list, which is fine for individual edits but a poor surface for the daily and weekly rhythm retention actually runs.

The kanban turns each status into a column with a count, surfaces the Trial Ending virtual column for the conversion-outreach queue, and lets drag-and-drop replace the dropdown-plus-save loop the SUMO admin demands today. The success team measures their conversion rate from a column count. Billing measures the dunning queue from a badge.

Cross-team coordination happens through saved boards: a success-scoped board for conversion outreach, a billing-scoped board for dunning, a finance-scoped board for renewal forecasting. The SUMO state hooks, payment scheduler, dunning emails, downloadable-product access logic, and the WooCommerce order lifecycle all keep working without changes because the kanban reads and writes the same postmeta SUMO already uses.