No. The plugin's own scheduler, email handler, and recovery-detection logic continue running. SleekView is a presentation and editing layer over the plugin's stored data — abandoned carts, scheduled emails, recovery links. Configuration of the email sequences and triggers still belongs in the plugin's admin.

The plugin stores carts in a dedicated custom table (typically named with a cartflows_ca_ prefix) and email-history rows linked by cart id. SleekView reads each like any other database source and joins on cart id for unified row context. Edits write through the plugin's option/action API, not direct table updates.

Yes. The plugin exposes a manual-send action used by its own admin's per-cart view; SleekView wires it to a row-level button. The send respects configured throttles and the standard email handler, so you don't accidentally bypass safety like duplicate-send protection.

The plugin allows flagging a cart so its scheduled emails are cancelled and no further messages are sent. Useful when a customer has reached out by another channel or asked not to be emailed. SleekView lets you set the flag inline as a row action; the plugin handles cancellation and the cart row reflects the new state.

Yes. When a cart converts, the plugin records the recovered WooCommerce order id on the cart row. SleekView surfaces it as a column linked to the order's edit screen, so you can jump from "recovered cart" to the actual order without navigating elsewhere.

The cart-abandonment plugin reads order data through WooCommerce's order CRUD, which is HPOS-aware. SleekView reads the cart-abandonment table directly and links recovered orders by id; whether the order itself lives in wc_orders or legacy posts, the link works. Build a parallel SleekView for orders if you want recovered-order details inline.

Yes. The plugin tracks current stage (email 1, 2, 3, recovered, expired) on each cart row. SleekView treats it as a column for filtering, sorting, and grouping. "Reached email 3, no recovery" is one filter; "recovered after email 2" is another. Useful for tuning the email sequence.

The plugin's GDPR settings — checkout consent capture, retention windows — continue to apply. SleekView surfaces consent-state as a column where the plugin records it, so a recovery operator can see at a glance which carts are eligible for recovery emails. Carts without consent simply have no scheduled emails for the plugin to send.