WooCommerce Cart Abandonment Recovery stores every tracked cart in the wp_cartflows_ca_cart_abandonment table. Each row carries an order_status column with values like normal, abandoned, completed, and lost, plus the email captured at checkout, the cart total, the line items, the customer's first name, the session start time, and the abandonment timestamp. The plugin's report screen shows the data as a flat table, which is fine for export but blind to the live retention work the team really needs to do every day.

SleekView Kanban reads the same wp_cartflows_ca_cart_abandonment rows you would query directly. Pick order_status as the group column and every cart becomes a card slotted under Normal, Abandoned, Recovered, or Lost. Card fronts show the captured email, the customer first name, the cart total in store currency, the abandonment age, and the recovery email count, so the retention team sees the shape of every cart at a glance without opening any cart detail row.

Dragging a card between columns calls the plugin's cart status helper, which writes back to wp_cartflows_ca_cart_abandonment.order_status and stops the recovery email sequence for that cart if the new status is Recovered or Lost. The recovery email scheduler picks up the change on its next pass and the report screen reflects the new status, exactly as it would after a manual update from the cart admin screen.

Stores running Cart Abandonment Recovery accumulate thousands of tracked sessions every month. Some recover on their own when the customer returns. Some never come back regardless of the email sequence.

A meaningful slice could recover if someone reached out personally with a discount code or a phone call. The default report screen treats all of them the same, which means retention managers export CSVs to find the high-value carts and never have time to triage them before they go cold. The disconnect between what the recovery system is doing automatically and what the retention team could do personally shows up in the worst places.

A $500 abandoned cart from a repeat customer cycles through the standard email sequence and gets nothing different. A customer who unsubscribed from recovery emails keeps receiving them because nobody manually marked the cart Lost. A kanban view that reads and writes the same wp_cartflows_ca_cart_abandonment rows the recovery scheduler reads keeps the team and the funnel honest.

Every drag is a real status change, every column count reflects the real recovery health, and the cards themselves carry enough context for a retention manager to triage high-value carts on day one of the job.