Yes. Global add-ons are stored under a separate options structure and a custom taxonomy rather than per-product postmeta. SleekView ships a separate view that surfaces global add-ons alongside the per-product view, so audit-style questions resolve across both storage strategies in one screen.

Yes. SleekView serialises updates back through the Product Add-Ons API where supported, so storefront caches refresh and the standard editor view stays in sync. Direct DB edits are available per view for bulk-rename operations where the price hasn't changed and hooks would just churn the cache unnecessarily.

Yes. Order item meta lives in its own table — woocommerce_order_itemmeta — under both legacy and HPOS storage, and the order item structure is unchanged by HPOS. SleekView reads from whichever order table the store is configured to use, so add-on revenue reports remain accurate post-migration.

Yes. Filter the orders view by add-on label or by the order item meta key for fast lookups. That's the route to answer questions like which-orders-included-the-rush-shipping-add-on during finance month-end or to follow up on add-on-specific support escalations.

Yes. The uploaded file URL stored in order item meta surfaces as a column with a direct download link, so support sees the customer's uploaded artwork or document without opening the order edit screen and hunting for the right line item.

Yes. Views are gated by WordPress capability and saved per role. A merchandising role sees the cross-product audit view; finance sees the revenue aggregation; support sees the per-order add-on detail. Each role gets the columns they actually use.

Yes. Add-on price types — flat fee, percentage, quantity-based — are stored in the serialized definition. SleekView surfaces the type as a column and applies the right calculation when reporting estimated revenue impact, so percentage-based add-ons aren't misreported as flat amounts in the audit view.

Yes. Joining add-on definitions with the order item meta selections produces an adoption-rate column — how often customers actually pick this add-on when they buy the parent product. That's the number that distinguishes add-ons worth keeping from add-ons that look interesting but no one selects.