WooCommerce Composite Products stores composites as standard product posts with a custom product type, components configured via the _bto_data postmeta key, and scenarios defining compatibility between component choices. SleekAI maps each component, its options (filtered by category, tag, or specific products), the scenarios that constrain compatibility, and the dynamic discounts or summed totals into named variables the chatbot uses on every request. When a shopper picks a frame and asks which wheelsets are compatible, the bot can name them.

The widget reads the composite's current configuration state on the single-product template, so the bot knows which components have been chosen and which are still required. Display conditions scope the widget by post type, taxonomy term, user role, login state, and URL, so a bike-builder bot can coexist with a PC-builder bot under multibot. The bot reads the live cart, so it can describe the running subtotal as each component is added, including any per-component discounts.

Every conversation is logged inside WordPress with model, token usage, and page URL. Combined with the JS API and PHP embed, the bot can pop from a step indicator, a sticky compare panel, or a custom Bricks element without rebuilding the composite engine.

Composite product stores live or die by the build experience. A bike, PC, hamper, or modular furniture configurator can carry six or eight components, dozens of scenarios, and a running subtotal that updates on every click. The most common drop-off happens when a shopper does not know which options at step three are compatible with their step-one frame, or whether picking the carbon fork unlocks a discount on the carbon wheels.

A generic chatbot has no visibility into the composite components or the scenarios, so it either declines to help or invents compatibility that does not survive the cart's validation. Composite Products already stores every component, every option source, every scenario, and every per-component discount as structured product meta, and WooCommerce already knows the current build state. SleekAI does the wiring that turns those records into accurate, step-aware answers, on a model and key the merchant pays for directly.