Shopify now drafts what AI agents hear about your store. Treat it like label copy, not a settings page.

Every CPG founder knows the back of the box gets more review than anything else the company writes. The ingredient list, the allergen statement, the net weight, the claim on the front panel: someone checks each word, someone signs off, and nobody changes it on a Friday afternoon because a draft looked fine.

On October 26 Shopify gave its merchants a new piece of copy that deserves the same treatment, and packaged it to look like a settings screen. The knowledge base is now built into the Shopify admin at Sales channels > Agentic > Knowledge base, replacing the separate Knowledge Base app, which goes away after January 15, 2027. In Shopify's own words, it is "a single page where you review, edit and publish the facts AI agents get about your store." We covered the launch in today's news.

Our argument is simple. For a brand selling food, supplements, skin care or cleaning products, this page is closer to label copy than to a store setting, and it should be run that way.

What Shopify actually built

Start with the language Shopify uses, because it is stronger than most of what we read in platform docs. The Help Center page says these facts "are the source of truth for AI agents for all non-product information about your store." When a shopper asks an [AI shopping agent](term:AI shopping agent) something about your store, "the agent can query your knowledge base through the Storefront MCP to find answers." The published knowledge base is public through that protocol and "can be used by AI channels including Shop and third-party platforms."

So this is not a help widget on your site. It is an answer sheet handed to software that talks to your customers somewhere else.

Here is what the page holds, taken from Shopify's category list, next to the question we'd ask about each one for a CPG brand.

