No. Order data is stored as meta on the standard WooCommerce order tables — no separate Mollie plugin tables. Every _mollie_-prefixed key (payment ID, method, customer reference, status) lives in wc_orders_meta. SleekView reads those keys as columns, which works against legacy CPT order storage and modern High-Performance Order Storage transparently.

Capture and refund still go through the Mollie plugin because they need to update Mollie-side state through Mollie's API. SleekView shows the queue and inline notes around capture — which orders are authorized, which are pending clearance, which have refund state — but the actions themselves run through Mollie's existing order actions so audit trails and webhook handlers stay consistent.

Yes. When used with WooCommerce Subscriptions, renewal orders appear in the grid with their Mollie references. Reference Transactions and stored Mollie customer IDs let renewals reuse the original payment method without customer re-entry. Filtering to renewal-only orders becomes a saved view, useful for tracking renewal failure rates and dunning queue length.

Yes. Saved views can be private to one user or shared by capability. Common patterns: a shared "SEPA pending clearance" view for finance and support, a shared "Stalled webhook 2+ hours" view for ops, and private analyst views for one-off questions. Sharing respects the same per-role row scoping so a shared view does not bypass anyone's read permissions.

Yes. The grid reads from High-Performance Order Storage tables Mollie writes to in modern WooCommerce. Sites still on legacy CPT order storage are also supported — SleekView checks which layer is active and reads accordingly. Migrations from CPT to HPOS happen transparently; column promotions and saved views carry over without reconfiguration.

No. SleekView only runs in admin views you open. Storefront pages, the Mollie checkout flow, webhook handlers and customer-facing API calls never trigger SleekView queries. Even in admin, the grid uses indexed columns and pagination, so opening the orders view stays fast on stores with hundreds of thousands of Mollie transactions.

Recurring payments through Mollie's first-and-recurring pattern store the recurring reference and customer ID in meta, both of which surface as columns. Sort by Mollie customer ID to see the chain of recurring orders for a single customer; group by it to count active subscribers paying via Mollie. Pairs cleanly with WooCommerce Subscriptions for full subscription analytics.

Settlement timestamps written to meta by Mollie integrations surface as their own column. Different methods settle on different cycles — iDEAL same-day, SEPA over several business days — so grouping by settlement date helps finance match Mollie's settlement reports. Discrepancies between expected and actual settlement become visible in a saved view rather than after a manual export.