SafeSale · Blog

Shopify's Knowledge base and your sale: what to tell AI agents

Shopify now has a Knowledge base for AI agents in the admin. Which sale facts to publish, how wording differs per SafeSale mechanism, when to unpublish.

On 26 October 2026 Shopify moved its Knowledge base into the admin, under Sales channels, Agentic. It replaces the standalone Knowledge Base app, which disappears after 15 January 2027. The page holds the facts AI agents get about your store that are not product data: contact details, delivery times, the return process, gift services, payment options. Shopify drafts a first set from your published storefront pages, each fact linking back to the page it came from, and nothing it drafted reaches an agent until you publish it.

We have written before about what agents see of a sale price and of a compare-at price. Both of those live in the product catalog and need nothing from you beyond running the sale correctly. This post is about the other half of a sale, the part that is not a number on a variant: when it ends, what it covers, whether the shopper has to do anything, and what happens if they want to return a sale item. That half now has a home, and the wording depends on which SafeSale mechanism you used.

What the Knowledge base is, and is not

Shopify's help page describes the published facts as "the source of truth for AI agents for all non-product information about your store". An agent answering a shopper in Shop, in a chat assistant or on a third-party platform queries them through the Storefront MCP, alongside the product search it already had. Facts fall into ten categories, from returns and warranty to payment options, plus an Additional facts category for anything you write yourself. The page accepts up to 1,000 additional facts, which for a sale is a rounding error: you need two or three.

Three rules from the help page shape everything below. Published facts are public, usable by Shop and by third-party platforms, so write them as you would write a banner, not an internal note. Facts Shopify drafts from a storefront scan stay unpublished until you say so. And facts linked to admin settings, such as your policies and contact details, are published when Shopify creates them, so your return policy is probably already live there whether you have looked or not.

Why a sale needs facts at all

Picture the questions a shopper asks an assistant during a sale. "Is there a sale on at this store?" "How long does the 20% off last?" "Do I need a code?" "Is the sale price what I see, or does it come off at checkout?" "Can I return a sale item?" Not one of those is answered by a variant price. The agent has the catalog, so it can tell the shopper that a jacket costs 79 today and used to cost 99 if your compare-at is set. It cannot tell them the 79 ends on Sunday at midnight, because no product field says so. SafeSale knows the end date, but it is in SafeSale and in your head, not anywhere an agent can read.

Without a fact, an agent does one of two things. It says it does not know, which is the acceptable outcome. Or it infers from whatever it can see, a homepage banner Shopify scanned last week, and tells the shopper something that was true then. Facts exist so you can replace inference with a sentence you wrote.

The mechanism changes the wording

SafeSale runs a sale one of two ways, and an agent experiences them differently, so the fact has to match.

With the price rewrite mechanism, SafeSale writes the sale price into each variant and moves the old price into compare-at. An agent reading the catalog quotes the reduced price as the price, with the old one as the reference. The fact should say exactly that: the prices shown are already reduced, no code is needed and nothing further comes off in the cart. Otherwise a shopper who reads "20% off everything" next to a price that is already 20% lower expects a second cut and feels cheated at checkout.

With the automatic discount mechanism, SafeSale creates a Shopify discount and leaves the product fields alone. The catalog still shows full price, the agent quotes full price, and the reduction appears as a line in the cart. Here the fact has to do the opposite job: tell the shopper that the price on the product is before the sale, that the discount is applied automatically in the cart, and what it is called. SafeSale titles the discount with the sale's name, so if your sale is "Autumn 20", the cart line says Autumn 20 and the fact should use the same words. An agent that can match the name it was told to the line the shopper sees has closed the loop.

The three facts worth writing

