Concept illustration of organizing store knowledge for AI answers
AI-generated concept illustration, not an actual app screenshot.

What the app changes

Shopify Knowledge Base organizes store facts and FAQs for AI shopping answers. The FAQs do not appear directly as a storefront FAQ page. Shopify also states that the app does not increase how often a store appears in AI platform results. Treat it as work on the information available when a store is mentioned. Knowledge Base overview

This guide uses official documentation checked on September 6, 2026. The operating examples are proposed workflows, not results from an installation. We do not assume that every AI service consumes these FAQs or that an edit reaches every service immediately.

Install the right app and identify its job

The official listing identifies Shopify as the developer, lists the app as free and shows an English interface. Shopify Knowledge Base listing

From the listing, select Install, review the store and requested access, and complete installation. Shopify documents this sequence for App Store installations. Installing apps

Knowledge Base is also among the store sources available to the Inbox agent, which operates in the online-store chat widget. Installing a knowledge source is separate from configuring that customer conversation experience. Inbox agent sources and scope

If your actual goal is to let staff or an agent respond to visitors, use our Inbox setup guide. For this task, define success as correct, maintainable answers to store questions. Do not count a saved FAQ as a completed chat rollout.

The essential FAQ controls

Open Apps → Knowledge Base. Use Add FAQ, enter a question and a brief answer, then Save. To modify an automatically generated answer, select it under Store FAQs and use Override; Return to default restores its source-based answer. In the query log, Test your knowledge base shows matched resources or Unanswered. Stores operate independently, and a single FAQ cannot hold multiple language versions within one store. FAQ controls and limits

Keep the first setup small enough to inspect every answer. Start with a single topic, such as pickup or shipping regions, rather than writing a long collection of loosely related questions. The following process is our recommended way to use those controls.

Decide whether the source or the FAQ needs changing

Create a working sheet with five columns: question, expected answer, authoritative source, owner and review date. Use the current business rule as the expected answer, not the wording already generated by the app.

Suppose your store offers pickup at one location and an answer suggests it is available everywhere. First inspect the location and delivery settings used by your store. If those settings misrepresent your operation, correct the underlying configuration through its normal review process. A polished FAQ should not conceal a configuration mistake that still affects checkout.

If the configuration is correct but the answer needs a qualification, document that qualification before creating an override. Record why the override exists. This prevents a later editor from removing apparently redundant text without understanding the exception it preserves.

Avoid using one FAQ to compensate for several contradictory pages. For example, a campaign page, shipping policy and custom answer might give different pickup hours. Assign a person to reconcile those sources together. Keep operational changes separate from wording changes so that a content editor does not accidentally redefine a service.

Write one answer around one decision

Choose questions with a clear subject and scope. “Can I collect an online order at the downtown location?” is easier to maintain than “How does shopping work?” Include the condition and the next step in the answer; leave unrelated product claims out.

As a fictional example, a store that genuinely offers pickup only at its downtown location could answer: “Online-order pickup is available only at our downtown location. Choose pickup at checkout and wait for the ready-for-collection notification before visiting.” Use that wording only if every step matches the real store configuration.

Do not paste a private customer's order number, address or exception into a reusable FAQ. Turn the recurring issue into a general question and keep individual resolution in the support conversation. An answer about the standard process should not imply that a specific order has already been approved.

Check which source a question finds

Use a small question set: the direct FAQ wording, an everyday paraphrase and a nearby question that requires a different answer. For pickup, compare “Where can I collect?” with “Can someone else collect?” and “Is my order ready?” They share vocabulary but ask different things.

When inspecting matches, record whether the selected resource actually supports the needed answer. If several resources match, look for contradictory conditions. If nothing matches, decide whether the question needs a new FAQ or whether it requires order-specific handling outside this content task.

A matching resource is evidence about retrieval, not proof of the exact answer every customer will see on every AI platform. Record the test wording and source result separately from any later observation of a customer-facing response. This distinction makes a failed check easier to diagnose.

Use query data to choose the next correction

The query log provides agent, question, matched source and date, with answered and unanswered filters. Shopify notes that data appears only after products begin appearing in AI shopping conversations. FAQ metrics

An empty log is not a reason to manufacture demand or report a zero market opportunity. Prepare essential answers and revisit the available observations later. When queries appear, group them by the business decision they expose rather than counting every paraphrase as a separate content project.

After a policy change, recheck the affected questions, their overrides and any independently maintained market versions. Keep a record of the previous answer and the effective date. This is an operational recommendation, not an automatic cross-store synchronization feature.

Use our product-description workflow when the missing information belongs to a product. Reserve Knowledge Base work for clarifying store knowledge, and evaluate chat behavior in its own customer journey.

Check the official Shopify Knowledge Base guide for your next stepRead the official guide ↗

Related articles