Yes. SleekAI reads your WordPress and WooCommerce data live, so picks stay inside what you actually broke down. The bot can mention adjacent cuts for context (a flat iron when the customer asked about hanger) but the recommendation, the cut the shopper should buy, stays in stock. Sold-out items get filtered before the prompt is built, and the bot's freshness matches your inventory cadence.

Yes. Custom fields for breed (Hereford, Angus, Schwabisch-Hallisches Landschwein), farm name, feed program, and hanging time feed the prompt. A customer asking 'where does the beef come from' gets a real answer with farm name and feed approach, not a vague 'locally sourced' deflection. If you publish farm profile pages, the bot retrieves them when the conversation calls for depth.

Yes. Hanging-time and aging-status fields on each product flow through. The bot can say 'this ribeye is 28 days dry-aged, ready now' or 'the bresaola needs another two weeks' based on what you set. For house-cured items like pancetta or guanciale, the bot quotes cure days and rest days from your product meta rather than generic charcuterie timelines.

Yes. Multibot plus display conditions let each section have its own bot and prompt. The wholesale bot on /restaurants/ quotes case pricing, minimum orders, and lead times. The retail bot on /shop/ stays focused on cut-to-occasion matching for home cooks. Each scope is set with URL pattern and user-role conditions.

The conversation logs flag pre-order interest you can route through your normal process. For Christmas goose, Easter lamb, or Thanksgiving turkey, the bot quotes the order deadline and pickup window from your published holiday page and captures the customer's name, weight preference, and pickup slot. The butcher's morning starts with a named list rather than a sequence of voicemail callbacks.

Yours. SleekAI is bring-your-own-key for OpenAI, Anthropic, Google, or OpenRouter. For most butcher shops, a smaller model handles cut and recipe questions cheaply, and you can reserve a higher-end model for occasions where the customer is planning a multi-course menu and the chat needs to reason across cuts, sides, and timing in one thread.

Yes, when your cut guides and recipe cards live on the site or upload into the OpenAI Files vector store. The bot quotes oven temps, rest times, and internal target temperatures from your wording, so the cook gets answers consistent with the cut you sold them. For shoppers buying a chuck roast and asking about a braise, the bot retrieves your house braise recipe rather than improvising.

If those live in WordPress with price, weight, and contents fields, the bot pulls from them. A shopper asking 'what is in this week's butcher's box' gets a real list with cuts, weights, and price, rather than a vague 'check the page' deflection. The same goes for sausage flights, charcuterie boards, and steak-night bundles, so the chat closes the upsell instead of losing momentum.