Shopify · 3 min read

Shopify's new activity log can help investigate unexpected store changes

Shopify updated its Store activity log on November 13, 2026. Learn what it records and how to use a change timeline when investigating a broken storefront.

When a Shopify page changes unexpectedly, start by recording the symptom and checking recent changes. The rebuilt Store activity log can help narrow the investigation, but a nearby log entry does not prove what caused the problem. Use the timeline alongside a reproducible test.

What changed in Shopify?

Shopify announced the updated log on November 13, 2026. It is available under Settings → General → Store activity log, with filters for actors, actions, resources, fields and dates. Entries can identify a staff member, collaborator or app, with before-and-after values where available. Shopify describes retention of up to 18 months, but recording started shortly before the release for each supported change type; it does not reconstruct all earlier history.

Access requires the appropriate permissions, and not every admin action is recorded. An app's name may appear without identifying the person who triggered it. These limits matter when interpreting an empty search. Read Shopify's release details.

Start with a problem you can reproduce

Our suggested investigation begins with a short record: the affected URL, the device, what you selected, what happened and what should have happened. Include the time and timezone. A report such as “the blue medium option enters the cart as red medium” gives a developer something specific to test.

Separate when someone first noticed the issue from when it actually began. A customer may discover an old problem during a new campaign. That distinction keeps the investigation from focusing only on yesterday's work.

Build a small investigation table

Use the log to generate candidates, then test them. This is a proposed workflow, not a case study or a claim about a particular store.

ObservationQuestion to investigateUseful next evidence
A product option behaves differentlyDid product data or its presentation change?Compare the selected option with the cart line item.
A section disappears on one templateIs the issue limited to that template?Compare another product using the same template.
A change appears under an app's nameWhat operation was the app performing?Review the relevant app settings and available history.
No relevant event appearsIs the action covered by this log?Use theme history and a developer's reproduction notes.

Avoid a rushed rollback

Preserve the current version before trying a fix. Where possible, reproduce a theme issue on a duplicate or preview theme and change one suspected cause at a time. Do not disable every app on a live store just to see whether the symptom disappears: that makes it difficult to tell which change mattered.

After a candidate repair, repeat the original steps and a neighbouring case. For the option example, check another available size as well as the previously failing one. Record the outcome and any remaining uncertainty.

Does the log replace testing?

No. A timeline tells you which recorded changes are worth investigating. The customer journey tells you whether the problem still happens. An app update, a data change and a theme change can occur close together without all being responsible.

What should I send a developer?

Send the reproduction steps, relevant timestamps and selected log entries with customer details removed. Use our website-fix brief to organise the handover. If you want help investigating an existing store, tell FixTheLeak which page is affected.

Source checked November 19, 2026. The investigation checklist is FixTheLeak's editorial guidance; it is not a guarantee that the log will identify every issue.

FTL.Shopify & Front-endIndia

Available for new work