How Appifire Syncs Store Knowledge and Keeps Answers Current

You will understand how Appifire syncs store knowledge and what to do so chat answers stay current. When you finish, you will know which Data Sync cards to use, how Knowledge Hub differs, and why orders are not a sync job.

For product-only change habits, see How to Keep AI Product Answers Accurate When Catalog Details Change. For Knowledge Hub setup, see Set Up Website Knowledge and FAQs in Appifire.

Direct answer

Appifire keeps answers current in three lanes:

1. Data Sync pulls Shopify products, categories (collections), stock levels, and articles (blog posts) into Appifire knowledge.
2. Knowledge Hub holds editable website knowledge and FAQ text (policies and common Q&A).
3. Orders are not synced. Chat looks up a live Shopify order when the shopper shares an order number.

Use individual Update … buttons for one section, or Update everything to refresh all four Data Sync sections together. Many single product edits also re-ingest through Shopify webhooks; still run Data Sync after big bulk changes.

Prerequisites

• Appifire installed (Getting Started)
• Access to Appifire Data Sync and Knowledge Hub
• Products you care about are active and published on the online store
• Optional: storefront widget ready so you can re-test after a sync

Step 1: Know the two knowledge homes

Home	What it stores	Merchant action
Data Sync	Catalog-shaped Shopify data: products, categories, stock levels, articles	Click Update … or Update everything
Knowledge Hub	Website knowledge + FAQ you edit/save	Edit text, then Save content so chat can use it
Orders (not a sync card)	Nothing stored long-term for RAG	Shopper provides order #; Appifire fetches live

Do not paste your whole catalog into Knowledge Hub. Put SKU facts on Shopify products, then sync.

Expected result: You stop treating “sync” and “Knowledge Hub” as the same button.

Step 2: Read the Data Sync cards (current UI)

Open Appifire → Data Sync. You should see:

Update everything

One primary action that refreshes products, categories, stock levels, and articles in one step. Use after season drops, migrations, or when several sections look stale. For the decision table (single Update vs full refresh) and retry rules, see Appifire Data Sync: When to Use “Update Everything”.

Products

• Update products
• Powers answers about what you sell (titles, descriptions, variants, prices in synced text).
• Only published, active products should appear in chat answers and product cards. Draft/unpublished should drop out after sync/purge.
• Zero inventory can still answer if the product stays published.

Categories

• UI title: Categories (Shopify collections)
• Update categories
• Helps chat understand how the store is organized for discovery-style questions.

Stock levels

• Update stock levels
• Refreshes availability data across locations for stock-related answers.
• Stock sync is separate from “unpublish this product.” If you need a product gone from recommendations, change publish/status, then update products.

Articles

• UI title: Articles (Shopify blogs/articles)
• Update articles
• Uses blog/article content for helpful brand and how-to style answers when that content is synced.

Each card shows saved counts and last sync timing when available. Labels can move slightly after releases; follow the Data Sync page you see.

Expected result: You can map “I changed X in Shopify” to the right Update button.

Step 3: How answers stay current (automatic + manual)

Change type	Typical freshness path
Single product create/update/delete	Shopify webhooks often re-ingest; re-test chat; run Update products if still stale
Bulk CSV / many unpublished SKUs	Update products or Update everything, then re-test
New collection structure	Update categories
Inventory-only moves	Update stock levels
New help article on the blog	Update articles
Shipping/returns policy rewrite	Edit live policy pages, then update Knowledge Hub and save
“Where is order #1001?”	No Data Sync; live order lookup in chat

Expected result: You pick webhook patience vs a manual sync on purpose.

Step 4: Keep Knowledge Hub in the loop

Policies and FAQ paraphrases live in Knowledge Hub, not in the four Data Sync cards.

1. Keep public shipping/returns pages true.
2. Open Knowledge Hub, edit website knowledge and Q: / A: FAQ lines.
3. Click Save content so text is ingested for chat.
4. Do not trust unedited auto-fetched drafts for legal wording.

Details: How to Teach Appifire About Shipping, Returns, and Store Policies.

Expected result: Policy answers match your pages after a Hub save, not only after Data Sync.

Step 5: Re-test after you refresh knowledge

1. Note what you changed in Shopify or Knowledge Hub.
2. Run the matching Data Sync action (or save Hub content).
3. On the storefront, ask 3 questions that should use that change (product fact, category/discovery, stock, article, or policy).
4. For orders, test with a real order number separately.
5. If cards or titles look wrong, confirm publish status and exact titles (product cards guide).

Expected result: You prove freshness with questions, not only a green sync status.

Common failures and fixes

Failure	Fix
Edited PDP, chat still old	Wait for webhook or Update products; confirm live PDP first
Draft product still discussed	Unpublish/draft correctly; sync products so RAG purges it
Policy wrong after catalog sync	Update Knowledge Hub, not only Data Sync
Stock answer wrong	Update stock levels; confirm Shopify inventory truth
Blog tip never appears in chat	Update articles; confirm the article is published in Shopify
Order status “needs sync”	Orders are live lookup; check order # and order access
Empty catalog after install	Wait for first bootstrap sync or run Update everything

Verification checklist

• Can open Data Sync and name the four cards
• Know when to use Update everything vs one card
• Know Knowledge Hub is for policies/FAQ
• Know orders are not synced
• After a real catalog edit, re-tested chat on the storefront
• Published/active rules understood for product answers and cards

When to escalate

Escalate with shop domain, UTC time, which Update button you ran, and example questions if:

• Sync shows completed but chat still quotes deleted/unpublished products after a full products update
• Data Sync errors repeat after retries
• Order lookup fails for real orders while other chat works (troubleshooting playbook)

Limits and non-goals

• Data Sync does not sync orders.
• Metafield-only facts that never appear in synced product text may not reach product answers.
• Stock sync does not replace clear OOS messaging on the PDP.
• Knowledge Hub save is required after policy edits; Data Sync alone will not rewrite Hub text.
• Update everything refreshes the four Data Sync sections; it does not replace Hub editing.

Related Appifire guides

• How Appifire Uses Shopify Product Information to Answer Questions
• How to Keep AI Product Answers Accurate When Catalog Details Change
• Set Up Website Knowledge and FAQs in Appifire
• How Order Status and Tracking Work in Appifire Chat
• Getting Started With Appifire AI Chat
• Or open appifire.com

Last verified

2026-09-09 against Appifire Data Sync UI (Update everything; Update products / categories / stock levels / articles) and product docs (webhooks, published/active RAG, orders on-the-fly, Knowledge Hub separate). Re-check button labels after app updates.

Next action

Open Data Sync and note last sync times on each card. If you changed products this week, click Update products, then ask one known SKU question on the storefront. If policies changed, save Knowledge Hub next, not another product sync.