Keep each one to a sentence or two. Agents quote facts, and a short fact gets quoted whole.

  1. Scope and end. "Our Autumn 20 sale gives 20% off all knitwear until Sunday 8 November 2026 at 23:59 Central European Time." Name the sale, the scope, the end date and the time zone. SafeSale schedules the end in your store's time zone; the time zone post explains why "midnight" needs a qualifier, and so does a fact that a shopper in another country will read.
  2. How it applies. One of the two sentences from the previous section, matching your mechanism. This is the fact most likely to be missing and most likely to cause a complaint.
  3. Exclusions and returns. Gift cards are excluded from SafeSale sales under both mechanisms, as explained in the gift card post, and any vendor or collection you left out deserves a mention. If sale items follow a different return rule, say so here, or confirm that the normal policy applies; your return policy is likely already a published, admin-linked fact, and the sale fact should agree with it.

When to publish, when to unpublish

The tempting plan is to publish the facts the day you schedule the sale and forget them. Resist the first half: a published fact is public through the Storefront MCP, so publishing the dates of a Black Friday sale two weeks early announces it to every agent, and to anyone who asks one. If you would not put the dates on your homepage yet, do not put them in the Knowledge base yet. Publish when the sale starts, or when your own announcement goes out, whichever you would do for the banner.

The second half is the dangerous one. SafeSale ends the sale on its own: it restores the snapshot prices or removes the discount, and the store is back to normal without you. The fact is not. A fact that says "20% off until Sunday" is harmless on Monday only if the agent reads the date and reasons about it, which you should not count on. A fact that says "20% off all knitwear, applied in the cart" with no date is actively wrong on Monday, and the shopper finds out at checkout. That is the same shape of problem SafeSale exists to prevent on the price side, stale state left behind after a sale, and the fix is the same: make the clean-up part of the end, not an afterthought. When you check the restored prices on Monday morning, unpublish or edit the sale facts in the same sitting. Unpublishing keeps the fact for next time; editing it to "our next sale will be announced on this page" is also fine.

Watch what Shopify drafts

Shopify builds draft facts by scanning your published storefront pages. A sale banner on the homepage, a "Sale" collection description, an announcement bar: any of these can turn into a drafted fact that mentions the sale. Drafts are unpublished until you act, so there is no harm in them sitting there. The harm comes a month later, when you are approving a batch of drafts about shipping and a stale "20% off knitwear" draft slips through with them. Each draft links to the page it came from; if the page no longer says it, dismiss the draft rather than publishing it.

A routine that fits on an index card

  1. When you confirm a sale in SafeSale, write the three facts in a note with the sale, using the sale's name and the mechanism's wording.
  2. When the sale starts (or your announcement goes out), publish them under Sales channels, Agentic, Knowledge base, in Additional facts.
  3. Ask an agent. Open Shop or any assistant that reads Shopify stores and ask "is there a sale on at [your store]". Check the answer matches your cart.
  4. When the sale ends, check the restored prices, then unpublish the facts and dismiss any drafts the scan produced about the sale.

SafeSale handles the prices and the discount, before, during and after. The Knowledge base is the first place where what you tell shoppers about a sale is machine-readable, and for now it is yours to keep honest.

Frequently asked questions

Does SafeSale write to the Shopify Knowledge base?

No. SafeSale changes prices or creates an automatic discount, and restores or removes them when the sale ends. The Knowledge base is a page you manage in the admin under Sales channels, Agentic. Adding and unpublishing the sale fact is a step for you, and this post suggests where to put it in your routine.

Do AI agents need a Knowledge base fact to see my sale prices?

Not for the prices themselves. Prices and compare-at prices are product data, and agents read those from the catalog. The Knowledge base is for the non-product part: when the sale ends, whether a discount applies in the cart, what is excluded, and how returns work on sale items.

Should I publish the sale dates before the sale starts?

Only if you would put them on your homepage. Published facts are public through the Storefront MCP, so Shop, third-party agents and anyone who asks can read them. Announcing a scheduled sale early is a marketing decision, not a technical one.

What happens if I forget to unpublish the fact when the sale ends?

Agents keep telling shoppers the sale is on, while SafeSale has already restored the prices or removed the discount. The shopper reaches a cart that does not match what they were told. Unpublishing takes seconds and belongs in the same checklist as checking the restored prices.