WooCommerce Subscriptions stores each subscription as a shop_subscription post type in wp_posts, with extensive metadata in wp_postmeta and renewal orders linked back to the parent subscription. The post_status takes values like wc-active, wc-on-hold, wc-pending-cancel, wc-cancelled, wc-expired, and wc-pending. Each transition triggers concrete billing behavior: payments retry, renewal emails fire, and access to memberships or content turns on or off.

SleekView Kanban reads the same shop_subscription records you would query with WC_Subscriptions::get_subscriptions or the WooCommerce REST API. Pick post_status as the group column and every subscription becomes a card grouped under its current state. Cards can show the customer name, billing schedule, next payment date, total billed to date, and the product being renewed, so the retention team has full context before reaching out.

Dragging a card from Active to On hold calls the same WC_Subscription::update_status method WooCommerce Subscriptions uses internally. Payment retries pause, renewal emails are suppressed where appropriate, and any integration listening for woocommerce_subscription_status_updated reacts normally. A customer who calls in to request a pause moves to On hold in seconds. A successful retention conversation drags them back to Active and billing resumes on the next scheduled date.

A subscription business does not have orders so much as it has relationships, and those relationships live in a constant state of motion. Customers upgrade, downgrade, pause, fail a renewal, and resume billing all in the same week, and the difference between a 2 percent and a 4 percent monthly churn rate is enough to change the trajectory of the entire company. The standard WooCommerce Subscriptions admin shows every record as a row in a list, which is useful for accounting but blind to the actual shape of the funnel.

There is no visual signal that On hold has doubled in the last fortnight. There is no obvious way to prioritize cancel save calls by remaining contract value. There is no way to spot the cluster of monthly subscribers who all fell off the same product in the same week.

A kanban view turns the implicit pipeline into something you can look at. The columns are the lifecycle. The card density is the health of the funnel.

Dragging a recovered card from On hold back into Active is both the retention action and the system update at the same time, and the data feeding everything is the same data WooCommerce Subscriptions already maintains.