✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Stitch Labs WP Connector: synced inventory & orders as tables

SleekView reads the connector's stored mapping in wp_options and the per-product SKU bindings in wp_postmeta so every WooCommerce product shows its Stitch SKU, last sync, and channel pushes inline. Sort by sync status, filter by channel, and fix mismatches without opening each product.

♾️ Lifetime License available

SleekView table view for Stitch Labs WP Connector

Inventory sync that doesn't end at "Connected"

The Stitch Labs WP Connector sits between WooCommerce and the Stitch Labs (now part of ShipBob Merchant Plus) inventory hub. Its default WP screens give a connection status and a log, but the per-product mapping it writes to wp_postmeta (keys like _stitch_sku, _stitch_last_sync, _stitch_channel_ids) is hidden behind each product edit page. When a SKU stops syncing, finding the culprit row means opening products one at a time.

SleekView reads wp_posts for product rows joined with the Stitch postmeta keys and the connector's settings cache in wp_options (stitch_connector_settings, stitch_channel_map). The result: a single table showing SKU, Stitch SKU, channel push status, last sync timestamp, and current stock side by side, sortable and filterable.

Inline edits update _stitch_sku or toggle _stitch_sync_enabled through WordPress's standard update_post_meta() path, so the connector's stitch_after_meta_update hook still fires on the next cron tick. Bulk-disable sync on a hundred discontinued SKUs in one pass instead of clicking through products.

Workflow

How SleekView reads your Stitch Labs sync state

1

Pick the source

Choose wp_posts with post_type=product as the base and let SleekView auto-detect the Stitch postmeta keys in use on your store.
2

Compose columns

Add columns for SKU, _stitch_sku, channel labels resolved from stitch_channel_map, current stock, and _stitch_last_sync.
3

Save and scope per role

Save a "Failed syncs" view scoped to the shop-manager role, and a broader "All mappings" view scoped to admins only.
4

Edit inline or bulk-update

Fix individual SKUs in the row, or bulk-toggle _stitch_sync_enabled on a filtered subset. The connector's next cron picks up the change.

Sample columns

A typical Stitch Labs sync view

SleekView joins wp_postmeta keys like _stitch_sku and _stitch_last_sync against the product post type so every row shows its real mapping state.
Source: wp_posts (post_type=product) + wp_postmeta + wp_options
SKU Stitch SKU Channels Stock Sync status Last sync
SHIRT-BLK-M STCH-44218 Web, Amazon 42 Synced Apr 24
MUG-CER-WH STCH-44219 Web, eBay 18 Pending Apr 24
POSTER-A2 STCH-44220 Web 0 Failed Apr 22
TOTE-NAT STCH-44221 Web, Amazon, eBay 126 Synced Apr 24

Comparison

Default Stitch Labs WP Connector admin vs SleekView

Default Stitch Labs WP Connector admin

  • Mapping data lives in _stitch_sku and _stitch_channel_ids postmeta, hidden inside each product
  • Connection status screen shows global state, not per-product sync health
  • No filter for "failed sync since X" without a custom SQL query
  • Fixing a broken SKU mapping requires opening the product edit screen
  • Channel push state in wp_options isn't exposed in any list view

SleekView

  • Reads _stitch_sku, _stitch_last_sync, _stitch_channel_ids as first-class columns
  • Filter by sync status, channel, or last-sync date in one pass
  • Inline-edit the Stitch SKU or toggle _stitch_sync_enabled per row
  • Save "Failed syncs this week" as a named view for the ops shift
  • Group products by channel push status using a kanban view

Features

What SleekView gives you for Stitch Labs WP Connector

Real mapping data as columns

Pull _stitch_sku, _stitch_last_sync, and the channel-id array from wp_postmeta alongside the product's own SKU and stock. The misalignments that cause sync failures become obvious at a glance.

Edit mappings inline

Fix a wrong Stitch SKU directly in the row. Inline writes go through update_post_meta() so the connector's next cron run picks up the change without a manual resync.

Filter by sync health

Combine sync status, channel, and last-sync date into one filter. "Failed syncs to Amazon since Monday" becomes a saved view that any team member can open.

Audience

Who uses SleekView for Stitch Labs WP Connector

Inventory ops

Filter by _stitch_sync_enabled = false to find products that fell off sync, then bulk-re-enable. Last-sync timestamps make stale rows obvious without opening the connector log.

Multi-channel managers

Group by _stitch_channel_ids to see which products push to Amazon, eBay, and the web store. Add or remove channel IDs inline when a listing moves.

Support

When a customer reports "out of stock" on a channel, search by SKU and see Stitch sync status, current stock, and last sync without leaving the support queue.

The bigger picture

Why Stitch Labs ops blow up the WP default admin

The Stitch Labs WP Connector scales fine technically because it stores a small set of postmeta keys per product and a single options record for global state. Operationally it falls apart the moment a SKU stops syncing, because the failure is buried in _stitch_last_sync on one product among thousands. Inventory teams end up running ad-hoc SQL through phpMyAdmin to find the bad rows, then reopening each product to fix the mapping.

SleekView turns that workflow into a single saved view: filter by sync status, see the affected SKUs, fix inline, move on. Multi-channel sellers also need to know which products push to which channel without diffing options serialisations by hand. The same view answers that question by unpacking _stitch_channel_ids into readable labels.

None of this requires changes to the connector, it just reads what's already there. The result is fewer support tickets about phantom stock and faster recovery when an API key rotates or a channel mapping drifts.

Questions

Common questions about SleekView for Stitch Labs WP Connector

Yes. SleekView reads the postmeta keys the connector writes, so the connector still has to be installed and authenticated. SleekView itself doesn't talk to the Stitch Labs API directly, it surfaces what the connector stores.

 

Yes. Inline writes update _stitch_sku via update_post_meta(), the same path the connector uses internally. The connector's next scheduled sync will use the new mapping.

 

The connector stores channel IDs as a serialised array in _stitch_channel_ids. SleekView unpacks them and renders a label per channel using the mapping cached in wp_options under stitch_channel_map.

 

Not directly. SleekView updates the postmeta and the connector's own cron picks up the change on the next tick. If you need an immediate push, the connector exposes a manual sync button that still works.

 

Yes. The agent UI scans wp_postmeta for keys actually in use on product rows, so meta added by shipping, tax, or analytics plugins shows up in the column picker alongside the Stitch keys.

 

The connector writes a single last-sync timestamp, not a history. SleekView surfaces that timestamp; for full history you'd need the connector's log table or a custom audit setup.

 

HPOS affects wc_orders, not wp_posts. Stitch mappings live on the product post type and its postmeta, so SleekView's product-side views are unaffected by HPOS state.

 

Stitch postmeta is product-level, not customer-level, so it isn't part of WordPress's personal-data export. SleekView's own per-view export uses the same capability checks as WP Admin so admin-only data stays admin-only.

 

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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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