Flexible Shipping extends WooCommerce with custom shipping methods based on weight, value, item count, and shipping zone rules. Orders that use those methods live in wp_posts or the HPOS wp_wc_orders table with standard statuses like wc-processing, wc-on-hold, wc-completed, and wc-cancelled. The shipping method label, the cost, and the destination country live in order item meta under _shipping_method and _shipping_total. The native WooCommerce orders screen shows them mixed with all other orders.

SleekView Kanban reads the same WooCommerce orders you would query with WC_Order, filtered to orders that selected a Flexible Shipping method at checkout. Pick post_status as the group column and every order becomes a card slotted under Processing, On Hold, Completed, or Refunded. Card fronts show the customer name, the order total, the shipping country, the Flexible Shipping method label, the total weight from line item meta, and the shipping cost, so dispatch sees every order's shipping context directly on the card.

Dragging a card between columns calls the standard WooCommerce status transition the admin uses, which fires woocommerce_order_status_changed. The customer notification email goes out through WooCommerce's email module, the order timeline records the transition, and any extension subscribed to the WooCommerce hooks reacts, exactly as it would after a manual admin status change from the order edit screen by a dispatch lead.

Stores running Flexible Shipping use the plugin's complex rules to charge accurate shipping based on weight, value, item count, and zone. The orders come through with shipping method labels and costs that reflect those rules. The default WooCommerce orders screen does not surface the shipping method or the weight as sortable columns, which means dispatch teams export CSVs or run SQL queries every time they need a meaningful breakdown of what is shipping where.

The disconnect between the shipping rules the team configured and the orders screen the team has shows up in the worst places. A heavy-weight order picks up the wrong shipping method because the cart rule was off by 100 grams and nobody catches it until the customer complains about overcharge. A cluster of orders to a specific country sits in Processing for days because dispatch did not realize they all share the same Flexible Shipping method and need customs documentation.

A kanban view that reads and writes the same WooCommerce orders the plugin shipped keeps the team and the warehouse honest. Every drag is a real status change, every column count reflects the real dispatch health, and the cards themselves carry enough context for a new dispatcher to triage shipments on day one of the job.