Product Add-Ons Pro stores its field definitions in _product_addons postmeta on each product as a serialized array of fields, each with a label, type, required flag, and optional price adjustment. Global addon groups live as their own post type, typically global_product_addon, with the same postmeta payload. At checkout, the customer's selections are written to wp_woocommerce_order_itemmeta as discrete meta rows per field. The default admin lets a merchant edit one product's fields at a time and lets a store owner see addons on a single order, but never connects the two.

SleekView reads _product_addons across every product (and the global addon CPT), expands the serialized payload into one row per field, and exposes label, type, required flag, and price adjustment as first-class columns. A second view joins order_itemmeta rows whose keys match addon labels to rank addon picks by frequency and revenue, so merchandising can finally see which fields actually move and which are clutter.

Inline edits to required flag and price adjustment route through Product Add-Ons Pro's own update path so plugin hooks fire and the serialized postmeta payload is rewritten correctly. Bulk operations like flipping a field from required to optional or adjusting price across a category go through the same path.

Product Add-Ons Pro is built around the idea that any product can grow extra fields, which is great for personalization but ends up hiding a sprawling catalogue inside one postmeta key per product. The default admin lets a merchant edit one product's fields and lets a store owner see addons on a single order, but it never connects the two, so merchandising cannot tell which addons actually convert, finance cannot attribute addon revenue cleanly, and support cannot trace a specific order line back to the field definition that produced it. The data is all there in _product_addons and order_itemmeta, but it lives behind per-product screens.

SleekView reads both, expands the serialized payload into one row per field, joins it to actual picks, and exposes the result as a sortable, filterable, editable table. Dead-weight fields surface immediately. Required-vs-optional split-tests become a one-click change.

Pick frequency replaces guesswork. The plugin still owns the field editor; SleekView turns the addon catalogue into a working surface.