Skip to main content

Overview

Store knowledge is a small library of plain-language documents about your store. Layers reads these documents when it decides which tags, collections, and metafields to include in a product’s index. It also reads them when it looks into a product flagged from the How AI sees this product panel. Use store knowledge to tell Layers things a catalog alone can’t express: what a house-specific tag means, why a metafield matters to shoppers, or how to treat a naming pattern you use across products. Store knowledge documents shape how Layers makes future indexing decisions. They don’t re-rank existing search results on their own.

Before you start

  • You need permission to view the Settings → Knowledge page. Editing, creating, and archiving documents require the knowledge-edit permission. Without it, the page is read-only: the New document button, title links, and row actions don’t appear. See Manage roles and permissions.
  • Knowledge documents guide AI judgement. They don’t override deterministic ranking, request transforms, or merchandising rules.
  • Layers removes archived documents from the index it searches, so they stop influencing new decisions.

Open the Knowledge page

  1. In the Layers dashboard, open Settings.
  2. Select Knowledge in the sidebar under the search and discovery group.
  3. The page lists your documents in a table, with any pending documents shown first.
The table shows each document’s Title, Status, Scope, Tags, and when it was last Updated. Use the search box above the table to find a document.

Create a document

  1. Click New document in the top right. The document editor opens on its own page.
  2. Click the title at the top of the page and type a short name for the document. Up to 255 characters.
  3. Write the document in the Body editor. The body supports Markdown, so you can use headings, lists, and links. Switch to the Preview tab to see how it reads, and back to Write to keep editing. Up to 50,000 characters.
  4. In the Document details panel, set:
    • Scope: A label that groups related documents. New documents start in General. Open the picker to choose a scope you’ve already used, or type a new name and select Create to add one. Up to 100 characters.
    • Tags: Optional labels for organizing documents. Type a tag and press Enter or a comma to add it, or pick a tag you’ve already used from the suggestions. Remove a tag with its ×. Up to 50 tags, each up to 100 characters.
  5. Click Create. Layers saves the document and returns you to the Knowledge page.
Layers picks the document up on the next indexing decision that matches its scope. You don’t need to resync your catalog.

Edit a document

  1. On the Knowledge page, click the document’s title, or open the ⋯ menu on its row and select Edit.
  2. Update the title, body, scope, or tags. The Document details panel also shows the document’s status, when it was last updated, and who created it.
  3. Click Save Changes. The button stays disabled until you change something.

Archive a document

  1. On the Knowledge page, open the ⋯ menu on the document’s row.
  2. Select Archive.
  3. Confirm the archive prompt.
Layers removes archived documents from the AI Search index, and they no longer influence indexing decisions. Archive rather than delete when you want a document out of rotation but kept as a record.

What to write

Documents work best when they tell Layers a rule, not a goal. Keep each document focused on one topic.

House-specific tags

Metafield meaning

Naming patterns

Tips

  • One idea per document. Short, focused documents give the AI a clearer signal than a single long document that mixes topics.
  • Name the actor. Write “keep this value,” “drop this value,” “treat this collection as internal.” Instructions to a person read cleanly to the model too.
  • Reach for knowledge when a rule is store-specific. For catalog-wide behavior the search pipeline should follow, use search instructions instead.
  • Use flags to build knowledge. When you flag a value in How AI sees this product, Layers may add a document that captures the fix. Review those documents on this page and edit them if the wording is off.

Troubleshooting

My document doesn’t seem to be having any effect. Knowledge shapes new indexing decisions. Layers doesn’t automatically re-evaluate products that were already indexed before you added the document. Resync the affected products from the catalog list, or wait for the next scheduled resync. See Manually resync a single product. A value I told Layers to keep is still being dropped. Open the product in the catalog and use How AI sees this product to see the ignore reason. Flagging the exact value from that panel gives Layers a direct signal to reconcile with your document. I archived a document by mistake. Create a new document with the same body. There is no in-place restore.

Next steps