Short answer: yes, and it stays fast in a specific way that's worth understanding, because it tells you what you do need to pay attention to as your store grows.

When a customer asks something, Arbyn doesn't keyword-match. It compares the meaning of the question against everything it knows about your store: your products, collections, pages, blog posts, policies, uploaded documents, FAQs, and the answers your team has taught it. Then it pulls the handful of items that genuinely relate.

That's why a customer can ask "will this survive a wash" and get an answer from a care-instructions page that never uses the word "wash."

The obvious worry is that comparing against 20,000 items must take a hundred times longer than comparing against 200. It would, if Arbyn checked them one at a time.

It doesn't. Your knowledge is organised into a structure that lets Arbyn jump more or less straight to the relevant neighbourhood, the way an index at the back of a book beats reading every page. Adding more to your store makes the book thicker; it doesn't make looking something up meaningfully slower.

We measure this rather than assume it. Search time is effectively flat from a few hundred items to tens of thousands.

This is the useful part, because these are the things you can actually act on.

More of your catalog competes for the same answer. Arbyn returns the most relevant items, not all of them. With a very large catalog, near-duplicates and thin product descriptions start crowding each other out. Two products described almost identically are two products Arbyn has to guess between.

Thin descriptions hurt more at scale. A product whose description is just its title gives Arbyn almost nothing to match a customer's question against. In a 200-product store that's one gap. In a 20,000-product store it's a pattern.

Your policies still need to be findable. Products are usually the largest part of a big store's knowledge by a wide margin. Make sure your shipping, returns and warranty information exists as proper pages or documents, not only as a line buried in a product description. That's what Arbyn reaches for when a customer asks a policy question.

Go to Knowledge. The Knowledge Center shows every source Arbyn is drawing on and how much of your store is covered.

If something specific isn't being found, Knowledge → Knowledge gaps shows the real questions Arbyn couldn't confidently answer, in the customer's own words. That's a far better guide to what to write next than guessing.

Do I need to do anything when I add products? No. New products, pages and blog posts are picked up automatically.

Is there a limit on how much Arbyn can know about my store? There's no cap you need to manage. Bigger catalogs are handled by the same mechanism as small ones.

My store is large and an answer felt wrong. What now? Open the conversation and look at what Arbyn used to answer. If it reached for the wrong product, that's almost always two items described too similarly. Tightening one description fixes it for every future customer, not just that one.