On WooCommerce attribute terms in termmeta, with the prefix the Variation Swatches plugin uses (typically swatch_ keys: swatch_type, swatch_color, swatch_image_id, swatch_tooltip). Per-product swatch overrides are stored as postmeta on the product with a related key pattern. SleekView reads both global term swatches and per-product overrides in the same grid so inconsistencies surface together.

No. SleekView edits the same termmeta keys the Variation Swatches plugin reads on the storefront. The plugin's storefront rendering, its frontend swatch picker, its caching layer and its theme integrations all continue to work exactly as before. Disabling SleekView leaves the swatch library untouched — the data is the plugin's, SleekView is just a faster admin layer for editing it.

Yes. Select rows and apply a value across them in one save. Common patterns include applying a single hex value to multiple terms (when a brand consolidates colors), applying tooltip text in batches with a template (when copy needs to be normalized) and clearing values across a set (when reverting to the plugin defaults). Each bulk save fires the same termmeta save hooks single-term saves do.

Yes. Image attachments can be picked inline with an attachment picker that opens in the cell. The current attachment thumbnail renders in the cell so merchandising can spot wrong images at a glance. Filters like "swatches with missing image" and "swatches pointing to deleted attachments" surface the cleanup work that otherwise hides inside individual term edits.

Yes. Any WooCommerce attribute taxonomy with swatch meta is supported, including custom taxonomies you have registered for things like Material, Finish or Size Range. The grid auto-detects which taxonomies have swatch metadata and shows them in the column picker. Custom swatch types added by other plugins (button, label, custom shape) appear as their own enum values in the swatch_type column.

No. SleekView only reads in admin — no queries fire on storefront page loads, on the frontend variation swatch picker or in any customer-facing flow. Edits made in SleekView write to the same termmeta the plugin reads, and the plugin's own caching layer (if you have object cache enabled) refreshes as it would after any standard term-edit save.

Yes. The grid can show both layers — global term swatches as one set of rows, per-product overrides as another. Filtering to overrides surfaces every place a product diverges from its global term defaults, which is where merchandising drift hides. Reverting an override to inherit the global value becomes a one-click action rather than navigating to the product, finding the variation, and editing the override there.

Yes. The Pro version's brand swatches and additional swatch types (radio buttons with images, custom HTML swatches) all store their data in termmeta with predictable key patterns. SleekView promotes those keys to columns alongside the standard color, image and tooltip fields. Brand-level swatches that span multiple attributes also surface, which helps brands managing licensed palettes across categories.