Shopify Knowledge Base now lives inside your admin, and the standalone app is due to disappear on January 15, 2027. The useful work starts before that deadline: check which store facts have already been published, remove promises your team can’t fulfil, and give someone responsibility for keeping the answers current. Here’s how we’d handle the move without turning it into another sprawling AI project.
What changed in Shopify Knowledge Base?
In its October 26 changelog announcement, Shopify says Knowledge base is now available at Sales channels > Agentic > Knowledge base. It replaces the standalone Knowledge Base app.
The built-in page lets merchants review, edit and publish facts that AI agents receive about their store. Shopify gives contact details and gift services as examples. Shopify drafts facts from your published storefront pages, and each draft links back to its source page.
Shopify-drafted facts do not reach AI agents until you publish them. That approval step matters. A sentence can accurately reflect an old page and still describe a service you stopped offering.
There’s also a migration detail worth checking immediately. For stores with fewer than 1,000 facts, Shopify says facts merchants wrote or edited moved across and were published. Don’t assume everything in the new location is waiting for approval.
If your store has 1,000 or more facts, confirm the applicable migration instructions and your actual admin state before making changes. The migration detail above applies specifically to the smaller-store group; it shouldn’t become a blanket assumption.
Shopify Knowledge Base migration starts with published facts
Our recommendation is to inspect what agents can already receive before polishing unpublished drafts. Existing exposure deserves attention first.
Open Knowledge base and compare the facts there with the information your customer service team currently uses. Keep a separate review record with the fact’s wording, its source page, its publication status and the person responsible for approval. This is an operational recommendation, not a claim that Shopify provides a dedicated audit log for this process.
Prioritise facts whose errors would create a broken customer promise:
- Contact details: Check that the published address reaches a monitored inbox and that any stated availability matches actual coverage.
- Gift services: Confirm which orders qualify and whether the service carries an additional charge.
- Delivery claims: Look for broad promises copied from pages that omit destination or product restrictions.
- Returns information: Check that the wording preserves relevant exceptions rather than reducing a conditional policy to a universal promise.
Those last categories are suggested review priorities where they appear in your store’s facts, not a guaranteed list of Shopify-generated fields.
Ask customer service to approve the meaning, not just the grammar. Someone who handles complaints is more likely to spot the difference between “gift packaging available” and “gift packaging available for every item.”
Fix the source page, then check the fact
The source link is one of the most useful parts of this update. It gives reviewers somewhere to investigate when a fact looks suspicious.
Imagine a gift-services page that still advertises wrapping across the catalogue, although your warehouse now excludes oversized products. That’s a hypothetical example, but the review process is straightforward: verify the operational rule, correct the public page, then check the corresponding Knowledge base wording before publication.
Editing only the agent-facing fact leaves shoppers reading an inaccurate storefront page. Editing only the storefront page leaves the status of the agent-facing fact unresolved. Check both. The supplied announcement does not establish an automatic refresh schedule, so don’t assume a page edit instantly updates a published fact.
Write answers that survive without surrounding context
A useful store fact should make sense when read on its own. Avoid references such as “the above exclusions” or “this service” if the underlying subject would be unclear outside the original page.
For the hypothetical gift service, a clearer answer would identify the eligible product group and explain where customers can confirm availability. Publish that wording only if it matches your actual process.
Keep marketing language out of operational answers. “Beautifully wrapped for every occasion” tells an agent less than a plain explanation of which items qualify. You can keep the personality on the landing page without asking it to carry the policy.
Treat publication as approval of a customer promise
We’d assign one accountable owner for publication, with operational reviewers for facts that affect their departments. A content editor can improve clarity. The warehouse team must confirm what can actually leave the building.
Use a short approval checklist:
- Does the source page describe the current service?
- Does the fact retain the restrictions a customer needs to know?
- Would customer service give the same answer?
- Is there a known event that should trigger another review?
That final question catches facts with a short shelf life. Seasonal gift services may need review when a campaign ends. A support-address change should trigger a contact-fact check. Delivery promises need attention when fulfilment arrangements change.
A published fact is an operational commitment, not simply an approved piece of copy. That’s the standard we’d use when deciding who gets the final say.
Don’t publish a questionable fact just to clear the draft list. Resolve the uncertainty first. A full page of approved answers is not a useful success measure if your team can’t stand behind them.
Where automation helps, and where it doesn’t
The current crop of ecommerce AI tools makes it tempting to automate the entire review. We’d keep the final approval human, especially when a fact describes a service exception.
There is a practical role for workflow automation around the process. In its review of ecommerce operations tools, Yotpo describes Shopify Flow as a conditional workflow tool and gives inventory-threshold alerts as an example. That kind of rule-based notification is useful when a detectable operational change should prompt someone to review customer-facing information.
Flow is worth considering if your team already uses it and a supported trigger matches the event you need to monitor. We would not add automation just to manage an occasional policy edit. A task in the existing campaign checklist may do the job better.
Crucially, that review does not establish a direct Flow integration with Knowledge base. Don’t plan automatic fact publication around an assumed connector. Define the review task first, then verify whether the available triggers and actions can support it.
Check the customer journey without promising AI visibility
After the fact review, test the same questions against your public storefront. Can a shopper find the answer? Does the answer agree with what you approved for agents? Record contradictions and fix them at the source.
You can also ask relevant shopping assistants those questions and record the answers you observe. Treat this as a diagnostic exercise. Publishing a fact does not establish that every assistant will use it, show it immediately or recommend your store.
Keep internal correctness separate from external behaviour. Your team controls the published information. It does not control every agent’s retrieval process or response.
The wider payments news makes that distinction useful. Digital Commerce 360 reports that American Express’s Intent Intelligence framework is designed to document and verify consumer instructions before AI shopping agents complete transactions. That addresses what the buyer authorised. Your store facts address what the merchant says it offers.
These are different responsibilities. We wouldn’t interpret the American Express announcement as evidence of a Shopify integration or a new merchant requirement. For a Shopify team, the actionable lesson is to keep service promises precise enough that a purchase based on them won’t surprise either party.
What to finish before the standalone app disappears
Before January 15, 2027, confirm that the relevant team members can find the built-in Knowledge base and know who owns it. Check the migration result against your review record rather than relying on memory.
Replace internal instructions that send colleagues to the standalone app. Add a Knowledge base review to the procedures that change public service information, including seasonal campaign closeouts. If a fact remains unresolved, give it an owner and a clear next action.
We’d judge completion by whether published answers are accurate and maintainable. The app’s retirement is a deadline. Reliable store information is the ongoing job.
Takeaways
- Find Knowledge base under Sales channels > Agentic in Shopify admin.
- Audit migrated, published facts before concentrating on new drafts.
- Correct inaccurate storefront pages and verify the corresponding facts separately.
- Assign approval responsibility to people who can confirm the service promise.
- Update your internal process before the standalone app retires on January 15, 2027.
Sources
- American Express Launches Intent Intelligence Framework for AI Shopping Agents
- Knowledge base is now built into your admin
- 8 Best AI Tools for Ecommerce Operations in 2026 - Yotpo
Want this handled for you?
We're a Shopify Premier Partner and this is the work we do every day: performance, CRO, and store builds that pay for themselves. Book a free store review and we'll show you the three fixes we'd ship first.
Frequently asked questions
Where is Shopify Knowledge Base now?
Knowledge base is built into Shopify admin at Sales channels > Agentic > Knowledge base. Merchants can review, edit and publish store facts for AI agents there.
When does the standalone Shopify Knowledge Base app retire?
Shopify says the standalone Knowledge Base app will no longer be available after January 15, 2027. Check your migration result and update internal instructions before that date.
Does Shopify automatically publish AI-drafted store facts?
Shopify says newly drafted facts do not reach AI agents until you publish them. Migrated content is different: for stores with fewer than 1,000 facts, Shopify says merchant-written or edited facts moved across and were published.
Where do Shopify Knowledge Base drafts come from?
Shopify drafts facts from your published storefront pages. Each draft links to its source page, which lets your team check whether the underlying information is still accurate.
Does publishing Knowledge Base facts guarantee AI recommendations?
No such guarantee is established by the announcement. Publishing store facts and observing whether a particular shopping assistant uses them are separate checks.
