SleekAI reads whatever multi-location data your plugin maintains. ATUM, Multi-Locations Inventory, Smart Manager, and bespoke plugins all store per-location stock as custom tables or postmeta. The data source wizard maps the relevant fields once, and the bot reads live values at query time. The mapping accommodates the different shapes plugins use, so the integration works whether your locations are a custom post type or a separate inventory table.

Yes, if you store store-specific prep time data. Most retailers maintain a daily or hourly prep capacity figure per store (often in a stores custom post type), and the bot reads the current queue against capacity to quote a realistic window. For stores without dynamic capacity data, the bot can quote a static prep window per category, which is less precise but still better than no window.

Yes. Store hours live in postmeta on each store record; the bot reads them along with any holiday override calendar your team maintains. When a customer asks about pickup today, the bot accounts for current hours, the prep window, and any holiday closure to quote a window that actually works. This is one of the most appreciated features for customers who plan visits around odd-hour stores or holidays.

If your inventory plugin supports store reallocation, yes. The bot can check the alternative store's stock and initiate the swap if the order has not yet entered prep. For orders past the prep cutoff, the bot routes to support with the request context so a human can coordinate the inter-store transfer. Either way, the customer gets a clear answer instead of a vague 'maybe' that erodes trust.

Most retailers hold pickup orders for a set duration (commonly 3 to 7 days) before restocking the items. The bot quotes the hold duration when the customer confirms pickup, sends reminders if linked to your transactional email tool, and explains the restocking flow if the customer cannot make it. This prevents the common frustration of a customer arriving on day 8 to find the order has been put back on the shelf.

Yes. If a customer's cart has three items and only two are in stock at the chosen pickup location, the bot can offer pickup of the two with delivery on the third, or store transfer for the third. The fulfillment flexibility is exactly the kind of decision customers want to make in chat rather than at checkout, where the friction often causes abandonment.

The bot does not run the counter handoff. That happens through your POS scanning the pickup confirmation code. The bot's role is everything up to and after the in-store handoff: pre-pickup confirmation, ETA, store location, ID requirements, and post-pickup follow-up. Customers who use the bot before pickup arrive at the counter with the right expectations, which speeds up the in-store flow.

Yes. Each store's policies (hours, hold duration, authorized pickup rules, store-swap availability) live as postmeta on the store record, so the bot answers each customer with the rules for the store they chose. Multibot can also scope per-region bots if regional differences are large enough to warrant a separate system prompt, though most retailers find a single bot reading per-store metadata is sufficient.