SleekView for ShipStation: order sync state, labels & tracking as tables
Read tracking numbers, carriers, and label state from order meta (_tracking_number, _shipstation_*) and join to wc_orders for a single row that shows where every shipment is. Sort, filter, edit inline.
♾️ Lifetime License available
Stop opening orders to find a tracking number
The ShipStation for WooCommerce integration synchronises orders to ShipStation, then writes tracking numbers, carrier codes, and shipment timestamps back into the WordPress order. Depending on plugin version and configuration, those values land in keys like _tracking_number, _shipstation_carrier, _shipstation_service, and on HPOS, the equivalent rows in wc_orders_meta.
The default Orders list shows none of these. Customer support fielding a "where's my package" call has to open the order to read the tracking number. Operations staff can't tell at a glance which orders have shipped, which are still in ShipStation queue, and which never synced. SleekView surfaces the tracking number, carrier, and sync timestamp as real columns. A support view filters by customer email and shows tracking inline. An ops view filters by "orders processing for more than 24 hours without a tracking number" — the early signal of a sync problem.
Inline edits write back through CRUD so a manually entered tracking number for a non-ShipStation handover (a one-off freight pickup, a returns label) updates customer-notification triggers exactly as the per-order screen would. Bulk operations across many orders take seconds.
Workflow
How SleekView reads your ShipStation data
Pick the source
wc_orders (HPOS) or shop_order (legacy). SleekView detects the active path and exposes ShipStation writeback meta alongside core order fields.
Compose your column set
_shipstation_* keys your integration uses. Mix with status, date, total, and address.
Save and scope the view
Edit inline and notify
Sample columns
A typical ShipStation tracking view
wp_wc_orders + wp_wc_orders_meta (_tracking_*, _shipstation_*)
| Order # | Customer | Carrier | Tracking # | Synced | Shipment status |
|---|---|---|---|---|---|
| #11045 | alex@studio.co | DHL Express | EE123456789DE | Apr 24 | Shipped |
| #11042 | ria@design.io | USPS | 9405511899223876543 | Apr 24 | Shipped |
| #11038 | tom@hello.dev | — | — | Apr 23 | In ShipStation queue |
| #11035 | mia@brew.coop | UPS | 1Z999AA10123456784 | Apr 23 | Shipped |
| #11030 | leo@atelier.fr | — | — | — | Not synced |
Comparison
Default ShipStation integration vs SleekView
Default ShipStation
- Tracking number and carrier visible only on the per-order screen
- No filter for "orders not yet synced to ShipStation"
- Sync state isn't a column — you find out by absence of a tracking number
- Bulk-adding tracking numbers for non-ShipStation handovers requires CSV import
- ShipStation's own UI is the dashboard, but it's a context switch from WordPress
SleekView
- Surface tracking number, carrier, and service as columns alongside order data
- Filter for orders not yet synced as an early-warning sync-failure view
- Inline-edit tracking and carrier — useful for non-ShipStation handovers
- Bulk-update tracking across many orders without leaving WordPress
- Save support and ops views with their own column sets and filters
Features
What SleekView gives you for ShipStation for WooCommerce
Tracking and carrier as real columns
Pull _tracking_number, _shipstation_carrier, _shipstation_service, and the sync timestamp into the row. Support sees what they need without opening orders; ops audits sync coverage at a glance.
Catch sync failures early
A saved view of "orders processing for over 24 hours without tracking" surfaces the orders ShipStation didn't pick up — connectivity, mapping, or rate issues — before customers chase support.
Inline edits for one-off handovers
Sometimes a freight forwarder, a returns courier, or a manual handover happens outside ShipStation. Drop the tracking number directly into the row and customer-notification hooks fire as if ShipStation had written it.
Audience
Who uses SleekView for ShipStation
Customer support
When a tracking question comes in, search by email and see carrier, tracking, and sync timestamp inline. Update or correct the tracking mid-call without opening the order.
Fulfilment ops
An audit view of "orders Processing without sync" runs three times a day. Sync gaps surface in seconds, not when a customer chases. Bulk-trigger re-sync or note them for ShipStation support.
Operations management
Carrier breakdown by date, average time-to-sync, and shipped-vs-pending count by warehouse all become saved views. Run them weekly to spot drift in shipping performance.
The bigger picture
Why ShipStation data deserves a row in WordPress
ShipStation does the heavy lifting for shipping — rate shopping across carriers, label generation, pick-pack flow, returns. The WooCommerce integration is the bridge: orders flow out, tracking numbers flow back. But once tracking is back in WordPress, it sits in order meta where only the per-order screen can see it.
Customer support fielding a tracking question opens the order. Ops auditing sync coverage opens the order. Finance reconciling shipped-vs-paid opens the order.
Each of those workflows lives in WordPress, not in ShipStation's dashboard, and forcing the team to context-switch back to ShipStation for every lookup adds friction. SleekView reads the meta ShipStation already writes — tracking, carrier, service, sync timestamp — and surfaces it as a row in WordPress. Saved views become the support lookup, the ops audit, the finance reconciliation.
ShipStation keeps doing what it's good at; WordPress gets the visibility it always lacked. Same data, dramatically less clicking.
Questions
Common questions about SleekView for ShipStation for WooCommerce
Yes. SleekView surfaces _tracking_number, _shipstation_carrier, _shipstation_service, and any related meta the integration writes back. The agent UI scans your installation and lists the keys actually in use, so you pick from the real list rather than guessing.
Yes. Build a view of orders in Processing status with no tracking number and a created-date older than your sync interval. Save it as "Sync gaps" and run it on a schedule. Sync failures stop being invisible — they're a one-click filter.
Yes. Tracking writes go through WooCommerce CRUD, so the order-update hook fires. If your store sends a tracking email on update — many themes and plugins do — it sends from a SleekView edit the same as from the per-order screen. Bulk edits trigger per-row hooks, not a single batched event.
Yes. On HPOS, ShipStation's writeback meta moves to wc_orders_meta. SleekView reads the active path. The same view config works whether you've migrated to HPOS or not.
Yes. Filter to the orders, select them, paste tracking numbers from a courier CSV (or type them), and save. Each row writes through CRUD. Useful for freight pickups, returns, or any handover ShipStation didn't process — without opening individual orders.
It reads what the integration writes back into WordPress. ShipStation's own internal statuses (awaiting shipment, shipped, on-hold) only appear in WordPress when the integration syncs them. If your setup writes those back, SleekView surfaces them; if not, the view shows what's in WP and you check ShipStation's UI for finer-grained internal state.
ShipStation's re-sync is typically initiated from the order's WooCommerce action menu. SleekView exposes order actions in the row's action menu, so re-sync fires per row from the table view. Bulk re-sync depends on whether the ShipStation plugin exposes a batch action — most modern versions do.
No — ShipStation's own dashboard remains where the bulk of label generation, carrier rate shopping, and pick-pack workflows happen. SleekView is the WordPress-side row view that gives support, finance, and ops the data they need without the ShipStation context switch.
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 checkout