Executive summary
- What: Knowledge base is now a page in the Shopify admin at Sales channels, Agentic, Knowledge base. It replaces the standalone Knowledge Base app, which will not be available after January 15, 2027.
- Why: It is the controlled source of truth AI agents query through the Storefront MCP for every non-product question about your store, from return windows to gift services.
- Who: Brand, CX, and ecommerce leads who own policy and service copy, plus any store that had the old app installed.
What changed
The knowledge base is a single page where you review, edit, and publish facts about your store. Shopify drafts those facts by scanning your published storefront pages, and each fact links back to the page it came from, so you can check a claim against its source. Nothing Shopify drafted reaches AI agents until you publish it. Facts tied to your admin data, such as store policies and contact details, are published when Shopify creates them. The knowledge base holds 1,000 facts in total, counting both generated and additional ones.
Migration depends on size. Stores with fewer than 1,000 facts had the facts they wrote or edited moved across and published, and anything can be unpublished at any time. Stores above that count did not have facts moved and need to re-add the ones worth keeping before January 15, 2027. Shopify emailed those stores directly. Two constraints matter: a password-protected store cannot be scanned, and custom storefronts along with Agentic plan stores can add only additional facts. You can request a rescan after significant content changes.
Why it matters
AI assistants already answer pre-purchase questions about your store whether or not you curate the inputs. Left alone, an agent infers from whatever is crawlable, which in most enterprise estates includes landing pages nobody has owned for three years. The knowledge base makes that answer surface reviewable, attributable, and explicitly gated: publishing is a decision, so CX and legal can sign off on claims before an agent repeats them. For Plus merchants running several storefronts, it also makes policy drift visible, because contradictions surface as facts next to the pages that produced them. The strategic framing here is the same one we apply to AI-driven customer experience work on Shopify Plus: the model is only as good as the facts you are willing to stand behind.
Role-specific impact
- Marketers: treat facts as owned brand copy. Align shipping promises, gifting, and warranty language with live campaigns so an agent does not quote a cutoff or a return window you no longer honor.
- Developers: published facts are served through the Storefront MCP. If you run a custom storefront you can add only additional facts, and password protection blocks scanning, which matters for staging environments.
- Store admins: review each drafted fact against the page it cites, publish in deliberate batches, and check headroom against the 1,000 fact ceiling before any bulk addition.
Use-case example
Real-world scenario
A specialty retailer with 900 SKUs and a long gifting season reviews its drafted facts and finds three contradictions: a 30 day return window on the policy page against 45 days on a 2023 landing page, two different support phone numbers, and no mention of engraving lead times anywhere an agent could reach. Correcting the source pages and publishing 22 facts takes one afternoon. Over the following month support logs 14 percent fewer pre-purchase contacts about returns and shipping cutoffs, because the agent answers correctly the first time.
Implementation checklist
- Open Sales channels, Agentic, Knowledge base and read every drafted fact against the page it cites.
- Identify which facts are already published because they come from admin data, such as policies and contact details.
- Fix contradictions at the source page, not only in the fact, so the next scan agrees with you.
- Add facts agents need that your site states poorly: lead times, gift services, warranty handling, trade terms.
- Publish in batches with CX and legal sign-off rather than all at once.
- If you used the old app and hold more than 1,000 facts, rebuild the set you want before January 15, 2027.
- Schedule a quarterly review and request a rescan after any significant content change.
FAQ
Q: Does publishing a fact expose it publicly?
A: Yes. A published knowledge base is publicly available through the Storefront MCP and can be used by Shop and by third-party AI channels, so treat every fact as public brand copy rather than an internal note.
Q: We never installed the Knowledge Base app. Is there anything to do?
A: Nothing is required. Facts drafted from your storefront stay unpublished until you publish them. Reviewing them is still worthwhile, because the facts linked to your admin data are already live.
Resources
Answering customer questions with your knowledge base
Need guidance? Talk to Makro.