Catalog sync and search health
How Findora keeps its index in step with your catalog, and what the Search health screen shows.
Findora is in development. These docs describe the app as it is being built; details can change before it is listed on the Shopify App Store.
The first sync
After install, Findora reads your whole catalog in one bulk export from Shopify, then builds its search index. Large catalogs take longer. Progress shows on the Search health screen.
During the first sync your storefront already works: the Findora blocks render filters from Shopify’s own filter data. See Engines below.
Staying in sync
- Live updates. When you create, edit or delete products, collections or inventory, Shopify notifies Findora and the change reaches the index shortly after.
- Bulk edits. Large bulk edits are batched rather than handled one product at a time.
- Hourly reconcile. Once an hour Findora checks for changes it may have missed and corrects them.
Engines
The engine is what is answering your storefront right now:
| Engine | When | What shoppers get |
|---|---|---|
| Indexed | Normally | Instant search and the full filter set from Findora’s index. |
| Native | While the first sync runs, during an incident, or if the subscription lapses | Filters from Shopify’s own data, rendered in your theme. |
The switch is automatic. Shoppers never see an error page because of Findora.
The Search health screen
Search health shows the state of the catalog sync and the index, and has two actions:
- Re-read the catalog: a fresh full export from Shopify.
- Rebuild the index: rebuild from Findora’s copy of your catalog.
When a change does not show yet
Some settings (synonyms, results rules, boosts, stopwords) reach the storefront when the index is next rebuilt. Findora saves them straight away and tells you when a rebuild is still to come; that is a notice, not an error.
Something unclear or missing? Tell us.