✨ 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 WooCommerce Customizer: option overrides as a single audit table

WooCommerce Customizer stores its label, button, and message overrides as keyed entries in wp_options. SleekView surfaces every override as a row so you audit, search, and edit copy in one place instead of clicking through admin tabs.

♾️ Lifetime License available

SleekView table view for WooCommerce Customizer

Customizer overrides, audited like data

WooCommerce Customizer by SkyVerge replaces stock WooCommerce strings (add-to-cart button text, cart-page labels, checkout messages, free-shipping notices, return-to-shop link) without you editing theme templates. Every override the plugin manages lands in wp_options under prefixed keys (wc_customizer_* family), one option row per override.

The plugin's own UI groups overrides into themed tabs (Shop, Cart, Checkout, Misc) and exposes each as a labelled text field. That's fine for the initial setup. After two years of small tweaks across a store team, no one remembers what was changed where. SleekView reads the wp_options rows directly, lists them as one searchable, editable table, and lets you audit the full set of overrides at a glance, exportable for review or rollback.

Inline edits update wp_options through update_option(), so the plugin's existing get-option calls pick up new values immediately. Bulk-revert is a saved view away: filter to a date range, clear the value column, hit the bulk-update button.

Workflow

Turn config rows into a searchable workspace

1

Point at the option prefix

SleekView reads wp_options rows where option_name starts with wc_customizer_. Each row becomes a table entry.
2

Join with known defaults

The plugin ships a known set of override slots with default values. SleekView lists each override beside its default, so you see exactly what changed.
3

Filter and search

Substring search across override values, filter by section (Shop, Cart, Checkout, Misc), filter by recently edited. Save the view for a brand review or compliance audit.
4

Edit inline or revert

Inline text editing through update_option(). Bulk-revert through delete_option() to fall back to the plugin's built-in defaults.

Sample columns

A typical customizer-override audit view

Reads wp_options filtered to the plugin's prefixed keys. Each row is one override.
Source: wp_options (option_name LIKE 'wc_customizer_%')
Option key Section Default Override Status
wc_customizer_add_to_cart_text Shop Add to cart Add to basket Active
wc_customizer_single_add_to_cart_text Product Add to cart Buy now Active
wc_customizer_free_shipping_text Cart Free shipping Ships free worldwide Edited today
wc_customizer_return_to_shop_text Cart Return to shop Back to catalogue Active

Comparison

Default WooCommerce Customizer admin vs SleekView

Default WooCommerce Customizer settings page

  • Overrides live in tabs (Shop, Cart, Checkout) with no cross-tab search
  • No "recently edited" view: changes from months ago aren't easily discoverable
  • Bulk-revert to defaults means clearing fields one by one across tabs
  • Multi-language stores don't see overrides side by side with translated copies
  • No audit trail for who changed which label and when

SleekView

  • Every wc_customizer_* override as a searchable row
  • Bulk-revert to defaults across a filtered set
  • Filter by section, recently edited, or contains-substring
  • Compare overrides side by side with their defaults
  • Export the full override set as a JSON or CSV review artefact

Features

What SleekView gives you for WooCommerce Customizer

Find any override by content

Substring search across every override value in wp_options. Find the one tab that has stale legacy copy after a brand rename without clicking through every section.

Inline edit and bulk-revert

Edit any override in the row. Or filter the recent-edits view, select a range, and bulk-revert to defaults through delete_option() if a campaign-specific copy needs to roll back.

Export as a review artefact

Every override exported as a single JSON or CSV file for legal, brand, or comms review. Easier than screenshotting each settings tab when copy needs sign-off.

Audience

Who uses SleekView for WooCommerce Customizer

Marketing and brand teams

Review every store-facing label in one screen during a brand or messaging refresh. Edit inline as approvals land, no rebuilding the page after each tab change.

Localisation teams

When the store ships in multiple regions or languages, see each region's overrides side by side. Spot a Cart label that never got translated, edit it in place.

Compliance and legal

Surface checkout and refund-related strings as a filterable set for legal review. Export the result as a signed-off artefact for the compliance archive.

The bigger picture

Why a config plugin still needs row-level audit

WooCommerce Customizer is one of those quiet utility plugins that does a small job exceptionally well: replace stock WooCommerce strings without editing templates. The trouble starts not at setup, but two years in. A marketing intern changed an add-to-cart label for a campaign and never reverted it.

The brand refresh updated some labels but missed others because they were on a tab no one opened. The Spanish translator translated the cart copy six months ago, but Customizer's own defaults shifted on a plugin update and the translation got out of sync. None of this is the plugin's fault.

It's the natural result of any tabbed settings UI accumulating edits over time. SleekView reads wp_options, lists every override as a row, joins each to the plugin's known default for comparison, and gives marketing, localisation, and compliance teams a single searchable audit surface. Edits route through update_option() so caches invalidate normally.

The plugin's own settings page keeps working, untouched, for first-time setup. SleekView just makes the audit possible.

Questions

Common questions about SleekView for WooCommerce Customizer

No, it complements it. The settings page is where overrides are first set up. SleekView is the audit and operations surface for once you have dozens or hundreds of overrides across years of small edits.

 

WooCommerce Customizer writes each override under a prefixed option key (the wc_customizer_* family). Each option row contains the override text. SleekView reads those rows and joins each one to the plugin's known default for side-by-side display.

 

update_option() fires updated_option hooks, which most page caches listen for. Object cache invalidation depends on the override's autoload flag. SleekView writes through update_option(), so caching behaviour matches direct WP changes.

 

Yes. Filter the override view to the rows you want, select them, and bulk-revert. SleekView calls delete_option() per row, so the plugin falls back to its built-in default on next read. Safer than blanking the values, which sometimes keeps an empty override stored.

 

WooCommerce Customizer overrides aren't language-keyed natively. WPML and Polylang typically register the option strings for translation in their own UI. SleekView still shows the base override row, and the translated copies live in the multilingual plugin's string-translation table. Both are exposable as separate views.

 

wp_options doesn't store who changed what. SleekView records SleekView-side edits with user id and timestamp in its own audit log, useful for compliance reviews. Changes made directly through the plugin's settings page aren't captured (those bypass SleekView's write path).

 

Each plugin uses its own prefix in wp_options. SleekView's view is configurable to match any prefix you want, so you can build a similar audit view for other SkyVerge or third-party plugins that store config the same way.

 

If the previous value was set through SleekView, yes, the audit log stores the prior value and exposes a one-click rollback. Edits made before SleekView was installed don't have a prior value recorded, only the plugin's default.

 

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