In wp_termmeta on the pa_color term. The exact meta key depends on the swatch plugin: common keys are product_attribute_color and swatch_color. SleekView lists meta keys actually in use on your terms so you don't have to guess.

Yes. SleekView joins wp_term_relationships with wp_term_taxonomy to count posts (variations and products) per term and exposes that count as a sortable column. Useful for both audit (find unused) and merchandising (find dominant palette colors).

Yes. SleekView writes through the WordPress term-meta API, so caches that listen on term-meta updates (object cache, swatch plugin's own cache) refresh on the next request. Front-end swatches re-render with the new hex or image on the next page load.

Image swatches reference an attachment id stored in wp_termmeta under a plugin-specific key. SleekView surfaces the attachment id, name, and a thumbnail preview in the row, and inline-edit lets you select a new attachment from the media library.

Yes. Filter to the relevant subset (e.g. "hex missing" or "by group tag"), select all, and inline-edit the hex column. Each row writes through the term-meta API so any cache that listens on term-meta updates fires per row.

Yes. Any pa_* attribute taxonomy can be the source. pa_material, pa_finish, or any custom global attribute with associated wp_termmeta swatch values follows the same schema and the same view configuration.

Queries hit indexed columns on wp_terms and wp_term_taxonomy, with wp_termmeta joined on the indexed term_id + meta_key path. Usage counts use indexed joins on wp_term_relationships. Even very large attribute sets stay responsive.

Yes. The catalog audit view is gated by capability, so a catalog-ops role can edit hex values while merchandising can read but not edit. WordPress capabilities map to view permissions one-to-one.