Only if your shipping page does. SleekAI mirrors what's published, so keep that page realistic. If the policy says 'estimated 2-4 weeks for orders shipping from overseas suppliers', the chatbot quotes that exact range. If the policy says 'fast shipping' with no specifics, the chatbot has nothing to anchor on. The fix is in the policy copy, not the bot, and stores that write honest policies get chatbots that protect them in disputes.

Yes. Shipping zone and class data are accessible as post meta and can be included in the chatbot's context. A buyer in Germany asking about delivery time gets a German-zone answer; a buyer in the US gets a US-zone answer. If you ship from multiple warehouses with different lead times per zone, the bot can quote those differences exactly as configured in WooCommerce.

Yes. SleekAI follows the visitor's input language and works with translated content. A buyer typing in Spanish gets a Spanish answer drawn from the Spanish version of your policy and product pages. WPML and Polylang are honored automatically, and the system prompt can also be language-specific so tone matches local norms, for example more formal in German and warmer in Spanish.

Only if those are in fields the bot can read. Keep supplier info in private metadata that you do not include in context, or in a custom post type the chatbot does not have access to. The default behavior is to read only the fields you explicitly add to the context, so internal supplier data, profit margins, and cost-of-goods information stay invisible by design.

Direct lookups need a small custom endpoint that exposes order status to the chatbot via the WooCommerce REST API. Out of the box, the bot answers policy and ETA questions, which cover most WISMO volume because most WISMO questions are 'when will this typically arrive' rather than 'where is order 12345 right now'. For stores that want the order-number lookup, the integration takes a few hours of dev work.

In your WordPress database. Nothing is shared with Sleek or third parties beyond the OpenAI calls your key authorizes. For stores with strict buyer-privacy commitments or GDPR obligations, the fact that conversations stay on your infrastructure simplifies the data-processor mapping. Logs are also useful as a disclosure trail when chargebacks go to dispute resolution.

If a product is out of stock or a buyer is comparing options, the chatbot can recommend alternatives drawn from your catalog based on the same attributes the product page uses. A buyer asking 'do you have this in red' gets either the red SKU or the closest available color, with a link to that product. This works best when product attributes are filled in consistently across the catalog.

If pre-order or backorder status is set in product meta, the chatbot reads it and answers honestly, including the expected fulfillment date if one is published. A buyer asking 'is this in stock' on a pre-order item gets 'this is on pre-order, expected to ship around X', which is the disclosure that prevents chargebacks later. As with shipping, the bot mirrors what the product configuration says, so realistic data in the catalog produces honest answers.