SleekView Kanban for CartFlows
CartFlows stores each checkout as a WooCommerce order with the originating flow and step recorded in meta. SleekView reads those orders, groups them by status, and renders one card per order so the team can drag a sale from On hold to Processing without opening it.
♾️ Lifetime License available
Read your CartFlows funnel as a kanban, not a list
CartFlows is a checkout and funnel builder for WooCommerce. Each flow is a cartflows_flow post with checkout, upsell, downsell, and thank-you steps inside it. When a buyer converts, CartFlows hands the cart to WooCommerce, so the resulting order lives in wc_orders with the standard status column and a _cartflows_flow_id entry in wc_orders_meta linking it back to the funnel that produced it.
SleekView reads wc_orders and joins on wc_orders_meta to pick up the CartFlows flow ID and step. The natural column to group by is status, which moves through pending, processing, on-hold, and completed for every funnel sale. Cards show the customer name from billing_first_name plus billing_last_name, the total_amount, and the flow title resolved from the linked cartflows_flow post.
Dragging a card from On hold to Processing writes wc-processing straight to wc_orders.status, the same value the WooCommerce edit screen would have saved, so emails, stock decrements, and integrations fire normally. Refunded and failed orders stay visible as their own columns instead of vanishing from the list, which matters when a funnel has a high upsell decline rate.
Workflow
From wc_orders to a CartFlows board in four steps
Point SleekView at WooCommerce
Pick status as the grouping column
Choose what shows on cards
Enable drag and drop
Sample board
Sample CartFlows orders board
Comparison
Default CartFlows reporting vs SleekView Kanban
Default CartFlows orders
- Funnel orders live in the WooCommerce orders list, no per-flow board view
- Per-step stats sit on the CartFlows analytics screen, away from orders
- Changing status means opening each order and saving the form
- Refunded and failed orders are hidden behind a status filter dropdown
- No way to scope the funnel order list per role without extra plugins
SleekView Kanban
-
Reads
wc_orderswith the CartFlows flow ID fromwc_orders_meta -
Groups by
statusso every funnel order shows up as a card - Drag and drop writes through the WooCommerce API for clean status changes
- Card fronts show customer, total, and flow title in one glance
- Failed and refunded orders stay visible as their own columns on the board
Features
What SleekView Kanban gives you for CartFlows
Group by any status field
Group by wc_orders.status by default, or by a custom meta key like _cartflows_step or _payment_method when you want to slice the funnel by upsell step or gateway. Each column counts its cards live so the team always knows the funnel mix.
Drag and drop writes through Woo
Cards move with the pointer or arrow keys and SleekView writes the new value through the WooCommerce order API. Webhooks, stock, emails, and CartFlows analytics behave exactly like a manual change on the edit screen.
Filter by flow, date, and total
Filter the whole board by flow ID, date range, payment method, or order total. Useful when you run a Black Friday flow alongside the evergreen one and want to look at each pipeline in isolation without rebuilding the view.
Audience
Where a CartFlows kanban earns its keep
Daily fulfillment standups
Ops pulls up the Processing column every morning and burns it down to Completed during the day. Counts on each column show progress without anyone running a report.
Bank transfer follow-up
On hold collects every order that picked manual payment. Finance works the column, drags paid orders to Processing, and leaves the rest visible until they clear or expire.
Upsell decline tracking
Filtering the board to a single upsell step makes the decline rate obvious in card counts, which informs which offers stay in the funnel and which get rewritten.
The bigger picture
Why a board beats the CartFlows orders list
CartFlows is built to convert, not to manage what happens after the buy button. Once a sale lands, the order belongs to WooCommerce, which still ships the same flat list it always has. Funnel teams end up jumping between the CartFlows analytics screen for conversion numbers and the WooCommerce orders screen for fulfillment, and neither view answers the question "where is each sale right now." A kanban grouped by status puts every funnel order on one screen and uses position to show state.
Pending payment, Processing, On hold, and Completed become columns, counts on each column expose the funnel mix at a glance, and dragging a card writes the same wc_orders.status value the order screen would save. Refunded and failed orders stay visible as their own columns instead of vanishing behind a filter, which matters when an aggressive upsell sequence pushes the failure rate up. The team works the same data the orders screen works, just with position and counts doing the heavy lifting instead of clicks.
Questions
Common questions about SleekView Kanban for CartFlows
No. SleekView Kanban is an extra reading layer on the same wc_orders table. The standard WooCommerce orders screen and CartFlows analytics keep working, and any change made on the board is the same wc_orders.status write a manual edit would do.
The columns are the WooCommerce statuses that exist on funnel orders: Pending payment, Processing, On hold, Completed, Cancelled, Refunded, and Failed. SleekView only renders the ones that actually have rows, so a funnel that never sees refunds will not show an empty Refunded column.
Yes. Any column on wc_orders or any meta key on wc_orders_meta can be the grouping column, including a custom field that stores the step or upsell variant. The drag and drop target then writes that meta key instead of status, which is useful when you treat upsell decisions as the pipeline.
Yes. SleekView calls the WooCommerce order API to write the new status, so woocommerce_order_status_changed and the per-status transition hooks fire, transactional emails go out, stock is adjusted, and CartFlows event tracking sees the change the same way it would from the edit screen.
Yes. A board can filter by the _cartflows_flow_id meta value so you get a per-flow pipeline, or filter by date and payment method so the Black Friday flow does not drown the evergreen one. Filters compose with the grouping column and apply across all columns at once.
Yes. SleekView reads from wc_orders and wc_orders_meta when HPOS is on and falls back to the shop_order post type on legacy stores. The same board configuration works in both modes, which matters during the HPOS migration window.
Yes. Each drag writes a single status change against the latest row, not a snapshot. If two people drag the same order in the same second, the second write replaces the first, exactly like two staff editing the same order in the orders screen back to back.
Yes. SleekView saves views per role, so marketing can see a board that groups by funnel and hides finance fields, ops can see status with stock columns, and finance can see status with totals and gateway. Each role only sees what their job needs without different plugins.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout