WooCommerce Shipping Multiple Addresses lets a single customer ship one order to multiple recipients (corporate gifting, bulk orders to multiple locations, family parcel shipments). The plugin stores additional shipping-address rows in wc_order_addresses on HPOS or in a serialized structure under postmeta on legacy stores. The default Orders screen still treats the order as one row, so the multiple shipping addresses are invisible until you open the order.

For fulfilment, that's the wrong shape. A warehouse picker doesn't care about the order, they care about the next shipment to pack. A corporate-gifting account manager doesn't care about the order's grand total, they care about the per-recipient handoff. SleekView reads the per-address rows directly so each shipment becomes a row with its own recipient name, address, item list, and status, joinable back to the parent order for billing context.

Inline edits to shipping status route through the plugin's address-status update path where supported, so per-recipient tracking-number entry and per-shipment status hooks fire normally. Bulk-flip 40 shipments to "Shipped" after a courier handover in one action, with hooks firing per shipment.

Split-shipment orders break the one-order-one-row assumption WooCommerce's admin is built on. Corporate gifting at scale, bulk orders to multiple offices, family parcels shipped before the holidays, all of these put one order with many shipping addresses into the database. The plugin stores the data correctly: wc_order_addresses on HPOS, serialized postmeta on legacy.

The default Orders screen still shows one row per order, with multi-address detail buried inside the per-order edit view. For fulfilment, that's the wrong shape. The warehouse picker wants the next shipment to pack, not the next order to consider.

The account manager handling a 200-recipient corporate gift wants to see per-recipient status, not the order's grand total. The support agent on a call about a single recipient wants to look up the shipment by name, not the parent order. SleekView reads the per-address data and presents each shipment as a row in its own working table.

Filters, sorts, status transitions, tracking-number entry all happen at the shipment level. The parent order is still there, one click away. Same database, same hooks, the multi-address workflow finally fits the table.