SleekView for ShipWorks: warehouse handoff and tracking writeback as tables
SleekView reads the tracking, carrier, and shipped-state meta ShipWorks writes back to _shipworks_* keys on WooCommerce orders and renders one row per shipment. Audit pull queue, label state, and tracking inline.
♾️ Lifetime License available
Stop alt-tabbing to ShipWorks Hub for every lookup
ShipWorks pulls WooCommerce orders into its desktop or hub application, generates labels through its carrier integrations, and writes the resulting tracking numbers and carrier slugs back to WooCommerce. The writeback typically lands in _shipworks_tracking_number, _shipworks_carrier, and _shipworks_ship_date on the order. With HPOS active those values live in wc_orders_meta; without HPOS they live in postmeta.
The default WooCommerce Orders list shows none of those columns. Knowing whether ShipWorks has pulled an order or written tracking back requires opening each order. SleekView promotes the writeback meta into real columns: tracking number, carrier, ship date, and a derived shipped state. A view filtered to processing orders with empty _shipworks_tracking_number surfaces the pull queue. A view grouped by carrier with today's ship date is the dispatch handoff sheet.
Inline edits write back through WooCommerce CRUD so the tracking email and any third-party reader of the same meta key see the change identically to a ShipWorks Hub edit. The audit lives in WP Admin where support and finance already work.
Workflow
How SleekView reads your ShipWorks data
Pick the source
wc_orders on HPOS or shop_order on legacy. SleekView detects the active path and exposes _shipworks_* meta keys alongside core order fields.
Compose the column set
_shipworks_* keys your integration uses. Mix with status, customer email, and shipping country.
Save and gate per role
Edit inline and export
Sample columns
A typical ShipWorks audit view
wc_orders joined to the ShipWorks meta keys for carrier, tracking, and ship date.
wp_wc_orders + wp_wc_orders_meta (_shipworks_*)
| Order # | Customer | Carrier | Tracking # | Ship date | Status |
|---|---|---|---|---|---|
| #73120 | alex@studio.co | UPS | 1Z999AA10123456784 | Apr 24 | Shipped |
| #73118 | ria@design.io | FedEx | 7942 1112 3344 | Apr 24 | Shipped |
| #73116 | tom@hello.dev | USPS | (none) | (none) | Awaiting pull |
| #73112 | mia@brew.coop | DHL | EE123456789DE | Apr 22 | Label voided |
Comparison
Default ShipWorks integration vs SleekView
Default ShipWorks integration
- ShipWorks Hub lives outside WordPress with its own application
-
Order list shows neither carrier nor
_shipworks_tracking_number - Pull queue gaps are invisible from inside WP Admin
- Voided labels and re-pulls aren't a cross-store filter
- Cross-reference between ShipWorks data and Woo data is a CSV export
SleekView
- Carrier, tracking, and ship date as columns on every order
- Pull-queue audit as a saved view of unsynced orders
- Group by carrier for the daily warehouse handoff
- Inline-edit tracking for off-platform handovers without leaving WP
- Bulk-export per-carrier slices to CSV for finance reconciliation
Features
What SleekView gives you for ShipWorks for WooCommerce
Pull-queue audit
A saved view of Woo orders in processing with no _shipworks_tracking_number surfaces the orders ShipWorks hasn't pulled yet. Connectivity blips, mapping errors, and unmapped statuses stop being invisible.
Carrier handoff sheet
Group by _shipworks_carrier with today's ship date and export per courier. Each carrier picks up exactly the manifest they need, no spreadsheet munging required.
Inline tracking for off-platform handovers
Drop a tracking number into a row for a freight pickup or returns courier and the order-update hook fires through WooCommerce CRUD, triggering customer notifications as if ShipWorks had written it.
Audience
Who uses SleekView for ShipWorks
Warehouse operations
Group by carrier with today's _shipworks_ship_date for the dispatch handoff. The carrier picks up exactly the manifest they expect.
Customer support
Search by email and see carrier, tracking, and ship date inline. Reply with accurate state instead of opening the order to find the meta value.
Finance reconciliation
Filter to the month's shipped orders, group by carrier, and export. The shipping-cost reconciliation runs against the same data the warehouse used.
The bigger picture
Why ShipWorks data needs a WP-side row view
ShipWorks is a desktop-and-hub application that pulls Woo orders, generates labels, and writes tracking back. It is excellent at label generation and rate shopping, but its application is not where customer support fields where-is-my-package calls or where finance reconciles shipping invoices. Those workflows live in WordPress where the orders and customer records already are.
Without a tabular surface in WP Admin, every lookup requires opening the per-order screen or alt-tabbing to ShipWorks Hub. SleekView reads the writeback meta ShipWorks already populates and renders one row per order with carrier, tracking, and ship date. Saved views become the pull-queue audit, the carrier handoff, the finance reconciliation.
The Hub keeps owning labels and the carrier APIs, and WordPress gets the visibility for the teams that work inside it.
Questions
Common questions about SleekView for ShipWorks for WooCommerce
Yes when ShipWorks writes back to WordPress. The Hub is the application that generates labels; the integration writes tracking and carrier values back to order meta. SleekView reads those writeback meta keys.
Yes. Build a view of orders in processing with empty _shipworks_tracking_number older than your pull interval. Save it as Pull queue and run it on a schedule.
Yes. Edits write through WooCommerce CRUD so the order-update hook fires. Tracking emails, third-party readers, and audit trails see the change identically to a ShipWorks Hub edit.
Yes. On HPOS the ShipWorks meta moves to wc_orders_meta. SleekView reads from there automatically, and the same view config works on legacy stores via postmeta.
Yes. Filter to the relevant orders, paste tracking numbers from a CSV, and save. Each row writes through CRUD so notifications fire per order, useful for freight or returns handovers.
No. The Hub remains the label-generation and rate-shopping environment. SleekView is the WordPress-side row view for support, ops, and finance who shouldn't context-switch to the Hub for every lookup.
Re-pull is a Hub operation. SleekView can flag orders that haven't synced and mark them for re-pull through a meta update, but the actual pull runs from the Hub on its next cycle.
Yes. Any filtered or grouped slice exports as CSV with order, carrier, tracking number, ship date, and customer. Drop straight into a carrier manifest or finance import.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Yith Essential Kit
- Edd Fes Frontend Submissions
- Order Status Manager
- Flexible Shipping
- Woocommerce Product Csv Import
- Woocommerce Shipping Discount
- Woocommerce Gift Cards
- Woocommerce Correos
- Woocommerce Blockonomics
- Woocommerce Currency Converter
- Authorize Net
- Woocommerce Braintree
- Edd Conditional Emails
- Woocommerce Grouped Products Pro
- Woocommerce Eu Vat Number