Yes. WooCommerce stores the bag base price, per-gram rate, and bin contents in postmeta. SleekAI reads those rows on every turn, sums the selected weight, and replies with the real total. If a bin is out of stock the bot flags it and suggests a similar sweet from the same allergen group.

Map an allergen taxonomy or postmeta flag for each sweet. The bot only confirms a product is gluten free, vegan, or nut free when the underlying data says so. For ambiguous cases it points shoppers at the dedicated allergy filter page rather than guessing, which protects you from liability.

Yes. Bulk favours usually use variable products with tiered prices, like 50 bags at $1.80 each or 200 bags at $1.35 each. SleekAI reads the variation postmeta and quotes the exact tier the bride is asking about, including ribbon colour and personalised tag options pulled from the same product fields.

Yes. Map shipping zones and lead times as variables. The bot can quote UK, US, EU, and Australia rates, free shipping thresholds, and the cut-off for next-day dispatch. From May to September it can also mention insulated packing for chocolate-coated lines that melt in transit.

Yes. Both Mix and Match Products and Pick Box store their bin selections in postmeta. Map the relevant meta keys in the SleekAI Wizard and the bot can list available bins, current selections, and the bag total. If you use a custom bag plugin you can map its custom table the same way.

Yes. Display conditions scope a bot by product category, tag, post type, user role, or URL pattern. A pick-and-mix bot can live on the pick-and-mix category while a wholesale bot runs only on the trade category, both reading from the same WooCommerce database without conflicts.

Stock status lives in postmeta and is read on every turn, not cached at indexing time. If a sweet sells out during the chat, the next reply reflects the new status. The bot can also suggest the closest in-stock alternative from the same flavour or allergen group.

Yes. Every chat is logged in WordPress with the model name, token usage, and the page URL it ran on. Review the logs to spot repeat questions about a missing allergen tag or an unclear pick-and-mix rule, then fix the underlying product copy and watch the question disappear from the queue.