Every status the plugin writes to _fedex_tracking, including Label Created, Picked Up, In Transit, and Delivered, plus any custom workflow status your team has registered. Each value renders as its own column the moment a shipment lands in it, so no manual mapping is required.

Yes. SleekView writes through the WooCommerce REST endpoints, the same path the admin uses. FedEx hooks fire as normal, so confirmation emails, carrier integrations, and refund flows behave exactly as if you had clicked the status dropdown manually in the order screen.

SleekView offers an optional confirmation prompt on drags into destructive columns, and any drag can be reverted by dragging back. The refund flow still runs through WooCommerce, so if your store auto-refunds on cancel, you can configure that to require manual approval first.

Yes. SleekView reads shipment state on a short interval and reconciles drags against the live record, so if a colleague has already moved a card, you see the new state before your drag conflicts. Optimistic updates revert cleanly if a write is rejected by the server.

Status is the grouping, but each card surfaces the carrier or location, service level, reference code, weight, and last scan, giving you the same visibility a carrier portal would without leaving the board. Filters let you scope to one carrier, one warehouse, or one shift.

Yes. Batch shipments and return labels expose the same status meta as outbound parcels, so both appear on the board with their parent order or return reference. A saved view per workflow keeps batches and returns visually separate from outbound shipments.

Yes. Save a filtered view for each warehouse, carrier, or service level and SleekView renders one board per saved view. Each board carries its own column counts and only writes back to the shipments in scope, so each dispatch screen stays focused on its own work.

Yes. SleekView only loads cards for the columns currently visible and paginates older shipments into a scroll-on-demand tail, so even stores with five years of history render the active columns instantly. Indexing on the status meta keeps group counts cheap.