SleekView for Skubana WP Connector: orders & shipment binds as tables
SleekView reads the connector's per-order postmeta (_skubana_order_number, _skubana_warehouse_id, _skubana_shipment_id) and the warehouse cache in wp_options. Sort by warehouse, filter by push status, and re-route stuck orders inline.
♾️ Lifetime License available
Order routing visible where the orders live
Skubana (now Extensiv Order Manager) handles multi-warehouse fulfilment for high-volume WooCommerce stores. Its WP connector pushes orders out and pulls shipment data back, writing a handful of meta keys per order. The default WP Orders screen shows none of this, so a question like "which orders are stuck before warehouse pickup" turns into a connector-log scroll.
SleekView reads wc_orders (HPOS) or legacy shop_order posts joined with the Skubana meta keys plus the warehouse map cached in wp_options under skubana_warehouse_map. Each order row carries its Skubana order number, target warehouse name, push status, and shipment ID side by side.
Bulk actions can fire the connector's own skubana_resync_order hook through SleekView, so resyncs follow the connector's existing retry path and webhooks. Edits to _skubana_warehouse_id propagate the same way a manual change in the order edit page would.
Workflow
How SleekView reads your Skubana routing state
Pick the source
wc_orders on HPOS or shop_order on legacy. SleekView detects the active schema and lists the Skubana meta keys actually in use.
Compose columns
skubana_warehouse_map, Skubana order number, shipment ID, and push status.
Save and scope per role
Edit inline or bulk-update
_skubana_warehouse_id inline or trigger skubana_resync_order on a bulk selection. The connector picks up changes on its next cron.
Sample columns
A typical Skubana routing view
_skubana_order_number and _skubana_warehouse_id against orders so every row shows its current routing state.
wp_wc_orders + wp_wc_orders_meta + wp_options (or wp_posts shop_order + wp_postmeta on legacy)
| Order # | Warehouse | Skubana # | Shipment | Push status | Updated |
|---|---|---|---|---|---|
| #30144 | NJ-East | SK-441-882 | TRK-99214 | Shipped | Apr 24 |
| #30143 | CA-West | SK-441-881 | Routing | Apr 24 | |
| #30142 | TX-Central | Push failed | Apr 23 | ||
| #30141 | NJ-East | SK-441-879 | TRK-99211 | Shipped | Apr 23 |
Comparison
Default Skubana WP Connector admin vs SleekView
Default Skubana WP Connector admin
-
Routing meta lives in
_skubana_order_number,_skubana_warehouse_id,_skubana_shipment_id - Connector page shows recent activity, not a per-order routing dashboard
-
Warehouse IDs need manual lookup against
skubana_warehouse_mapoptions - No filter for "orders pushed but not yet shipped" without writing SQL
- Resync requires opening orders one at a time or running the connector's batch tool
SleekView
-
Reads
_skubana_warehouse_id,_skubana_order_number,_skubana_shipment_idas columns - Resolve warehouse codes to names via the options cache
-
Bulk-trigger
skubana_resync_orderon a filtered subset - Save "Push failed today" as a recurring view for the ops shift
- Switch to kanban grouped by warehouse for picking handoff
Features
What SleekView gives you for Skubana WP Connector
Routing meta as columns
Skubana order number, warehouse, and shipment ID appear in the same row as the WooCommerce order. The relationships hidden in postmeta become a single readable line.
Bulk resync without the connector page
Select failed pushes and fire the connector's skubana_resync_order hook. The retry runs through the connector's standard API path and webhooks.
Filter by warehouse and state
Combine warehouse, push status, and date range into a saved view. "NJ-East pending today" becomes one click for the warehouse lead.
Audience
Who uses SleekView for Skubana WP Connector
Multi-warehouse ops
Group by warehouse to plan picking. Reroute mis-assigned orders by editing _skubana_warehouse_id inline and triggering resync on the row.
Integration engineers
Filter for orders with empty _skubana_order_number to find pushes that never succeeded. Resync in bulk and watch the column fill in on the next cron.
Support
When a customer asks for tracking, search the order and see Skubana number plus shipment ID without opening the connector. Hand the tracking link over and move on.
The bigger picture
Why Skubana ops blow up the default WP admin
Skubana sits behind multi-warehouse, multi-channel stores doing real volume, and the WP connector is one piece of a pipeline that includes carriers, marketplaces, and 3PLs. The connector itself scales fine because it writes a small set of meta per order and a cached warehouse map in options. The operational scaling problem is that the default WP Orders screen doesn't reflect any of this state.
Warehouse leads see "Processing" on orders that are stuck before push, support sees "Shipped" with no tracking link visible, and integration engineers can't filter for orders that need resync without raw SQL. SleekView exposes the connector's meta as columns and saved filters, so the routing state becomes part of the order's normal admin surface. The connector keeps doing what it does, the data path doesn't change, but the people who manage the operation finally see it.
Questions
Common questions about SleekView for Skubana WP Connector
Yes. Skubana meta is written to wc_orders_meta on HPOS or postmeta on legacy. SleekView reads from whichever schema is active without config changes.
Yes. Bulk actions can fire do_action('skubana_resync_order', $order_id), the same hook the connector's own resync button uses. The actual API call happens on the next cron tick.
The connector caches its warehouse map in wp_options under skubana_warehouse_map. SleekView resolves _skubana_warehouse_id values against that map so the column shows readable labels.
Skubana stores shipment IDs as _skubana_shipment_id on the parent order. Multi-package orders may have a serialised array; SleekView unpacks it and shows one row per shipment when configured to.
Yes. The agent UI scans actual meta keys on shop_order or wc_orders rows and lists them all. Add tracking, fraud, or CRM keys alongside Skubana ones in the same view.
Returns flow through the connector's return webhook, which writes _skubana_return_status on the original order. Add that column to the view to spot returns in progress without a separate report.
Filters and sorts use indexed columns on wc_orders. Meta joins for Skubana keys are scoped to active orders by default; very large historical filters should rely on date-range narrowing first.
Yes. SleekView surfaces what the Skubana connector stores; it doesn't talk to Skubana directly. With the connector active, the data is there and SleekView makes it visible.
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
- Woocommerce Packlink Pro
- Woocommerce Pinterest Feed
- Woocommerce Quickbooks Sync
- Woocommerce Invoice System
- Woocommerce Composite Products
- Instamojo
- Woocommerce Octobat
- Woocommerce Frontend Manager
- Woocommerce Allegro Pl
- Woocommerce Amazon Feed
- Stripe For Woocommerce
- Woocommerce Cart Abandonment Recovery
- Yith Woocommerce Wishlist
- Woocommerce Gift Ultimate
- Woocommerce Referrals
- Wishlist Member X
- Cimy User Extra Fields
- Paid Member Subscriptions
- Super Socializer
- Membership 2 Pro
- Restrict Content
- Loginpress Pro
- Woocommerce Paid Courses
- Restrict User Access
- Memberium Active Campaign
- Content Restriction By Userrole
- Memberium
- Profilepress
- Thrive Apprentice
- Woocommerce Memberships