WooCommerce stores global product attributes in wp_woocommerce_attribute_taxonomies, with each attribute generating a pa_* taxonomy whose terms live in wp_terms + wp_term_taxonomy. Swatch plugins add color, image, or label meta on each term via wp_termmeta. A store with eight global attributes can easily have several hundred terms across them.

SleekView reads all of those tables together: the attribute registry, the terms, the swatch meta, and a variation-usage count joined from wp_term_relationships. Build cross-attribute views like "All terms missing a swatch value", "Unused terms across all attributes", or "Attributes with the highest variation coverage". Or scope a view to one attribute (pa_color, pa_material) for a focused audit.

Inline edits write back to wp_termmeta through the WordPress term-meta API, so swatch caches refresh and the front end re-renders on the next page load. Bulk-update across a filtered set and each row's term-meta save fires the same hooks a manual term edit would.

WooCommerce attributes sprawl: a store with eight global attributes can have several hundred terms total, each with one or more swatch values, accumulated over years. The default WordPress taxonomy admin treats them as separate worlds, which is fine for setup and frustrating for audit. Catalog ops needs a cross-attribute "every term that's missing a swatch" view.

Merchandising needs a cross-attribute usage ranking. Cleanup needs unused terms surfaced across all taxonomies at once. SleekView reads the attribute registry, the terms, the swatch meta, and the variation-usage counts together, and lets each team save the cross-attribute view they actually need.

Inline edits write through the term-meta API so swatch caches and front-end rendering follow the same path as manual term edits. The data has always been there; SleekView gives it the workspace.