SleekView for WooCommerce Composite Products: bundles, components & priced configurations
Read composite-type products from wp_posts, follow the _bto_data meta to component definitions, and surface scenarios and per-component price overrides as columns. Sort by composite, filter by component, edit inline.
♾️ Lifetime License available
Stop drilling into each composite to audit its components
WooCommerce Composite Products stores a configurable bundle as a single product of type composite, with each component ("Frame", "Wheels", "Saddle") defined inside the _bto_data meta as a serialized array. The component points to a query — a category, a tag, or a hand-picked product list — and optionally to scenarios that hide or override pricing based on selection. The default product table shows none of this. You click into each composite to see its components and their option counts.
SleekView reads the composite's _bto_data, decodes the components, and joins them back to their underlying product IDs so a single row exposes composite name, component name, option count, and per-component price overrides. Filter by composite, by component title, or by whether a component has discounted options. Spot the composite where the "Frame" component points to a category that no longer has any in-stock products before a customer hits the configurator.
Inline edits through CRUD update the composite's meta directly. Toggle a component's optional flag, change its title, switch its query type from category to product list — all from the row. Per-component price overrides update without opening the composite editor's tabbed UI for each one.
Workflow
How SleekView reads your composite product data
Point at composite-type products
wp_posts for products of type composite, decodes _bto_data meta, and exposes both composite-level and component-level rows.
Compose your column set
postmeta keys if your store uses them for vendor codes or sourcing flags.
Save and scope the view
Edit inline and ship
_bto_data through CRUD so the configurator and editor stay consistent.
Sample columns
A typical Composite Products component view
_bto_data meta to surface each component as its own row, joined to the composite's product data.
wp_posts (composite) + wp_postmeta (_bto_data)
| Composite | Component | Query type | Options | Optional | Price override |
|---|---|---|---|---|---|
| Custom Mountain Bike | Frame | Category | 12 | Required | — |
| Custom Mountain Bike | Wheels | Tag | 8 | Required | −€20 |
| Build-a-Desk | Top | Product list | 5 | Required | — |
| Build-a-Desk | Cable tray | Product list | 3 | Optional | +€15 |
| Studio Camera Kit | Lens | Category | 0 | Required | — |
Comparison
Default Composite Products admin vs SleekView
Default Composite Products
- Components are buried inside each composite's tabbed product editor
- No way to list all components across all composites in one screen
- Empty queries (categories with no products left) silently break the configurator
- Per-component price overrides require opening the composite's editor
- No bulk operations across composites that share a component definition
SleekView
-
Decode
_bto_datameta into one row per component, per composite - Surface query type and option count so you spot empty components
- Filter on optional flag, query type, or per-component price overrides
- Inline-edit component titles, optional flags, and price overrides
- Switch to a kanban view grouped by composite to audit each bundle's structure
Features
What SleekView gives you for WooCommerce Composite Products
Component-level rows, not just composites
One row per component per composite means you can audit, sort, and filter across components — "all required components with zero options", "all optional components with a price override", "every component pointing at a deprecated category".
Inline-edit component config
Toggle a component's optional flag, retitle it, switch its query type from category to product list, override its price. Each edit writes back into _bto_data through CRUD so the configurator picks it up immediately.
Catch broken configurators before customers do
Filter to components with zero matching products, or components whose category was emptied by a stock adjustment. Surface them as a saved "Broken composites" view your team checks weekly.
Audience
Who uses SleekView for WooCommerce Composite Products
Made-to-order shops
Custom bikes, modular desks, or build-your-own kits where each composite has six or more components. Auditing them one composite at a time is impractical — a flat component view turns a half-day audit into a coffee.
Pricing teams
See every per-component override across the catalogue in one filtered view. Spot composites where the discount maths no longer adds up, or where a price override predates a vendor cost change.
Catalogue ops
Find composites whose component query points at an empty category before a customer reaches a broken configurator. Saved view: "Components with zero options." Run it after every catalogue update.
The bigger picture
Why component-level visibility beats composite-by-composite clicks
WooCommerce Composite Products is the right tool for build-your-own catalogues — bikes, desks, photography kits, gift baskets — but its admin treats each composite as an island. The components that make a composite work live inside a tabbed editor, accessible only by opening that one product. There's no list of all components across all composites, no filter for components with empty queries, no quick way to audit which composites still have a price override that predates last quarter's vendor change.
Catalogue teams scale this with spreadsheets, exporting and re-importing CSVs to spot anomalies. SleekView replaces the spreadsheet step. It decodes the _bto_data meta, exposes one row per component per composite, and lets you sort, filter, and edit across the whole catalogue at once.
Components pointing at deprecated categories surface in seconds. Per-component overrides become reviewable in bulk. Audits that took a morning take a coffee.
The composite editor stays where it is — SleekView is the cross-composite layer the per-product UI can't be.
Questions
Common questions about SleekView for WooCommerce Composite Products
Yes. SleekView reads the composite's _bto_data meta, decodes the serialized component array, and exposes each component as a row with its title, query type, query value, optional flag, and price override. The component-level fields are queryable, sortable, and editable just like top-level columns.
Yes. Build a composite-level view that shows one row per composite — name, total components, total options across components, last edited. Or pivot to the component-level view for cross-composite analysis. Both views read the same source; switching between them is a saved-view toggle.
Yes. SleekView writes back to _bto_data through WooCommerce's product CRUD. The composite editor's tabbed UI reads the same meta on next load, so changes show up there as expected. Hooks like woocommerce_process_product_meta still fire for any custom logic you've layered on.
Yes. SleekView joins each component back to its query target — a category, a tag, or a product list — and exposes the option count. Filter to components with zero options and you have an early-warning view for broken configurators, refreshed on demand.
Yes. Composite Products and Product Bundles are separate plugins with different data models. SleekView reads each from its own meta keys (_bto_data for composites, _bundled_items for bundles) and presents them as their own views. You can build a tabbed page with one tab per source if useful.
Composite Products' scenarios are stored as part of the same _bto_data structure. SleekView can surface scenario count per composite and the components each scenario affects. Editing scenarios inline is supported for the simpler cases (visibility toggles); complex scenario logic still benefits from the composite editor.
HPOS only changes the orders schema, not products. Composite products stay in wp_posts with _bto_data meta in wp_postmeta regardless of HPOS state. SleekView reads them the same way on either configuration.
No — it's a row-level audit and bulk-edit surface. The composite editor's tabbed UI remains where it is for building a composite from scratch and for complex scenario logic. SleekView gives ops the cross-composite views the per-product editor can't, without disturbing existing workflows.
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.
Lifetime ♾️
Most popular
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
€749
Continue to checkout