WooCommerce Shipment Tracking attaches tracking information to orders through postmeta. Each shipment carries a tracking_provider, a tracking_number, a tracking_link, a date_shipped, and a tracking_status derived from the carrier callback when integrated providers are enabled. The plugin stores all of this under _wc_shipment_tracking_items on the order in wp_postmeta as serialized JSON. The native order edit screen shows tracking inline but offers no overview of every shipment across the storefront.

SleekView Kanban reads the same shipment tracking meta you would query with the plugin's helper functions. Pick the tracking_status as the group column and every shipment becomes a card slotted under Pending, In Transit, Delivered, or Returned. Card fronts show the order number, the customer name, the tracking_provider, the tracking_number, the date_shipped, and the destination country, so dispatch sees the shape of every shipment without opening individual order detail screens for each one.

Dragging a card between columns updates the tracking_status in the order's _wc_shipment_tracking_items postmeta and fires the plugin's status update hook. Customer tracking notifications send through the email module if you have the integration enabled, the order timeline records the change, and any extension listening for shipment updates reacts, exactly as it would after a manual update from the order admin shipment tracking metabox.

Storefronts running Shipment Tracking ship hundreds of orders every week. Some are Pending while the carrier picks up the warehouse pallet. Most are In Transit and need basic monitoring against the carrier SLA.

A steady stream get Returned to sender because of address errors or missed delivery windows. The default WooCommerce orders screen does not show tracking_status as a sortable column, which means dispatch teams export CSVs or run SQL queries every time they need a meaningful breakdown of shipment health. The disconnect between what the tracking plugin holds and what the team can see shows up in the worst places.

A shipment that stalled in transit for two weeks does not get a carrier ticket because nobody noticed. A returned shipment sits in the warehouse for days because nobody updated the tracking_status in the order meta and the customer never gets a refund. A kanban view that reads and writes the same _wc_shipment_tracking_items postmeta the order metabox reads keeps the team and the order timeline honest.

Every drag is a real status change, every column count reflects the real shipment health, and the cards themselves carry enough context for a new dispatch hire to triage on day one of the job.