Yes, the kanban reads the composite product itself regardless of whether its components reference simple or variable products underneath. The component count, price range, and stock status on the card reflect the full configurator including its variable components, so the board reads accurately across mixed configurations.

Yes, when writeback is enabled, dragging a card from draft to published updates the WordPress post status through the standard update path. WooCommerce hooks tied to product publishing fire as they do from the post editor, including hooks that any third-party plugin or custom theme has registered.

Yes, component count is one of the metadata fields you can map onto the card front, derived from the composite's component definitions stored by the plugin. That helps merchandising distinguish small two-piece configurators from sprawling seven-piece bundles without opening the edit screen for each product.

A composite lands in the out of stock column when at least one of its required components has zero stock, which the plugin calculates as part of its standard storefront logic. The blocking component is shown on the card so your inventory team can act on the root cause quickly without investigation.

Yes, the kanban inherits the same capability checks WordPress and WooCommerce apply to product editing. A shop manager who can publish products can drag cards between status columns, and a role without that capability can view the board but cannot move any cards across the columns.

Yes, SleekView ships with filters that scope the board without changing the underlying products. Filter by component count to focus on small or large configurators, or by price band to focus on a tier of your catalog, and the column counts recalculate to match the filter applied.

If a status change happens outside the kanban, SleekView picks up the new state on the next refresh and the card moves to the right column automatically. The board stays in sync with edits made through any path, including bulk actions and CLI updates from external scripts and migrations.

Yes, columns paginate and card details lazy-load on scroll, so stores with hundreds of composites open the kanban quickly. The status grouping queries the same indexed post status column WordPress already uses, so the database load is comparable to opening the WooCommerce products screen.