A catalog-aware AI sales assistant is only as good as its copy of your catalog. If a shopper asks for waterproof hiking boots in size 44 and the assistant still thinks last week's discontinued model is the best match, the answer looks wrong, even if the AI part worked perfectly. That is why catalog sync frequency is one of the first practical questions Magento 2 merchants ask us. This post explains what gets synced, how often, and how to pick the right schedule for your store.
What a catalog sync actually does
Claspwell does not crawl your storefront pages. During install we map your shopper-facing attributes, then sync your Magento categories, products and those attributes into our own database. The assistant searches that synced copy with structured queries, category first and then attributes, and returns real product cards. A low-cost LLM is used only to route the shopper's intent, not to invent products. The background is in why AI chatbots fail without catalog sync.
So the sync schedule decides how fresh that copy is. Anything you change in Magento admin, such as a new product, a new category, a price change, a product going out of stock or a new attribute value, reaches the assistant at the next sync.
The schedules on each plan
- Growth: hourly catalog sync, for most single-store Magento and Hyvä merchants.
- Scale: 15-minute catalog sync, for higher volume and up to three store tenants.
- Essential: a single store with early catalog chat on a less frequent schedule, a good fit for catalogs that change slowly.
- Agency: sync frequency is quoted per contract, together with the multi-store setup.
The current details are always on the pricing page.
How to pick the right one
Ask yourself how much your catalog changes in a normal day, and how much it hurts when a shopper sees an outdated answer.
- Your catalog changes a few times a week (a B2B parts catalog, furniture, made-to-order goods): a slower schedule is usually enough. Shoppers care more about the right attributes than about minute-by-minute freshness.
- You run regular promotions, price updates or daily imports from an ERP or PIM: hourly sync keeps the assistant in step with the storefront within the same working hour.
- You sell fast-moving stock, run flash sales or manage up to three stores: 15-minute sync narrows the window where the assistant can recommend something that just sold out.
If you are unsure, start with the plan that matches your conversation volume and watch where shoppers hit stale data. It is easier to move up a tier with real evidence than to guess.
What sync frequency does not solve
A faster schedule cannot fix messy data. If sizes are stored in free-text descriptions instead of attributes, or half of your products sit in the wrong category, the assistant will be fast and still unhelpful. Our attribute checklist for AI product discovery covers what to clean up first. For how prices and stock are checked before products are shown, see live price and stock validation.
What is coming next
Real-time sync webhooks and stock signals are in progress on our roadmap. The goal is event-based updates for inventory and price changes instead of waiting for the next scheduled run. Until that ships, scheduled sync is how Claspwell stays current, and we will say so plainly when it changes.
Practical tips
- Plan big catalog imports right before a scheduled sync, not right after one, so changes reach the assistant sooner.
- Before a sale starts, give the catalog one full sync cycle to pick up sale prices and promo categories.
- When you add a new attribute that shoppers filter by, tell us so it can be mapped. Unmapped attributes are not used in answers.
Want to know which schedule fits your catalog? Request an integration and we will look at your store, your catalog shape and your change rhythm during the discovery call. Install typically takes 3 days to 1 week after access is ready.