Read synchronization progress and turn a failed or partial catalog sync into a focused next action This guide keeps the work focused on catalog synchronization 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 read access is enough to inspect status. Reconnecting or starting synchronization requires catalog or company write access.

• Know the connected shop and intended Shopify Market.
• Record when source data last changed.
• Choose one product that can be checked end to end.

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 catalog or Shopify integration and distinguish queued, running, completed, partial, and failed work from the separate indexing state.

   • 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

   Inspect the reported stage and error details, then check whether the source product, market, or authorization explains the problem.

   • 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

   Retry or reconnect only after correcting the identified cause. Avoid launching overlapping synchronizations that obscure the result.

   • 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

   Confirm the representative product, variants, price, stock, market, and Agent availability after the final sync and indexing states complete.

   • 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 synchronization separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.

Verify the result

• The synchronization reaches a clear final state.
• Reported totals are plausible for the intended shop and market.
• The representative product matches Shopify source data.
• A product test can use the item after indexing completes.

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

A synchronization remains queued or running

Wait for the active job and refresh its state. If it exceeds the normal operating window, record the shop, stage, start time, and visible error before asking support to investigate.

The sync completes but products are missing

Check market activation, source publication, product visibility, and indexing separately. A completed import does not mean every source item is eligible for Agent use.

Related guides

• how to sync your catalog
• connect shopify and sync your catalog
• control which products the agent can use
• verify product variants prices stock and markets