FKCart replaces the WooCommerce cart with a sliding side cart that captures bumps, upsells, and free-shipping nudges before checkout. Once a customer pays, the order lives in the same WooCommerce orders table with the standard post_status values like wc-pending, wc-processing, wc-on-hold, wc-completed, and wc-refunded. Custom meta from FKCart records which bumps were accepted and which upsells fired, but the order admin gives you no way to see that on a list.

SleekView Kanban reads the same orders through the WooCommerce REST endpoints, pulls the FKCart meta with each row, and turns the status column into the natural grouping axis for a board. Each card shows the customer name, the order total, the payment method, and a small marker when a bump or upsell was accepted. Columns mirror your real WooCommerce statuses, so a glance tells you how many sliding-cart orders are still pending, how many are being shipped, and how many have completed.

Drag a card from Processing to Completed and SleekView writes through the WooCommerce REST endpoints. The order completion email fires through your existing FKCart-aware mailer, refund drags trigger the standard refund flow, and any custom statuses your fulfilment plugin uses become their own columns automatically. The sliding-cart context that drove the order remains visible at a glance on the board.

FKCart's value lives in the moments right before checkout: the bump, the upsell, the free-shipping nudge that turns a thirty-dollar cart into a sixty-dollar order. Once the order is placed, all of that context is buried in WooCommerce order meta that the default admin list cannot show. Staff working the fulfilment queue see an order ID and a total and have to click into each one to find out whether a bump was accepted, whether an upsell hit, or whether anything beyond the headline product needs to ship.

The board view fixes this by making status the primary axis, which is the only state that drives fulfilment, and by lifting the bump and upsell markers onto the card itself. A picker scanning the Processing column can tell which orders carry accessory bumps without ever opening the detail page. A CS rep handling a refund can see immediately that an order included two bumps and an upsell before opening the conversation.

Drag updates the WooCommerce order through the same REST endpoints, so the FKCart meta stays intact and every email and integration fires as normal. The board treats the cart context as a first-class signal instead of hiding it in a meta box.