Yes. Dokan exposes the active vendor via WordPress query vars on store templates and via product authorship on single product pages. SleekAI reads that signal on every request and loads the matching vendor's store data, policies, and product set into the prompt. On the marketplace homepage where no single vendor is active, the bot falls back to a site-wide context with no per-vendor data exposed.

Dokan splits a buyer's checkout into one sub-order per vendor, and each sub-order has its own status, shipping field, and tracking. SleekAI reads the relevant sub-order from the WooCommerce orders layer (legacy posts or HPOS) so a buyer asking about a slow package gets the correct vendor's fulfillment status, not a confused average.

Yes. SleekAI's multibot mode runs multiple bots on one site with separate system messages, data sources, and display conditions. A common setup is one shared marketplace bot for the homepage and search, plus one per-vendor bot scoped by display condition to that vendor's store template. Vendors can have distinct tones without operators rebuilding each install.

Yes. Dokan Pro stores additional vendor fields in the same usermeta layer and adds a vendor-side dashboard. SleekAI can read those fields like any other meta. A separate vendor-facing bot can run inside the dashboard URL pattern to help sellers with payout, listing, and KYC questions while the buyer-facing bot runs on storefront pages.

Dokan stores shipping zones per vendor, and tax rules either inherit from WooCommerce or are vendor-overridden. SleekAI pulls the active vendor's shipping zone map and tax notes into the system message, so a quote-to-Toronto question returns that vendor's rate rather than a blended marketplace average.

The bot can explain the vendor's refund policy and the marketplace's escalation path, and it can describe what action will be taken. It does not write refunds directly, since Dokan and WooCommerce both have approval flows. Wire the bot's escalation into a Dokan ticket or a WooCommerce email so the actual refund stays in the dashboard.

Conversation logging stores the page URL alongside the message history. Operators can filter logs by URL pattern to see only one vendor's conversations, which is enough for QA without surfacing per-vendor logs to the vendors themselves. If you do want vendor-side log access, expose a custom view in the Dokan dashboard scoped by URL prefix.

No, when the bot is configured correctly. SleekAI only loads the active vendor's context on a vendor page, and falls back to global marketplace context on neutral pages. The system message should not paste the full vendor list. For sub-order data, the bot only reads orders belonging to the logged-in user, so a customer cannot ask about another customer's sub-order.