Make the intended products available to the Agent while excluding unsuitable or incomplete items This guide keeps the work focused on catalog product eligibility and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.

The catalog gives Humind structured product information such as products, variants, prices, availability, collections, and metadata. Shopify synchronization brings source data into Humind, while indexing and AI filters determine what the Agent can use. A successful sync alone does not prove that every product is ready for customer conversations.

Before you begin

Access: Catalog write access is required for Humind product controls. Shopify source changes require access to the connected shop.

• Define the intended catalog scope and markets.
• Choose one product to include and one to exclude.
• Check product status and availability in Shopify first.

Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.

Step-by-step workflow

1. Confirm the scope and current state

   Open the product list and inspect source status, market, collection membership, and any Humind availability or discovery controls.

   • Confirm the active company and Agent before editing.
   • Record the current state so the result can be compared after the change.
   • Stop if the screen or permission does not match the intended task.

2. Prepare the change

   Correct source publication and catalog metadata before relying on filters or behavioral instructions to hide a product.

   • Use the smallest change that completes the customer task.
   • Keep authoritative information in its owning source.
   • Review labels, dates, language, and customer-visible wording before saving.

3. Save and allow required processing to finish

   Save the product or collection controls and allow synchronization and indexing to finish where required.

   • Wait for the interface to confirm that the change is saved.
   • If synchronization, indexing, or publication is required, wait for its final state.
   • Reload the area and confirm the saved values persist.

4. Test the complete customer journey

   Run product tests for included and excluded examples, then ask for a recommendation that could otherwise surface the excluded item.

   • Use a fresh session and a realistic customer scenario.
   • Check desktop and mobile when the result appears on a storefront.
   • Capture the exact failing step if the outcome differs from the expectation.

Important limits and operating notes

• A successful save confirms persistence, not every downstream synchronization or public update.
• Workspace permissions can hide an area or allow reading without allowing changes.
• Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
• Test only supported capabilities that are visible and configured for the current company.
• Keep changes in catalog product eligibility separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.

Verify the result

• Included products are selectable and usable in product tests.
• Excluded products are not recommended in the tested scope.
• Market-specific availability is respected.
• No narrative Knowledge workaround duplicates volatile product eligibility.

Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.

Troubleshooting

An excluded product is still recommended

Check whether a duplicate product, another market record, cached conversation context, or broad collection still includes it. Retest with a fresh conversation after indexing.

An included product cannot be found

Verify source status, active market, catalog import, required fields, and indexing. Fix the earliest failing layer rather than adding Agent guidance.

Related guides

• manage products filters collections and promotions
• understand catalog sync status and errors
• test how the agent handles a product
• verify product variants prices stock and markets