Category (Shopify's description)	What we'd check for a CPG brand
About the Store: description, audience, ownership, history, size, business model, social mission	Is the founding story the one on your packaging and press kit, or an old About page?
Brand and Identity: your brands, third-party brands you sell, brand values and aesthetic	Does it describe values you can document, such as certifications, rather than adjectives?
Company policies: terms, privacy, shipping and returns policies, plus missing-policy alerts	Are these your real policies or the template text from when the store opened?
Contact: address, email, phone, social profiles	Is this the address you want a shopper or an agent to see?
Gift services: gift cards, receipts, registry, wrapping	Usually simple, and worth getting right before December
Payment: accepted payment methods at checkout	Does it match what your checkout actually accepts today?
Returns & warranty: policy, window, refunds, warranty, self-serve returns link	Do perishable items have a different rule, and does the fact say so?
Second hand: whether you sell second-hand products	For most CPG stores, a clean "no"
Fulfillment: shipping and delivery types such as international, express, pickup	Cold-pack shipping, heat-season pauses, regions you don't ship to
Additional facts: anything else you want agents to know	Allergen handling, facility claims, subscription rules, certifications

The mechanics matter as much as the categories. Shopify scans your published storefront and drafts facts from it, and each one links back to the page it came from. Nothing it drafted reaches agents until you publish it. Facts linked to your admin, such as store policies and contact details, are published as soon as Shopify creates them. Each field has one source and can carry several reference links, and the Help Center asks merchants to make sure the storefront matches whatever they add, with a public page as the reference. The whole thing holds 1,000 facts, a rescan can take up to 48 hours, and Shopify says it never changes knowledge base content without your approval.

That last part is good design. It is also where we think most stores will go wrong.

The draft inherits your mess

A scan of your storefront is only as good as your storefront. Think about what sits on a typical DTC food or beauty site after a couple of years: a free-shipping threshold from a summer promotion, a holiday cutoff from last December in an FAQ accordion, a "ships to Canada" line written before you stopped shipping to Canada, a sustainability paragraph a freelancer wrote at launch. People skim past all of that. A scanner reads it as fact.

Shopify has done the right thing by keeping scanned drafts unpublished. The risk is what happens next. A founder opens the page, sees ten tidy categories filled in with plausible sentences, and clicks Publish all, because the screen offers exactly that button and the drafts read well. Plausible is the problem. The errors that cost you are the ones that sound right: a 30-day return window that is 14 days for opened food, "ships nationwide" when chilled products don't ship to Hawaii.

The automatic part is quieter and, in our view, more important. Policies and contact details linked to your admin are published on creation. For many smaller brands, the shipping and refund policies in admin are still the boilerplate filled in on day one. Those are now live answers to agents, today, unless someone has read them.

Why this is label copy

Three things make this closer to the back of the box than to a settings page.

First, it is a statement to customers you won't see. On your own site you control the layout, the fine print and the context. In an agent's answer, your fact is paraphrased: Shopify notes that for paragraph facts, the agent uses your text "as the source for its answer but with its own words and phrasing." A vague fact gets paraphrased vaguely. A precise one survives.

Second, it is going to be acted on. Agents are no longer only answering questions. Forter's network data, published October 23, shows agents that drive a store's own checkout pages went from 1% of agentic orders in late July to 70% in the week of October 12. Forter's CEO, Michael Reitblat, told eCommerceNews that merchants are "effectively opted in by default, whether they've prepared for agentic traffic or not." An agent that reads "free returns" and then places the order on a shopper's behalf has turned your fact into a promise.

Third, some of these facts carry real liability. Allergen handling, "made in a nut-free facility," organic or kosher certification, age restrictions on supplements. A brand would never let an intern rewrite those on the pack. The Additional facts section, with its Paragraph, Yes/No and Tags types, is exactly where they would go. A Yes/No fact, Shopify says, "is the whole fact." There is no room for a qualifier you forgot to add.

The useful question isn't whether the drafts are good. It's who in your company is allowed to publish one.

The counterargument, and why we still land here

There's a fair objection. Plenty of agents never ask. The Storefront MCP route reaches Shop and third-party AI platforms, but the agents growing fastest in Forter's data, like Meta's Muse, work by driving a store's pages directly. Reitblat's point was that these agents "default to crawling a merchant's website if it's not optimised for agentic traffic," which "takes significantly longer, is more costly and is very error prone." If the agent is reading your pages anyway, why fuss over a separate fact sheet?

Two reasons. The first is that the knowledge base is the cheap, structured answer, and agents and platforms tend to prefer whatever is cheap and structured once it exists. We've seen the same pattern in feeds: Masters of Search reported that ChatGPT Shopping in the US runs on OpenAI's own index built from merchant feeds, while Europe still pulls from Google Shopping. The structured layer becomes the default the moment a platform can rely on it.

The second reason is the stronger one. Writing the knowledge base properly forces you to fix the storefront. Shopify's own guidance is to make the storefront match what you add, with a public reference page. If you write "we ship chilled products Monday to Wednesday only," you need a page that says that, which means the crawling agents find it too. The work pays twice.

Retailers are drawing their own lines on agents in the meantime. The RealReal tightened its bot defenses this week after The Verge showed Muse could keep items held in a cart for hours, while still letting agents surface listings and link to product pages. That is a retailer deciding what agents may do. On your own Shopify store, the knowledge base is where you decide what they may say. We wrote about the retailer side in retailers picking sides on AI agents.

What running it like label copy looks like

None of this needs a new team. It needs the habits you already have for packaging.

1. One owner. Pick the person who signs off packaging claims or the customer service policy. They publish; nobody else does.
2. Read every draft against the source page. Use the reference links Shopify attaches. If the page is wrong, fix the page first, then the fact. Our tip on the knowledge base walks through the screens.
3. Rewrite the admin policies. Since they publish automatically, they are the first thing to read. Replace template text with your actual rules, including exceptions for perishables and subscriptions.
4. Write the facts your support inbox already answers. Shipping regions, cold-pack handling, allergen handling, certifications, how subscriptions pause. Use Yes/No only where the answer truly has no exceptions.
5. Keep a change log. A dated line each time a fact changes. When an agent repeats something old, you'll know whether it came from you.
6. Tie it to your other fact sources. The knowledge base covers store facts, not products. Product facts live in your feed, your pages and your retailer listings, and all of them need to agree. Tip 5 is our checklist for that, and our earlier piece on your website as a reference book for robots makes the wider case.

Then check the result from the outside, because what you publish and what an assistant repeats are not the same thing. Ask the assistants your shoppers use the questions your facts answer, and note what comes back. Teams with many products sometimes hand that to a tool: XENA Intelligence, for example, asks assistants such as ChatGPT, Perplexity, Gemini and Amazon's assistant shopper-style questions, and its SearchPanel keeps the answers by product. A monthly spreadsheet works too.

The bigger point

For a decade, a brand's facts lived in many places and nobody was quite responsible for the whole set: the About page belonged to marketing, policies to operations, the FAQ to whoever handled support. That was tolerable when a person read them in context.

Shopify has now put the whole set on one screen and labeled it the source of truth for software that answers your customers and, increasingly, buys for them. That is a gift, honestly. It is also a test of whether a brand treats its words as product or as decoration. The drafts are a reasonable start. Publish them the way you'd approve a new label, line by line, with a name next to each one.