Most ecommerce GEO advice starts with a page: rewrite the description, add schema, answer the FAQ. Shopify's latest change moves part of the work somewhere less visible, deciding which facts about a store an AI agent should receive, where each fact comes from and who approved it.
On October 26, Shopify moved its knowledge base for AI agents into the admin, under Sales channels and Agentic. Its Help Center describes the published knowledge base as the source of truth for AI agents on all non-product information about a store. Shopify Catalog already plays that role for products. Keeping both records accurate is a governance job before it is a writing job.
What actually changed
The idea is not new. Shopify launched a standalone Knowledge Base app in May 2025 and featured it in its Summer '25 Edition. It generated AI-readable FAQs from a store's policies and settings, let merchants edit and add to them, and showed which questions shoppers asked AI agents. Shopify's Storefront MCP documentation suggested the app for managing the store policies behind its policy and FAQ tool.
What changed is where the work lives and how it is governed. Shopify's changelog says the knowledge base is now built into the admin and replaces the app, which will no longer be available after January 15, 2027. The Fall '26 Edition repeated it on October 28. Shopify now drafts facts by scanning the public storefront and sorts them into categories, from store description, target audience and brand values to policies, contact details, payment, returns, gift services and fulfillment. Merchants can add their own facts as paragraphs, yes or no answers or tags, such as materials and certifications.
Existing app users may have had their edited and additional facts transferred and published automatically. Stores above Shopify's migration limit must manually add the facts they want to retain before the standalone app is retired on January 15, 2027. Custom storefronts and stores on the Agentic plan can add only additional facts, according to Shopify's Help Center.
Newsletter
Follow the research
Research notes and analysis on how AI, digital transformation, product discovery, and customer behavior are changing commerce.
Subscribe to Hu's Weekly HootTwo records beside the storefront
For products, the Channel mapping page lets a merchant choose which product field or metafield Shopify Catalog uses for the title and description without changing what the online store shows. Merchants can also send agents the compare-at price as the list price, which Shopify passes only when it is higher than the current price, through the list_price field of the Universal Commerce Protocol (UCP). Custom variant grouping tells Catalog which separate listings are really one product.
So a Shopify merchant now manages three representations of the business: the storefront people browse, the product record Shopify Catalog supplies to AI channels and the non-product record agents can query through the knowledge base. It extends my argument that product data has become shared infrastructure to the facts around the product.
What the merchant actually controls
Facts Shopify drafts from a storefront scan start unpublished. Facts linked to admin settings, such as policies and contact details, publish when Shopify creates them. When a later scan finds something new, Shopify offers a suggested update that the merchant approves or rejects, and the Help Center says Shopify never changes knowledge base content on the merchant's behalf. A merchant can publish or unpublish the whole knowledge base, one category or a single field.
Each field has one source, a storefront scan, an admin setting or manual entry, and can carry several reference links that are passed to the agent with the fact. A rescan can take up to 48 hours and may miss changes, so Shopify suggests entering important facts directly.
What the merchant controls is the fact, not the sentence. For a paragraph fact, Shopify says an agent uses the merchant's text as its source but answers in its own words. Shopify's Ask MCP tool, ask_business, returns an answer drawn from the knowledge base and policies that the outside agent can use in its reply. Approval governs the source information, not the final wording.
Where the thesis breaks
The tempting conclusion is that ecommerce GEO now means governing what AI agents may retrieve. The evidence supports something narrower.
Shopify's Help Center describes the knowledge base as publicly available through Storefront MCP. Its current developer documentation says the older Storefront MCP catalog and cart tools were removed, while policy and FAQ questions now use Ask MCP's ask_business tool through the UCP endpoint. Ask remains a draft capability that an agent must declare. The delivery path is still evolving, which reinforces the limit: publishing a fact does not mean every agent can or will retrieve it. Shopify also names no third-party channel that queries the knowledge base.
Shopify's own Catalog documentation says inclusion does not guarantee that a product appears in an AI answer, and that each channel controls the final ranking, wording and shopping experience. The old app's help page said the knowledge base improved the accuracy of AI responses without affecting how often a store appeared. The mapping preview is not an exact picture of what an AI channel displays, and a compare-at price lets an agent show a markdown without obliging it to. Shopify has published no visibility, traffic or conversion results for any of this.
The public web does not disappear either. Some knowledge-base facts come from storefront pages, others come from Shopify admin settings or manual entries, and merchants can attach external public references. Shopify still asks merchants to keep those facts consistent with customer-facing information. The knowledge base adds a governed retrieval layer; it does not replace the public evidence behind it, much as Shopify gave the storefront a second front door for AI agents without removing the original.
What it means for ecommerce GEO
Against the six dimensions I use for ecommerce GEO, the knowledge base strengthens AI Retrievability across store-level facts. Target audience supports WHO. Policies and services support WHAT. Shipping timelines and return windows support WHEN. Locations and delivery markets support WHERE. Brand values support WHY. It can support all six dimensions, although publishing the information does not guarantee that an agent retrieves it.
The bigger change is operational. Ecommerce teams have long run the storefront, product feed, policies, informational pages and service scripts with different owners. An agent that can access those sources may treat them as one account of the business. For each fact, someone now has to decide which source owns it, what the agent should receive, who approves a suggested change and how anyone knows it is still current. Because agentic storefronts are active by default for eligible stores, and the knowledge base now sits inside the same Agentic area of the admin, this governance work can appear before a merchant has assigned anyone to own it. Policy and contact facts may already be published while storefront-drafted facts wait for review, so the operating model gets defined either deliberately or by neglect.
Start small: publish only what a public page supports, tie fast-changing facts such as return windows to their admin source or a named owner, and review suggested updates on a schedule.
When an AI agent describes your return policy next month, will anyone on your team know which source it came from?
