Skip to content

20. Products & Materials

Products and materials are the factual base for Klariton. Products provide structured catalog facts. Materials provide the source text Klariton uses for BIQs, chat answers, SafeGuard checks, and translations.

Open Products to review the product catalog imported from Shopify or maintained manually.

The product library supports:

  • search by name or description,
  • filters by manufacturer, category, source, availability, and missing touchpoint links,
  • product cards with price, availability, source, linked touchpoints, and BIQ count,
  • product detail pages,
  • manual products,
  • Shopify sync status where a Shopify connection exists.

Product data can include:

  • name,
  • description,
  • manufacturer,
  • model or variant,
  • images,
  • price and currency,
  • availability,
  • category path,
  • variants,
  • metafields,
  • source platform and external ID.

Product detail controls can affect how Klariton uses a product:

ControlMeaning
Attach to touchpointMakes the product available in a specific touchpoint context.
Exclude from recommendationsPrevents the product from being suggested in advisor flows.
Exclude from BIQsPrevents BIQ generation from using the product.
Exclude from sitemapPrevents the product from appearing in AI-facing sitemap output.
Publish product BIQsPublishes generated product BIQs where review and status allow it.

Use these controls to keep discontinued, sensitive, or unsuitable products out of generated answers and recommendations.

Use product detail when a product is missing from touchpoints, recommendations or generated BIQs.

Check:

  • product name and slug,
  • manufacturer,
  • availability,
  • price and currency,
  • images,
  • description,
  • metafields,
  • linked touchpoints,
  • generated BIQs,
  • exclusion toggles.

Metafields can contain structured Shopify data. Klariton displays them by namespace where possible. Use metafields as context, but do not assume every metafield is safe to publish. Review generated BIQs before publication.

The three product exclusion toggles have different effects:

ToggleAffectsDoes not necessarily affect
Exclude from recommendationsAdvisor and recommendation flows.Existing published BIQs.
Exclude from BIQsBIQ generation and product-based answer creation.Existing manual BIQs unless edited.
Exclude from sitemapAI-facing sitemap and crawler discovery.Normal Studio visibility.

Use all relevant toggles for discontinued, restricted, private, B-stock or legally sensitive products.

Open Material to manage the organization-wide knowledge library. Touchpoints select which materials they use.

Supported material sources include:

  • file upload: PDF, DOCX, Markdown, TXT,
  • URL import,
  • website crawl for relevant pages such as blog, pages, policies, and FAQ content,
  • conversation-derived material where enabled.

Processing states include:

StateMeaning
ProcessedIndexed and ready for retrieval.
ProcessingEmbeddings or parsing are running.
PendingWaiting to be processed.
PartialSome content was extracted, but with warnings.
FailedProcessing failed.
Bot-blockedThe source likely blocked automated access.

The material detail page shows:

  • original URL or file metadata,
  • extraction status,
  • language,
  • word count,
  • knowledge chunks,
  • embedding model and embedding cost,
  • Schema.org metadata where extracted,
  • quality heuristics,
  • linked touchpoints,
  • processing log,
  • re-index action.

If bot protection blocks a URL, use owner override plus re-crawl only when you are allowed to crawl that source. Otherwise upload the content directly or use a different source URL.

Use reparse when:

  • a source URL changed,
  • a PDF or document was replaced,
  • material extraction failed,
  • SafeGuard or BIQ generation still sees outdated text,
  • quality warnings suggest the extracted content is weak.

Reparse can update chunks, language metadata, Schema.org metadata and embeddings. After reparsing important material, review affected BIQs and translations.

Bot-blocked means the source likely refused automated access. This can happen because of:

  • cookie banners,
  • bot challenges,
  • login gates,
  • geographic blocking,
  • client-side rendering,
  • robots or rate restrictions.

If you own the source and are allowed to crawl it, use owner override and reparse. If you do not control the source, upload the relevant content manually or use an official alternative URL.

Material quality warnings can indicate:

  • cookie-banner content was extracted instead of the article,
  • content density is low,
  • layout or boilerplate dominated the page,
  • bot challenge was suspected,
  • language detection is uncertain.

Quality warnings are not always fatal, but they should be resolved before large BIQ generation or SafeGuard-dependent workflows.

Material can be linked to products and touchpoints. Use these links to keep retrieval focused.

Good linking practice:

  • link product guides to the affected products,
  • link policy pages to relevant support or FAQ touchpoints,
  • link manuals and safety instructions to product detail touchpoints,
  • avoid linking every material to every touchpoint unless it is truly global.

Focused links improve retrieval, curation quality and SafeGuard precision.

Product facts and material evidence are complementary:

  • Products provide structured attributes and recommendation context.
  • Materials provide source evidence and long-form explanations.
  • BIQs should cite material whenever factual claims go beyond basic catalog attributes.
  • SafeGuard compares published BIQs against material and rules.

Best practice: For every important product category, connect at least one structured product source and one authoritative material source, such as a product guide, policy page, manual, or official FAQ.

See also Connecting Data, BIQs, and SafeGuard.