Merchants ask whether the chatbot “knows live stock.” The honest answer is: it knows the last successful catalog sync for that store_id, including special prices and availability signals, at the cadence you pay for. Claspwell does not claim a Magento inventory API round-trip on every chat turn in v1.
That is still far ahead of a website crawler that cached a product page from Tuesday. It is not magic. Cadence is why Growth and Scale exist.
What syncs today
Products, categories, shopper-facing attributes, special_price, and in-stock style signals land in the tenant catalog. Chat-visible products respect catalog scope (allowed/excluded categories, public audience, optional exclude-out-of-stock). Configurable children stay internal as described in /blog/magento-ai-chatbot-configurable-products.
Freshness by plan
Essential: daily. Growth: hourly. Scale: every 15 minutes. If you run flash sales that last twenty minutes, say so on the discovery call. Hourly Growth will miss some of that; 15-minute Scale is the published ceiling, not a secret faster queue unless Agency quotes one.
Specials vs customer groups
Special prices sync. Customer-group and Shared Catalog prices do not get a v1 marketing promise. If a logged-in B2B buyer must see a different net price in chat than a guest, that is an entitlement problem, not a copy problem — we will not paper over it.
When answers should refuse
Out of scope, not chat-visible, or out of stock (when configured) should not appear as a confident add-to-cart suggestion. Low-confidence turns should fall back rather than invent warehouse counts. Stale sync is still the usual incident: upgrade cadence or fix the Magento job, do not yell at the model.
How to buy this honestly
Pick cadence from /pricing, not from a “real-time” checkbox. Request integration if Magento 2 / Hyvä catalog chat with EU hosting is the actual job.