Yes. Blend ingredients usually live as a structured list in postmeta or a custom field group. SleekAI reads the list and replies with the full ingredient set, including the order they appear, plus salt or sugar flags. For a salt-free garam masala the bot can confirm the omission without guessing from generic recipes.

Map origin country, region, and PDO or DOP certifications as product attributes. The bot can confirm a smoked paprika is Spanish Pimenton de la Vera PDO certified or that your saffron is from La Mancha. For uncertified spices it can quote the country of origin without overstating provenance claims.

Yes. Each spice usually has multiple variation sizes from 50 g jars to 1 kg foil bags and 5 kg drums. SleekAI reads variation postmeta and quotes the right row directly. It can also compute a per-gram saving for restaurant customers comparing a 1 kg bag to a 50 g jar without inventing numbers.

Map salt-free, sugar-free, organic, and gluten-free flags per product. The bot only confirms a blend is salt free when the data says so. For organic claims it references the certifying body where you have set one, like USDA Organic or EU Organic, instead of relying on visual cues from packaging.

Yes. Stock status is read on every turn. When the smoked paprika sells out the bot can recommend Hungarian sweet paprika plus a pinch of chipotle for the smoke note, both of which it can link to your in-stock SKUs with their real $5.50 and $6 jar prices, all from the same product database.

Yes. Display conditions support post type, product category, tag, user role, and URL pattern. A retail bot focuses on jars, recipes, and allergens, while a wholesale bot specialises in 1 kg and 5 kg pricing and chef-focused substitutes. Both read the same WooCommerce data with no duplication.

If you offer Woo Subscriptions for refills, map the subscription postmeta. The bot can quote a monthly 100 g refill at $11 with a 10 percent subscriber discount and explain how to pause. Without a subscription product it can suggest your largest in-stock variation and a manual reorder reminder workflow.

Yes. Every conversation is stored with the model name, token usage, and the page URL it ran on. Patterns like repeat questions about missing PDO certifications or unclear bulk sizes feed back into product copy and variation labels, so the spice catalogue keeps tightening over time.