Yes. Zones live in the core WooCommerce shipping tables and the plugin's rate rows sit in woocommerce_shipping_table_rates. SleekAI maps both via the data-source wizard, including class conditions, weight ranges, price tiers, and labels. The bot only sees the zone and class data relevant to the current cart or product, so the prompt stays grounded and small.

Yes. Shipping classes are a WooCommerce taxonomy and Table Rate Shipping references them in rate rows. SleekAI exposes both the class assigned to each product and the per-class rules in the relevant zone, so the bot can explain why a fragile item costs more or why a heavy item bumps into a different rate tier without inventing a surcharge.

No, as long as the data source is mapped correctly. SleekAI reads the same rate rows WooCommerce uses to compute checkout. If a rule changes, the prompt picks up the new value on the next request. There is no separate rate cache to fall out of sync, and the bot never writes to the rate table, so configuration stays in the WooCommerce admin where it belongs.

Yes. Display conditions cover page templates, URL patterns, and post types. A common setup is a shipping-focused bot on the cart, checkout, and shipping policy pages with the full zone matrix in scope, plus a separate sales bot on product and category pages that only carries lightweight shipping summaries to keep the prompt short.

Yes. Free-shipping thresholds and minimum-order rules are part of the table rate schema and flow into the prompt. The bot can quote the threshold for the visitor's destination and explain how much more they need to add to qualify. It will never invent a free-shipping line that does not exist in the rate table.

The shipping cost itself comes from the table rate row. VAT and duties live in WooCommerce's tax configuration, which SleekAI can also read as a data source. The bot can describe the shipping cost from Table Rate Shipping plus a tax summary, while explicitly noting that destination duties may apply on import rather than promising a final landed price.

Yes. If a destination has no matching shipping zone, that fact is visible in the data. The bot can clearly say the store does not currently ship to that country instead of pretending a rate exists. That honesty cuts a recurring class of refund and cancellation requests caused by checkout discovering the truth at the last step.

Yes. Every user question and bot reply is stored inside WordPress with model name, token usage, and page URL. Logs help support spot patterns: a zone that triggers complaints, a label that confuses customers, or a class assignment that needs adjusting. Most fixes ship in the WooCommerce admin rather than the prompt.