✨ 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 TradeGecko WP: synced inventory & orders as tables

The TradeGecko connector synced stock levels, product variants, and sales-order records from QuickBooks Commerce into WordPress. SleekView reads those rows so inventory ops teams can audit sync state and stock movements without per-product clicks.

♾️ Lifetime License available

SleekView table view for TradeGecko for WordPress

Synced inventory data, surfaced as tables

TradeGecko (now QuickBooks Commerce) connectors for WordPress kept stock levels, variant mappings, and sales-order history synced into WooCommerce. The data typically lives across wp_posts (variant products), wp_postmeta (TradeGecko-specific keys such as _tradegecko_variant_id, _tradegecko_sku, _tradegecko_committed, _tradegecko_last_synced), and the WooCommerce order tables (wp_wc_orders or wp_posts (shop_order)) for sales-order records that pushed back to TradeGecko.

The default WooCommerce admin shows stock as a single number per variant and hides TradeGecko's view of the world (committed, on order, allocated by warehouse, last sync timestamp) inside the variant detail. For a small catalog that is fine. For a multi-warehouse catalog with hundreds of variants and constant sync activity, an inventory lead needs to see all variants where committed exceeds available, all variants that have not synced in 24 hours, and all sales orders waiting on a TradeGecko fulfilment update on one screen.

SleekView pivots the TradeGecko meta keys into proper columns and joins variants with the sales-order rows that committed their stock. Inline edits cover the internal fields the connector exposes (notes, manual override flags). Stock adjustments and reorder logic stay in the TradeGecko/QuickBooks Commerce backend since those are the canonical source.

Workflow

TradeGecko sync data as one inventory workspace

1

Pick the base resource

Start from the product-variation CPT for stock-level views, or from wp_wc_orders for sales-order audit. SleekView detects whichever connector keys (tradegecko_* or qbc_*) are present.
2

Add the connector columns

Expose _tradegecko_sku, _tradegecko_committed, _tradegecko_last_synced, and any warehouse-allocation keys as columns. Join variants with the sales orders that committed their stock.
3

Save the inventory views

Oversold queue, stale-sync watchlist, per-warehouse allocation, and sales-order push audit. Each gated to inventory ops, fulfilment, or finance via WordPress capability.
4

Audit, do not write

Stock adjustments stay in TradeGecko (or QuickBooks Commerce) so the connector's bi-directional sync stays clean. SleekView is the read-side audit surface, with internal fields like notes and override flags writeable.

Sample columns

A typical TradeGecko-synced inventory view

Pivots _tradegecko_* postmeta keys and joins variants with sales-order commitments.
Source: wp_posts (product_variation) + wp_postmeta + wp_wc_orders / wp_posts (shop_order)
SKU Variant On hand Committed Available Last synced Status
BAG-RED-S Bag, Red, S 48 12 36 May 16 09:42 Synced
BAG-RED-M Bag, Red, M 5 8 -3 May 16 09:42 Oversold
BAG-BLU-S Bag, Blue, S 120 4 116 May 14 18:11 Stale
BAG-BLU-M Bag, Blue, M 0 0 0 May 16 09:42 Out

Comparison

Default TradeGecko sync admin vs SleekView

Default TradeGecko sync admin

  • _tradegecko_* keys live in postmeta, not in the product list
  • Committed and available stock hide in variant detail screens
  • No saved view for oversold variants across the catalog
  • Stale-sync detection (variants not synced in 24 hours) requires custom code
  • Per-warehouse stock allocation needs CSV exports from TradeGecko

SleekView

  • Pivot _tradegecko_committed, _tradegecko_sku, _tradegecko_last_synced into columns
  • Saved view for oversold variants (available below zero)
  • Stale-sync watchlist filtered by _tradegecko_last_synced
  • Join variants with the sales-order rows that committed their stock
  • Per-warehouse allocation columns where the connector stored that data

Features

What SleekView gives you for TradeGecko for WordPress

Oversold detection

Filter the variant base where _tradegecko_committed exceeds stock_quantity. The oversold queue is one saved view away, not a SQL query.

Stale-sync watchlist

Sort by _tradegecko_last_synced ascending and filter to the variants that have not synced in 24 hours. Flags broken syncs before they cause oversells.

Variant plus sales-order join

Join product variants with the sales-order line items that committed their stock. See the open commitments per SKU in one row.

Audience

Who uses SleekView for TradeGecko WP

Inventory ops

Oversold queue, stale-sync watchlist, and per-warehouse stock allocation in one workspace. Resolves sync drift before orders ship with wrong stock numbers.

Fulfilment

Open sales orders joined with their TradeGecko variant data. Confirm stock available before picking, especially for orders queued during a sync gap.

Finance and reporting

Committed-versus-available audit across the catalog, with last-sync timestamp visible. Inventory valuation reports run faster when the source data is already joined.

The bigger picture

Why multi-warehouse inventory needs a flat audit view

Inventory management on a multi-warehouse catalog runs on small, frequent decisions: which SKUs are at risk of oversell, which variants have not synced recently, which sales orders are waiting on a stock confirmation. The TradeGecko connector keeps WooCommerce stock aligned with the canonical inventory backend, and the data needed for those decisions is already in WordPress tables. The default WooCommerce admin reduces stock to one number per variant and hides committed, on-order, and last-sync timestamps in the variant detail screen.

That works for a 50-SKU catalog and fails at 500. SleekView pivots the TradeGecko meta into proper columns and lets inventory ops, fulfilment, and finance each run the saved views that fit their job. Oversold queue, stale-sync watchlist, sales-order push audit, per-warehouse allocation, and committed-versus-available audit all become single filters.

Inline edits stay narrowly scoped to internal fields (notes, override flags) because the canonical stock numbers belong to TradeGecko. The connector keeps doing its job, the WooCommerce admin keeps its familiar product list, and SleekView gives the inventory team the joined audit surface a busy catalog needs.

Questions

Common questions about SleekView for TradeGecko for WordPress

TradeGecko was acquired and rebranded as QuickBooks Commerce, and the WordPress connector lineage continued under that name and a few community forks. SleekView reads whichever tradegecko_* or qbc_* meta keys are present on variants and orders, so existing installs keep working with the same column mapping.

 

No. It reads only the data the connector has already synced into WordPress tables. Stock adjustments and re-syncs stay in the connector and the TradeGecko/QuickBooks Commerce backend.

 

Inline edits to WooCommerce stock fields are possible but will conflict with the next sync from TradeGecko. The right pattern is to push the adjustment in TradeGecko and let it sync down, and SleekView is the audit surface that confirms the sync landed.

 

Where the connector wrote per-warehouse allocations into postmeta or a custom table, SleekView surfaces those as columns. The exact key shape depends on the connector version, and the column picker scopes to keys actually present in the data.

 

Yes. Filter variants by _tradegecko_last_synced below a threshold (last 24 hours, last 6 hours). Variants that fall behind that line are the broken-sync watchlist.

 

The connector typically writes a _tradegecko_sales_order_id on the WooCommerce order after the push. Surface that column to confirm every paid order pushed back into TradeGecko successfully.

 

Yes. SleekView reads wp_wc_orders and wp_wc_orders_meta under HPOS, picking up the TradeGecko keys from order meta. Variant data continues to live in the product CPT regardless of HPOS state.

 

Intuit deprecated QuickBooks Commerce for new customers but kept the API for existing connectors. Several community-maintained WordPress connectors remain. SleekView's mapping does not assume one specific connector vendor, only that the standard _tradegecko_* or _qbc_* keys are written on variants and orders.

 

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