No, except where you explicitly edit a row. SleekView reads the same wp_cartflows_ca_cart_abandonment table CartFlows already maintains. Edits write back to that table through standard WordPress database functions, exactly as the default screen does. No shadow copy, no parallel storage.

Yes. SleekView only needs the standard CartFlows abandonment table, which both the free and Pro versions create with the same schema. No CartFlows licence is required for SleekView to read or write the table — but the recovery emails themselves still depend on whichever CartFlows version you have installed.

Yes. Build the filter you want, then export the visible rows to CSV. The export respects every filter, sort, and visible column set on screen, so the file matches exactly what the team is looking at — no "export everything" surprise downloads.

SleekView paginates and filters server-side rather than loading the full table into the browser, so even shops with hundreds of thousands of recovery rows render without locking up WP Admin. Indexes on email, status, and last-modified make filters resolve in milliseconds rather than seconds.

Yes. SleekView joins recovered carts to the resulting WooCommerce order on the order ID stored in the abandonment row. The view then shows which abandoned cart turned into which order, with order total, status, and date as columns next to the original cart total.

SleekView checks the same WordPress capabilities CartFlows uses for its recovery screen. Roles that can already see the abandonment screen can see the SleekView table. Roles that cannot see the recovery screen also cannot open the SleekView view, so the access boundary stays consistent.

Yes. SleekView supports row actions, so you can wire a Send recovery email action that calls the CartFlows hook for that cart. The status flips in place once the email is queued, so manual outreach and automated sequences appear in the same column.

Yes. WooCommerce HPOS only changes how orders are stored, not the CartFlows abandonment table. SleekView reads the abandonment table directly and joins to the canonical WooCommerce order store — whether that is the legacy posts table or HPOS — so both modes work without configuration.