Yes. SleekAI reads your live daily-catch list and WooCommerce stock so recommendations stay inside what arrived on the morning truck. The bot can suggest a substitute when a requested species is not in (pollack for cod, gurnard for monkfish) but the recommendation always points to a piece you can actually wrap and hand over. Out-of-stock items get filtered before the prompt is built.

Yes. Add MSC, ASC, or Good Fish Guide ratings as a custom field or taxonomy and the bot quotes them naturally in recommendations. When a customer asks for a red-rated fish, the bot can offer the closest green alternative without lecturing. Sustainability is one of the questions where a grounded answer (your shop's specific rating choices) beats a generic blog summary every time.

Yes. Line-caught, day-boat, trap-caught, dive-caught, farmed: all of these are post-meta fields the bot reads. A customer asking 'is the seabass farmed or wild' gets a real answer, not a deflection. For shops that publish boat profiles, the bot can also retrieve which boat landed which species, which is the kind of detail that turns a curious shopper into a regular.

The conversation logs flag oyster and shellfish pre-orders with quantity, type (Fines de Claire vs Speciales vs Belon), and pickup window. The buyer's morning starts with a named list rather than a sequence of voicemails. For weekend whole-fish or special-order turbot, the same flow captures species, weight preference, and pickup time.

Yes. Multibot plus display conditions lets a wholesale bot live on /restaurants/ with case pricing, minimum orders, and morning delivery cutoffs. The retail bot on /shop/ stays focused on cook-to-catch matching for home customers. Each scope is set with URL pattern and user-role conditions, so wholesale clients do not hit a retail-tuned voice and vice versa.

Yours. SleekAI is bring-your-own-key for OpenAI, Anthropic, Google, or OpenRouter. For fishmongers, a smaller model handles most catch-to-dinner conversations cheaply, and you can reserve a higher-end model for the multi-course Friday evening planner conversations where the chat needs to reason across starter, main, and side in one thread.

Yes, when your recipe cards live on the site or upload into the OpenAI Files vector store. The bot quotes pan temps, rest times, and target internal temperatures from your wording. For a customer buying brill and asking how to bake it whole, the bot retrieves your house recipe rather than improvising. The result is cook-time guidance consistent with the fish you actually sold them.

If those live in WordPress with contents, weight, and price fields, the bot reads them. A shopper asking 'what is in this week's seafood box' gets a real list, not a 'check the page' deflection. Friday weekend specials (paella mix, bouillabaisse pack) and seasonal items (mackerel run, scallop landings) all surface in recommendations the moment they are added to the catch list.