Yes. SleekView detects whether the store is on HPOS wc_orders or legacy shop_order posts and queries the right schema. Chart cards configured once work on either path, so an HPOS migration doesn't break the dashboard.

MRR cards sum the recurring total across active subscription parents, normalised to a monthly value using the billing-period meta (a yearly plan is divided by 12). The aggregation and column are configurable, so finance can swap to ARR or strip trial subscriptions if needed.

Yes. Subscriptio stores the gateway on the order. A Bar card grouped by gateway and summed on recurring total gives an MRR-by-gateway breakdown, useful when a retry batch fails on one provider but not another.

Cards run their queries on each dashboard load and cache for a configurable interval. A renewal that fails on the next-renewal date appears in the failed-renewal Number card within the cache window, so the dunning queue size stays accurate.

Yes. Group renewal orders by renewal date with a daily or weekly bucket and pick an Area or Line variant. Churn is buildable as a derived metric: cancelled subscriptions divided by active count at the start of the period.

Each chart card runs one aggregate query against indexed columns on wc_orders or posts. Recurring-meta joins are scoped per key. Heavy aggregates like lifetime renewal totals are opt-in per card to keep the dashboard responsive.

No. Subscriptio's per-subscription editor and scheduler stay where they are. SleekView Charts adds the dashboard the default admin doesn't ship, without disturbing existing hooks or workflows.

Yes. Each card respects WordPress capabilities, so billing sees the dunning Number card, finance sees MRR by plan, support sees the status mix, and only admins see them all on one screen.