A product page can look like one screen while depending on catalog data, a theme template, installed apps, structured data, inventory rules, and the visitor's browser. A change log keeps those layers from becoming one vague problem. Start with the product URL, product or SKU identifier, affected variant, market, currency, device, browser, time zone, and a screenshot. Write the expected and actual behavior in separate sentences. Note whether the problem affects content, price, availability, images, variants, the add-to-cart control, or only search presentation.
Confirm the scope before editing
Retest in a private browser window, on another device, and on another network. Shopify's theme-troubleshooting guidance recommends clearing browser causes and testing another or uncustomized theme to determine whether the issue is local to the active theme: https://help.shopify.com/en/manual/online-store/themes/theme-support/troubleshooting. If every theme shows the same symptom, investigate product data, administration settings, or apps before editing theme code. For a missing product, confirm that it is active and available to the Online Store. When only some products fail, compare their assigned theme templates.
Correlate the failure with recorded changes
Open the store activity log and compare its timestamps with the first confirmed failure. Shopify says this log records recent actions with the date, time, and actor, which can be a person, an app, or a channel: https://help.shopify.com/en/manual/shopify-admin/activity-logs. It is view-only, limited to 250 results, and cannot be exported, so preserve relevant observations in the incident log without copying private customer information. Record installed or recently updated apps, template edits, product-status changes, and changes to availability. A timestamp establishes sequence, not guilt; test the suspected layer before naming a cause.
Make controlled tests
Use a duplicate or unpublished theme when practical. Give each entry a hypothesis, one action, the before-and-after result, and a rollback reference. Shopify's code-editor Timeline can restore an earlier file version, but restoring replaces the whole file; its guidance says to copy the current contents first. Avoid combining a template edit, app removal, and catalog correction in one step because the result would not identify which action mattered.
If the visible product is correct but its search enhancements are wrong, inspect the page's structured data. Google identifies the Rich Results Test for checking eligible Google rich results and the Schema Markup Validator for generic schema.org markup: https://developers.google.com/search/docs/appearance/structured-data. Save the test URL and result in the log, then correct the source field rather than merely hiding the symptom.
Finish by repeating the affected visitor path through variant selection and cart creation without placing an unnecessary real order. Verify the page in the active theme, confirm the retained catalog data, and document any remaining limitation. The closing entry should identify the approved change, the person who verified it, and the rollback point.
Sources
- Troubleshooting your online store theme — Shopify
- Activity logs in the Shopify admin — Shopify Help Center
- Understand how structured data works — Google Search Central