SleekView for Subscriptio: subscriptions, renewals & invoices as tables
Read directly from Subscriptio's WooCommerce-backed subscription data — shop_order and HPOS wc_orders rows tagged as subscription parents and renewals, plus the recurring meta. Sort, filter, and inline-edit subscription status without opening each one.
♾️ Lifetime License available
Stop opening every subscription to check the next renewal
Subscriptio is a WooCommerce extension that turns orders into recurring subscriptions stored as parent orders with renewal child orders. Each subscription holds the recurring period, next-renewal date, and trial state in postmeta (or HPOS meta). The default WooCommerce admin lists orders fine but doesn't expose subscription-specific columns — next-renewal date, recurring total, billing-period meta — without a per-order click. SleekView reads the order data along with Subscriptio's recurring meta so a single subscriptions view shows next renewal, recurring amount, and customer lifetime value side by side.
Failed renewals are where billing teams lose hours. A renewal order fails, Subscriptio retries on the configured schedule, and the default admin shows the failed renewal somewhere in the orders list with no obvious link back to the parent subscription. SleekView surfaces parent subscription, retry count, last-failure reason, and next-retry date as columns on a Renewals view — billing teams catch the dunning queue at a glance instead of after a customer cancels.
Inline edits route through Subscriptio's standard save logic, so the recurring scheduler still fires, payment-gateway hooks still run, and customer notifications still send. Pause five subscriptions for a billing review in one bulk action and the same hooks fire as if each were paused by hand — except it took a few seconds.
Workflow
How SleekView reads your Subscriptio schema
Pick the source
wc_orders on HPOS or shop_order on legacy, scoped to Subscriptio's recurring meta. SleekView detects which path is active and exposes the matching columns.
Compose your column set
Save and scope the view
Edit inline and ship
Sample columns
A typical Subscriptio subscriptions view
wp_wc_orders (or wp_posts shop_order) + wp_postmeta with Subscriptio recurring keys
| Sub # | Customer | Plan | Recurring | Next renewal | Status |
|---|---|---|---|---|---|
| S-1042 | alex@studio.co | Pro Monthly | €29 / mo | Apr 28 | Active |
| S-1041 | ria@design.io | Team Annual | €348 / yr | Mar 12, 2027 | Active |
| S-1040 | tom@hello.dev | Pro Monthly | €29 / mo | Apr 26 | On hold |
| S-1039 | mia@brew.coop | Starter Monthly | €9 / mo | — | Cancelled |
| S-1038 | leah@rainfox.eu | Pro Monthly | €29 / mo | May 02 | Renewal failed |
Comparison
Default WooCommerce + Subscriptio admin vs SleekView
Default admin
- Subscription-specific columns (next renewal, recurring total) hidden behind per-order clicks
- Failed renewals don't link clearly back to their parent subscription
- No saved-view filters for dunning or paused subscriptions
- Customer lifetime spend across renewals not visible inline
- Bulk status changes (pause, resume) require per-subscription action
SleekView
-
Read parent subscriptions and renewal child orders from
wc_ordersorshop_order - Inline-pause, resume, or cancel subscriptions across many rows at once
- Custom columns from Subscriptio's recurring meta and gateway tokens
- Save filtered views per role (e.g. "Failed renewals", "Trials ending this week")
- Switch between table and kanban views grouped by status or plan
Features
What SleekView gives you for Subscriptio
Subscription-specific columns
Recurring amount, next-renewal date, billing period, trial state, gateway token — all surfaced as columns. The data Subscriptio already holds, finally visible without per-order clicks.
Dunning queue at a glance
A Renewals view filtered to failed renewals with retry count, last-failure reason, and next-retry date. Catch the dunning queue before customers cancel, not after.
Inline status changes
Pause, resume, or cancel inline with bulk operations across many subscriptions. Subscriptio's scheduler hooks, gateway integrations, and customer emails still fire as expected.
Audience
Who uses SleekView for Subscriptio
Billing teams
Failed-renewal dunning queue with retry count and last-failure reason inline. Bulk-resume after a card update without opening each subscription's edit screen.
Customer support
Search by email, see active subscriptions with next-renewal date and lifetime spend. Pause or resume mid-call with the same hooks Subscriptio's admin fires.
Finance and ops
Filter active subscriptions by plan and gateway for MRR reconciliation. Export the filtered set to CSV for the bookkeeper without leaving WordPress.
The bigger picture
Why row-level subscription ops beat per-order clicks
Subscriptio extends WooCommerce well — recurring billing, gateway integrations, retry schedules, trial handling. The data lives in the same orders table WooCommerce already knows how to scale, with subscription-specific keys layered on as meta. The default admin, though, surfaces those keys behind a per-order click.
That works for a small site with a handful of subscriptions. It does not work for a SaaS-style WordPress shop with thousands of active subscriptions, weekly failed-renewal dunning, and a support team that needs lifetime spend on screen during a call. The default Orders list shows fixed columns, hides next-renewal date, and forces every pause or cancel through the per-order screen.
Recurring meta — billing period, gateway token, retry schedule, trial-end timestamp — exists in the database but never surfaces in the list. SleekView turns the same data into the workspace each role needs: billing triages the dunning queue, support pauses subscriptions mid-call, finance cuts MRR by plan and gateway. Same database, same hooks, dramatically less clicking — and failed renewals stop slipping past until the customer cancels.
Questions
Common questions about SleekView for Subscriptio
Yes. Subscriptio stores subscriptions as orders tagged with recurring meta. On HPOS stores it reads wc_orders with the Subscriptio meta keys; on legacy it reads shop_order posts with postmeta. Both paths surface next-renewal date, recurring total, and billing period as real columns.
Yes. Subscriptio links renewals to parents via post-parent on legacy and a parent-id column on HPOS. SleekView joins them so a parent-subscription view can include latest-renewal status, retry count, and last-renewal date — useful for spotting subscriptions whose renewals stopped without manual cancellation.
 Yes. SleekView writes through WooCommerce's CRUD layer and Subscriptio's own status-change hooks, so the recurring scheduler updates next-renewal dates, gateway tokens are preserved, and customer notifications fire. Bulk operations don't bypass these — they iterate so behaviour matches per-subscription edits.
 Yes. SleekView aggregates renewal totals per customer using the order-customer relationship. A Customers view can show active subscriptions, lifetime renewal total, and last-renewal date side by side, useful for support triage and segment exports.
 Subscriptio retries failed renewals on a configurable schedule. SleekView surfaces retry count, last-failure reason, and next-retry timestamp as columns on a Renewals view, so the billing team triages the dunning queue at a glance and can bulk-pause subscriptions whose cards are clearly dead.
 No — it's an additional admin surface. Subscriptio's per-subscription editor stays where it is. SleekView adds row-level views Subscriptio doesn't ship — failed-renewal dunning queue, plan-by-plan MRR cuts, customer lifetime view — without disturbing existing workflows or hooks.
 SleekView reads the gateway token and last-charge metadata Subscriptio stores per subscription. It doesn't initiate charges directly (Subscriptio's scheduler does that), but inline status changes that trigger Subscriptio's own gateway calls — pause, resume, cancel — work the same way through SleekView.
 
Queries hit indexed columns on wc_orders (or posts on legacy) directly. Recurring-meta joins are scoped per key. Aggregate columns like lifetime renewal total are opt-in per view — keep them off the default list to keep the subscription table fast even on stores with tens of thousands of active subscriptions.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout