edd_subscriptions for state, edd_orders and edd_order_items for renewal payments, the download post type for product names and edd_customers for the customer side. SleekView only reads data EDD Recurring has already written.

MRR sums recurring_amount across rows where status is active or trialling, normalised to a monthly cadence based on the billing period column. Yearly subscriptions are divided by 12, weekly by 0.23 and so on. The chart description spells out the normalisation so finance can audit it.

Yes. Group by date_cancelled on edd_subscriptions with weekly or monthly grouping and an Area card. Useful for spotting cancellations clustered around a price change or a deliverability incident.

When SleekView routes edits through the EDD Recurring API the standard hooks fire (cancellation, expiration, renewal notifications). Direct DB writes skip hooks for back-fill scenarios. The chart view itself is read-only and never triggers a write.

Yes. A Pie or Bar grouped by gateway shows the renewal volume per Stripe, PayPal or other gateway. Useful for redundancy planning and for spotting a gateway-level renewal failure that finance has not noticed yet.

Yes. Trial rows live in the same table with their own status. Filter to status equals trialling for an Area of new trials per week, useful for funnel reviews when free trial is the top of the pipeline.

Yes. Add a filter for product_id and every card narrows. Useful when one product line is its own MRR book and the team wants to track its renewal pipeline separately from the rest of the catalogue.

Yes. Any chart card drops to the table view of the same dataset and exports respect the column choice. Finance gets a CSV that matches what they see on the dashboard, not a separate report.