Yes. Composites are products of type composite, with components in the woocommerce_composite_components custom table linked to the parent composite. SleekAI maps both via the data-source wizard, including option sources (categories or specific products), default options, optional flags, quantity ranges, and per-component discounts. The bot only sees the composite currently in scope, so the prompt stays bounded.

Yes. Scenarios encode conditional visibility and compatibility between components. SleekAI exposes the scenario rules relevant to the current composite, so the bot can explain why a specific CPU disappears when a small case is selected, or why a power supply is required at a higher wattage when a particular GPU is chosen. It will not invent a scenario that the merchant has not configured.

Yes. The composite holds component-level pricing, and SleekAI exposes the per-component price and any configured discount. The bot can describe the running total based on the customer's current selections (when those are passed in via the page state) and explain how each remaining choice will change the total before the customer finishes the form.

Yes. Each component carries an optional flag, and SleekAI exposes it. When a customer asks whether the RGB lighting kit can be skipped, the bot reads the real configuration and answers honestly. That removes a recurring class of pre-sale questions and keeps the customer in the builder instead of email.

No. SleekAI guides, the composite builder executes. Letting an LLM push a configured composite into the cart would bypass scenario validation, the min/max checks per component, and the stock dependency logic that Composite Products enforces. The bot describes the right build, the customer selects it on the form, and WooCommerce stays the source of truth.

Yes. Point SleekAI at the composite product type as a whole rather than a single composite, and the bot can compare builds. A custom PC store might run one builder bot that recommends the right composite for the customer's use case (workstation, gaming, compact home server) and then dives into the components of that composite.

WooCommerce tracks stock on the underlying products that feed each component's option pool. SleekAI reads stock state alongside the option metadata, so when a popular option is out of stock the bot can say so honestly rather than promising a build that depends on a missing part. Pairing this with a notify-when-back-in-stock link keeps the customer in scope.

Inside WordPress, per chatbot, with model name, token usage, and page URL on every message. Logs help support spot scenarios that confuse customers, options that should be hidden by default, or wording that needs to match the builder more closely. Most fixes ship in the WooCommerce admin or the composite product description.