SleekView for BigCommerce Bridge: synced catalog & orders as tables
SleekView reads the bridge's per-product postmeta (_bc_product_id, _bc_channel_id, _bc_synced_at) and the channel cache in wp_options. Sort by sync status, filter by channel, and re-map products inline.
♾️ Lifetime License available
BigCommerce channel state where editors actually look
BigCommerce's headless model has WordPress as the storefront and BigCommerce as the catalog + checkout. The official and community bridges expose products in WP via a custom post type or by mirroring to product, with per-row meta tracking the BigCommerce side: _bc_product_id, _bc_channel_id, _bc_synced_at, _bc_visibility. The default Products screen doesn't show any of it.
SleekView reads wp_posts (whichever post type the bridge uses) joined with those meta keys, plus the channel cache in wp_options (bigcommerce_channels). The result is a single table showing the WP post, BigCommerce product ID, target channel name, sync status, and last-sync timestamp side by side, sortable and filterable.
Bulk actions can re-pull a filtered subset by firing the bridge's bigcommerce_resync_product hook on each row. Inline edits to _bc_visibility or channel assignment flow through update_post_meta() and the bridge syncs the change on its next cron tick.
Workflow
How SleekView reads your BigCommerce Bridge state
Pick the source
bigcommerce_product, product, or custom). SleekView lists the BC meta keys in use.
Compose columns
bigcommerce_channels, visibility flag, and last-sync timestamp.
Save and scope per role
Edit inline or bulk-update
bigcommerce_resync_product on a filtered subset. The bridge picks up changes on the next cron.
Sample columns
A typical BigCommerce Bridge view
_bc_product_id and _bc_channel_id against bridge-managed product rows so every entry shows its current sync state.
wp_posts (post_type=bigcommerce_product or product) + wp_postmeta + wp_options
| WP post | BC product ID | Channel | Visibility | Sync status | Last sync |
|---|---|---|---|---|---|
| Black tee shirt | 44218 | Web (US) | Visible | In sync | Apr 24 |
| Ceramic mug | 44219 | Web (EU) | Hidden | Pending | Apr 24 |
| Art poster A2 | Web (US) | Hidden | Unmapped | ||
| Natural tote bag | 44221 | Web (US) | Visible | In sync | Apr 23 |
Comparison
Default BigCommerce Bridge admin vs SleekView
Default BigCommerce Bridge admin
-
Channel and visibility meta in
_bc_channel_idand_bc_visibilityisn't shown in the post list - Bridge dashboard shows totals, not per-row sync state
- Multi-channel stores need separate clicks per channel to verify state
-
Unmapped products (empty
_bc_product_id) only surface after a failed checkout test - No filter for "hidden on EU channel" without writing a custom meta query
SleekView
-
Reads
_bc_product_id,_bc_channel_id,_bc_visibility,_bc_synced_atas columns - Filter by channel and visibility in a single saved view
-
Inline-edit
_bc_visibilityper row, per channel -
Bulk-trigger
bigcommerce_resync_producton broken mappings - Switch to kanban grouped by channel for multi-region merchandising
Features
What SleekView gives you for BigCommerce Bridge for WordPress
Per-channel state as columns
Channel ID, visibility flag, and last-sync timestamp per channel on every product row. Multi-region stores see at a glance which products show where.
Toggle visibility inline
Flip _bc_visibility right in the row. The bridge picks up the change on its next sync and updates the BigCommerce channel API accordingly.
Filter unmapped products
Save "Empty BC product ID this week" as a recurring view. Catalogue leads catch missing mappings before they break a checkout.
Audience
Who uses SleekView for BigCommerce Bridge
Multi-region merchandisers
Group by channel to see US vs EU vs APAC catalogue state. Inline-toggle visibility for region-specific launches without per-product clicks.
Integration engineers
Filter for unmapped rows (empty _bc_product_id) and trigger initial sync in bulk. The bridge's existing retry path handles rate limits.
Support
When a customer reports a product missing from the storefront, check the row's channel visibility and sync state. Most tickets resolve without escalating to engineering.
The bigger picture
Why headless BigCommerce ops need better dashboards
BigCommerce-on-WordPress setups are usually headless, with the storefront in WP and the catalog and checkout in BigCommerce. The bridge holds them together with a per-product mapping and a channel cache. The bridge itself scales fine for the data volumes most stores see.
The pain is operational: editors think of products in WP, but the actual visibility and inventory state lives across the bridge in BigCommerce, and the default WP admin doesn't reflect any of it. A product can be unmapped, hidden on one channel, or pending sync without any visible signal. SleekView pulls the bridge's own meta into a sortable, filterable list so catalogue managers, merchandisers, and engineers see the same state, on the same screen, in WP.
The bridge keeps doing its job; SleekView makes its work legible to the humans running the store.
Questions
Common questions about SleekView for BigCommerce Bridge for WordPress
Yes. The official plugin uses the bigcommerce_product post type and writes mapping meta like bigcommerce_id and channel data. SleekView's agent UI detects the actual keys in use on your install and exposes them as columns.
Yes, if the bridge exposes a hook like bigcommerce_resync_product. SleekView calls that hook per selected row. The bridge handles API rate limits the same way it does for its own buttons.
BigCommerce channels are cached in wp_options under bigcommerce_channels by most bridges. SleekView resolves _bc_channel_id against that cache so the column shows readable labels like "Web (US)" instead of raw IDs.
Yes. If your bridge stores visibility as a per-channel array (_bc_visibility_by_channel) or one row per channel, SleekView unpacks it and lets you filter or edit per channel.
Inline edits update WP postmeta via update_post_meta(), which fires standard hooks. Bridges that listen on those hooks propagate the change to BigCommerce on the next sync; others do it on the regular cron run.
Yes. Build a tabbed SleekView page with separate sources for products and orders. Each tab joins the relevant _bc_* meta to its own post type.
If the bridge logs webhook deliveries (often in _bc_last_webhook or a small custom table), SleekView can surface them as columns or as a separate view. Useful for debugging "why didn't the order arrive" tickets.
Queries hit indexed postmeta keys. For multi-region catalogues with many channels, narrow with a channel filter first. Per-channel aggregate columns are opt-in to keep the default list responsive.
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
- Edd Reviews
- Woocommerce Advanced Bulk Edit
- Woocommerce Packlink Pro
- Wp Crowdfunding
- Skubana Wp
- Woocommerce Glsship
- Amazon Product Importer
- Woocommerce Quotes Orders
- Woocommerce Wholesale Payments
- Woocommerce Inventory Pro
- Woocommerce Wholesale Prices
- Woocommerce Zip Checkout
- Woocommerce Product Table
- Easy Digital Downloads
- Woocommerce Mix And Match