Verify every Shopify Agentic Storefronts knowledge base fact against its source, current store policy and customer-facing page before publishing it. This process is for merchants preparing AI channels and the staff responsible for store policies, contact details and brand information. A completed review reduces avoidable inconsistencies; it does not guarantee that an AI channel will show or accurately repeat a fact.
Who this is for: Shopify merchants preparing store information for AI channels.
Operations staff maintaining policies, delivery details and brand facts.
Business leads deciding which claims are ready for public use.
Last updated November 6, 2026. Shopify help documentation and the Fall ’26 Edition information were checked for this review. Confirm the latest guidance and the controls available in your own admin before making changes.
Shopify Agentic Storefronts knowledge base verification: what it covers
Treat the knowledge base as a place to review non-product store facts used in AI queries—not as a product catalogue, an order-attribution report or proof of what a channel will display. Shopify describes the knowledge base as managing non-product information and its sources, review and publication status in the official knowledge base documentation.
Keep three evidence layers separate:
- Knowledge base fact: the claim and status shown in your Shopify admin.
- Store source: the current policy, settings or approved brand material that supports the claim.
- Customer-facing evidence: the published page or contact route a shopper can access.
A match across those layers is a release condition for your content review. It is not a promise about channel inclusion, wording, ranking, conversions or regulatory compliance. Shopify’s Agentic Storefronts management documentation is the place to check current management guidance. The actual controls available to you may depend on the current rollout and your account, so verify both the help page and your own admin.
Keep this review separate from Shopify Storefront MCP implementation work. The Storefront MCP documentation describes a developer-facing integration area. It does not replace reviewing the truth, scope and publication status of your store’s knowledge base.
Source review before customer-visible claims
For each fact, identify its original source before deciding whether to publish it. A knowledge base entry is not self-validating: it may reflect old wording, an incomplete page or a claim that only applies to one market.
Use this evidence order:
- Current operational source: policy text, shipping settings, current contact details or approved brand materials.
- Public customer page: the live page that communicates the same fact to shoppers.
- Knowledge base entry: the fact as recorded in the admin, including the available source, citation and publication status.
If the public page and operational source disagree, do not choose whichever wording sounds more convenient. Resolve the underlying store information first. Then check whether the knowledge base entry and its citation need an update. This prevents a narrow correction in one place from leaving a contradictory promise elsewhere.
Shopify announced that the old Knowledge Base app was replaced by the new knowledge base. Merchants with more than 1,000 facts in the old app must manually migrate additional facts and overrides by January 15, 2027, according to Shopify’s migration announcement. If that applies to your store, treat migration as a separate reconciliation task: confirm that each carried-over fact is still valid and supported before publishing it. Do not assume that moving content also verifies it.
Returns, refunds and warranties
Returns often combine a policy statement, an operational process and a customer-facing route. Check them as separate claims instead of treating a general “returns accepted” statement as sufficient.
Verify that:
- The return window matches the current policy and any conditions are stated clearly.
- Refund wording does not promise a method or timing that the store’s actual process cannot support.
- Warranty or guarantee language has a current source and applies to the products described.
- Any self-service return link opens for a customer and leads to the intended flow.
- Market-specific or product-specific exceptions are not rewritten as universal rules.
Shopify’s policy settings guidance explains the relevant store policy area. Use it to locate the official setting, then compare the exact wording with the customer-facing policy page. The verification target is your store’s actual commitment, not a generic policy template.
When there is a mismatch, correct the policy or customer page first if that is the authoritative source. Then review the knowledge base fact and its citation. If you change only the knowledge base, shoppers may still see a conflicting policy. If you change only the page, the AI-facing information may remain stale.
Shipping, payment and contact scope
Delivery promises by market
Shipping claims need a defined market and a defensible boundary. Check each relevant destination against the store’s shipping zones, applicable rates and delivery estimates. Shopify’s shipping rates setup documentation covers shipping zones and rates; use your current settings and public shipping policy to confirm what your store actually offers.
Avoid broad language such as “worldwide delivery” if availability depends on destination, product, carrier or order conditions. A delivery estimate should not be presented as a guarantee unless your store’s evidence supports that commitment. If a fact applies only to selected markets, name the scope or hold the fact until it can be expressed accurately.
Payment methods and contact routes
Check each payment method against what your store currently offers to the relevant market. Do not turn a method available in one market or checkout condition into a global claim. If availability varies, define the scope clearly or leave the fact unpublished until the wording can reflect the difference.
Test contact information as a customer would:
- Confirm the support email is active and reaches the right team.
- Check that any listed phone number is current and appropriate for customer enquiries.
- Open social account links and verify they belong to the business and remain public.
- Confirm that contact details on the knowledge base match the public contact page.
A contact fact can be technically correct but operationally unhelpful if it sends customers to an unattended inbox or an account that is no longer maintained. Record who owns each route so that future changes have a clear reviewer.
Brand facts and publication decisions
Brand values, business descriptions and other supplementary facts need evidence too. “About us” copy may be useful context, but a factual claim about materials, sourcing, service coverage or business history should have a source that supports that specific claim.
Check whether each cited link is publicly accessible and directly relevant. A page that requires staff access, redirects unexpectedly or discusses a different subject is weak support for a public-facing fact. Manually maintained content deserves the same review as scanned suggestions. An automated scan can surface a candidate; it cannot approve the candidate on your behalf.
Use a clear release rating for each entry:
- Pass: the source is current, the claim is correctly scoped, the public page agrees and the publication state is intentional.
- Conditional: the claim is supportable but needs narrower wording, a market qualifier or a page correction before release.
- Hold: the source is missing, the evidence conflicts, the link is inaccessible or the claim cannot be verified.
These are internal review labels, not Shopify ratings. Keep the decision, evidence and reviewer together so another operator can understand why a fact was released or withheld.
A published knowledge base fact is not evidence that an AI channel has retrieved it. Treat store-side publication and channel-side behavior as separate checks.
Pre-publication checklist
Use this checklist for each fact or coherent group of facts. If any item is unresolved, hold the affected claim rather than publishing it by default.
- [ ] I can identify the original source for the fact.
- [ ] The source is current and supports the exact wording.
- [ ] The fact has a clear scope: market, product, order condition or customer group where relevant.
- [ ] The matching customer-facing page is public and accessible.
- [ ] The page and the current operational setting do not conflict.
- [ ] Any citation opens and supports the claim it is attached to.
- [ ] The fact’s publication status is intentional and visible in the admin.
- [ ] A named owner has reviewed the evidence and recorded the decision.
- [ ] Unconfirmed or overbroad claims are held rather than treated as approved.
- [ ] The review record includes the fact, source, customer-page evidence, reviewer and release decision.
Save that record in the team’s normal operational documentation. It makes later policy changes easier to trace and avoids relying on an operator’s memory of why a statement was published.
FAQ: review and update controls
Where should you look for the knowledge base?
Open the Agentic Storefronts management area in your Shopify admin and use Shopify’s current help documentation to confirm the location and available controls. The admin is the source for your store’s current entries and statuses; the documentation explains Shopify’s intended workflow. If the interface differs from the help page, verify the feature’s availability for your account before relying on an assumed control.
How do you compare return and shipping details?
Start with the current policy and operational settings, then open the public customer page and compare the wording with the knowledge base. For returns, check the window, refund terms and return route. For shipping, check destinations, rates and estimates. If one source disagrees, resolve the underlying store policy or settings first, then review the knowledge base claim and publication status.
Should scanned facts be published automatically?
No. Review each suggestion as an unapproved candidate. Check the source, citation, exact claim, market scope and customer-facing page. If the scan has combined separate conditions or inferred a broader claim than your evidence supports, edit or hold it. Assign a reviewer and keep the evidence with the decision; the presence of a suggested fact in the admin is not a substitute for approval.
What confirms an update is ready for AI channels?
Confirm that the updated entry appears correctly in the admin and has the intended publication status, then follow current Shopify guidance for knowledge base updates. That confirms the store-side change only. It does not establish that an AI channel has read, displayed or accurately paraphrased the entry. Check customer-facing pages separately, and do not treat a successful page review as proof of channel behavior.
Review cadence and customer-page testing
Assign an owner to revisit the relevant facts whenever a return policy, shipping condition, payment option, contact route or brand statement changes. Also review facts affected by a market expansion or a change to the public page that supports them. Shopify may update migration, publication or permission guidance, so revisit the current knowledge base documentation when the admin workflow changes.
A knowledge base review and a customer-browser review answer different questions. The first checks store facts, sources and publication state. The second checks what a shopper can actually see: whether policy links load, text fits the page, navigation works and the customer experience is coherent. Neither test proves that a particular AI channel will show the same information.
For a browser check that specifically requires macOS Safari, your existing Windows or Linux browser setup may not reproduce Safari behavior. A local Mac gives you direct hardware access but ties the test to that machine and location. Browser emulation can help with general layout checks, but it is not the same as inspecting the page in Safari. A remote Mac can be useful for temporary, real-Safari testing without buying a device; it still cannot validate AI-channel retrieval or answer accuracy.
If Safari is part of your release review, see the remote desktop options and compare them with your testing schedule. For a short verification project, a temporary environment may be more practical than buying hardware. If your team needs continuous access, relies on physical peripherals or runs sustained workloads, a dedicated local Mac may fit better. Check the available plans against your access and runtime needs before choosing. Use any Mac environment only to inspect the customer-facing storefront—not as evidence that AI channels have accepted, indexed or correctly presented your facts.
Your release decision should stay simple: publish only claims with current sources, matching public pages and an intentional status. Hold anything that is unclear, and record who will recheck it when the underlying store information changes.
Frequently asked questions
Where can I review the Agentic Storefronts knowledge base in Shopify?
Open the Agentic Storefronts management area in your Shopify admin and review the knowledge base there. The exact location and available controls may depend on your account and Shopify’s current rollout, so confirm them in Shopify’s current help documentation and your own admin. Check the source, citation and publication status for each fact; don’t treat a suggested fact as approved just because it appears in the interface.
How should I check return and shipping facts against my store?
Compare each knowledge base entry with the current policy or operational source and the customer-facing page where a shopper can verify it. For returns, check the stated window, refund terms, warranty language and self-service route. For shipping, confirm eligible regions, rates and delivery estimates against your current settings. If they disagree, correct the source information first, then review the knowledge base entry again.
Can I publish facts Shopify has scanned from my store without reviewing them?
No. Treat scanned facts as candidates, not approved statements. Confirm that each claim has a reliable source, applies to the markets and products described, and matches the public page customers can access. If a source is unclear, a page is outdated or the claim is too broad, hold publication until the responsible owner resolves the mismatch. Keep a record of who reviewed the fact and what evidence supported the decision.
How do I know AI channels can read a knowledge base change?
Confirm the revised fact and its publication status in the admin, then check the relevant official Shopify documentation for how updates are managed. That verifies the store-side change, not what an individual AI channel will retrieve or display. Channel behavior can vary, and a published entry is not proof of visibility, accurate paraphrasing or sales. Use a separate customer-experience test when you need to inspect a live store page.
Verify Storefront Updates on a Remote Mac
Rent a VPSPush M4 dedicated physical Mac and review your customer-facing storefront from a remote desktop.
