EDD Recurring Payments stores subscription state in edd_subscriptions with product, customer, gateway, billing period, status and timestamps for created, expiration, trial end and last renewal. The default Subscriptions screen lists them with a fixed column set.

SleekView reads the same tables. Customer email, product name, gateway, billing period, recurring amount and last-renewed date sit as real columns. Filter to active subscriptions on Stripe, to trials ending this week, or to a single customer's whole subscription book, all without opening each row.

Inline edits route through the EDD Recurring API where supported, so cancellation, expiration and renewal hooks fire, customer notifications still send and any plugins listening on subscription state stay consistent. The table is the operating surface a recurring business actually needs.

EDD Recurring quietly turns a digital download store into a SaaS-shaped business. The default Subscriptions screen does not match how a SaaS-shaped business actually runs. A real table with customer, product, gateway, status and renewal date as columns turns the book into a workspace.

A filter to failing subscriptions becomes a retention sprint. A filter to trials ending becomes a conversion sprint. A per-customer view becomes a support workflow.

Same tables EDD Recurring already maintains, table surface that respects what the data actually represents.