Verify product variants, prices, stock, and markets
Confirm that customer-critical product facts match the intended variant and Shopify Market Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Confirm that customer-critical product facts match the intended variant and Shopify Market This guide keeps the work focused on catalog product details 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 and permission to inspect the Shopify source are required.
- Choose a product with multiple variants or market-specific data.
- Record the expected currency, price, availability, and selected market.
- Wait until the latest catalog sync is complete.
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
Confirm the scope and current state
Compare the Humind product record with the Shopify product and each representative variant, paying attention to identifiers rather than title alone.
- 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.
Prepare the change
Check price, compare-at price when relevant, stock or availability, attributes, currency, and active market context.
- 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.
Save and allow required processing to finish
Correct source data in Shopify when it owns the value, then synchronize and wait for indexing instead of editing a duplicate narrative fact.
- 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.
Test the complete customer journey
Ask the Agent factual and recommendation questions that distinguish variants, out-of-stock cases, and the intended market.
- 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 details separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- Variant identifiers and attributes map to the correct product.
- Price and currency match the intended market.
- Availability is represented without unsupported guarantees.
- The Agent does not combine details from different variants or markets.
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
The displayed price belongs to another market
Confirm the active market and shared-domain routing, then check that market data synchronized for the same product record. Retest on the real domain when market selection depends on hostname.
Stock differs from Shopify
Check the timing and final state of inventory synchronization. Avoid documenting a fixed quantity in Knowledge and report repeated lag with the product and sync context.