Gooten's WooCommerce integration syncs products into the product custom post type and persists the Gooten product id, SKU, and last-synced timestamp in wp_postmeta. Orders carry the Gooten order id and fulfilment state in order meta (or wc_orders_meta on HPOS). The default Woo Products list shows none of that; Gooten SKUs live in a metabox or hide behind the Gooten dashboard.

SleekView reads wp_posts (post_type=product) and joins it with Gooten's meta keys, commonly _gooten_product_id, _gooten_sku, and _gooten_last_synced. Each row pairs a Woo product with its Gooten SKU and sync state. A sibling order view does the same for wc_orders, surfacing the Gooten order id and fulfilment status next to Woo's own status field.

Inline edits route through Woo CRUD for product and order fields, and through Gooten's hook where the integration exposes one. Bulk-update categories across a SKU family, or filter to orders stuck in production and trigger the integration's resync action without leaving WP Admin.

Gooten's catalogue is wide and the SKU families inside it move on their own schedule. A canvas size gets discontinued, a phone case template adds a new model, a blueprint changes its print method. The default integration sync handles those updates as a background job, but the result of that job (which Woo products are still valid, which need new images, which need to be removed from the storefront) isn't visible from the default Products list.

Catalogue managers end up opening products one at a time to read postmeta, or running spreadsheet reconciliations against exports from Gooten. SleekView pairs each Woo product with its Gooten SKU and sync state, and each Woo order with its Gooten order id and fulfilment status. Audits become filtered views, bulk edits go through Woo CRUD, and re-syncs ride the integration's existing hooks.

The Gooten dashboard keeps doing production. SleekView is the in-WP audit surface where catalogue, orders, and sync state line up next to each other.