Admin / Improvement

Store activity log overhaul
See who changed what, and when, in one place

Changes to products, orders, discounts, themes, apps, staff, payments, and store settings now appear in one log. You can see who made each change, filter entries, and compare values before and after the change. Logs are now kept for up to 18 months.

What's on this page
  1. What's changing (in 30 seconds)
  2. How it works: from a change to a traceable log entry
  3. What gets logged, and who made the change
  4. Old log vs. new log
  5. Who can use it, and what to watch for
  6. How to use it (3 steps)
  7. 5 key points for developers
  8. 3 business use cases
  9. One-line summary for proposals

1What's changing

Until now, finding out who changed what meant checking several different parts of the admin.
The redesigned Store activity log brings changes into a single log, so you can trace who made each change, what was affected, and the values before and after.
?

Before: search page by page

Records of changes were spread across different pages. The old log kept only the 250 most recent events.

New log: track everything in one place

Everything is in Settings > General > Store activity log. You can filter by who made the change, and opening a row shows the values before and after. Logs are kept for up to 18 months.

2How it works: from a change to a traceable log entry

Made by Staff Collaborators Apps Shopify (staff) Store changes Products, orders, discounts Themes, apps, staff Payments, store settings Something changes Store activity log Who (made the change) What (resource / field) How (action type) When (date & time) Retained for up to 18 months All in one place Investigate Narrow down with filters Open a row for details Before → After Jump in from any page "View activity"
Admin pages for products, orders, discounts, gift cards, collections, domains, and more now have a "View activity" action, which opens the logalready filtered to that item.

3What gets recorded and who made the change

Changes you can see in one log

Products & orders
Products / Orders
%
Discounts & themes
Discounts / Themes
Apps & staff
Apps / Staff
Payments & store settings
Payments / Settings

Who the change is attributed to

People

Staff / collaborators

Shown under the staff member or collaborator who made the change.

Apps

Apps

Changes made by apps are attributed to the app.For some app changes, the person who made them isn't recorded, so the app name is shown.

Shopify

Shopify

Changes made by Shopify staff are shown as "Shopify."

Filter options (5)

Who made the change Action type Resource Changed field Date range

4Old log vs. new log

ItemOld logNew Store activity log
Retention period Entry limit Up to the 250 most recent events Time range Up to 18 months
Coverage Not stated Consolidated Products, orders, discounts, themes, apps, staff, payments, and store settings
Filtering Not stated 5 dimensions Actor / action type / resource / field / date range
Change details Not stated Before/after comparison Shows before and after values when available
Access from individual pages Not stated View activity Opens the log pre-filtered to that item
Who can use it Staff with access to the old log (can keep using it for now) Restricted Store owner + staff with both Manage settings and Edit permissions

5Who can use it & caveats

Who can use the new log

Store owner, and staff with both "Manage settings" and "Edit permissions"staff permissions (e.g., the Administrator or Organization administrator role).

Other staff

Other staff with access to the old logwill keep using the old log for now. No migration timeline has been given.

No retroactive history : History starts from when recording began for each type of change (shortly before this release). Earlier changes aren't shown.
Not every action is logged : Not all actions in the Shopify admin are tracked yet.

6How to use it (3 steps)

1

Settings > General > Store activity log

or open it directly from "View activity" on pages such as products and orders.

2

Narrow it down with filters

Filter by actor, action type, resource, field, and date range.

3

Open a row to see details

See what changed and, where available, the before and after values.

Investigations like "Who changed this product's price, and when?"Product page View activity → filter by field → open the rowis all it takes.

75 key points for technical teams

APP

1. Changes made through apps may not be traceable to a person

For some app-made changes, the actor isn't recorded and only the app name is shown.In stores with many integrated or custom apps, "which app made the change" may beas far as you can trace.

API ?

2. No mention of APIs or exports

The article only describes the feature in the admin. It says nothing about access via the Admin API, CSV export, or webhook integration. Don't design anything that assumes ingestion into an external SIEM or similar tool.

18M

3. Retention shifts from "event count" to "time period"

The old log was capped at the most recent 250 events, so high-activity stores lost entries quickly. The new log keeps up to 18 months. However,recording only starts shortly before the release, so older history can't be retrieved retroactively.

4. Viewing access is tightly restricted

Only the owner, or staff with both Manage settings and Edit permissions.If you want frontline staff to see it, you'll need to revisit your permission setup, but keep in mind that granting these permissions has a broad impact.

5. "Not in the log" doesn't necessarily mean "not changed"

Shopify explicitly states that not all admin actions are recorded yet. Before and after values are also shown only "where available."For audits and incident investigations, treat the log as the primary source, but assume gaps may exist and cross-check it against other sources (such as app-side logs)as standard practice.

83 practical use cases

USE CASE 1

Pinpoint the cause of "prices or settings changed unexpectedly" incidents faster

Challenge
When product prices, discounts, or payment settings changed unexpectedly, teams had to dig through the admin to find out whether staff or an app made the change, and when.
Approach
Open the filtered log via "View activity" on the relevant page, narrow it further by field and date range → open the row to check the before and after values.
Impact
Identifying the cause (actor, time, and change) takes a single screen, enabling faster rollback decisions.
Technical note
Some app-made changes show only the app name. In that case, trace what happened through the app's own logs or settings.
WHO?
USE CASE 2

Clarify "who touched what" when co-managing a store with agencies and external partners

Challenge
With in-house staff, collaborators (such as agencies), and multiple apps all working in the same store, responsibility for theme and app setting changes tends to be unclear.
Approach
Regularly filter by actor to check changes by each collaborator and app, and set up a routine review of theme-, app-, and staff-related changes.
Impact
Responsibility for each change becomes visible, cutting the cost of "who said what" disputes and reducing missed unintended changes.
Technical notes
Only the store owner and staff with Manage settings + Edit permissions can view the new log. Confirm reviewers' permissions in advance.
USE CASE 3

Checking settings changes before and after releases and sales

Challenge
Before and after a theme publish or sale prep, it takes effort to identify which settings, discounts, and products were changed. The old log was capped at 250 entries, so busy periods quickly pushed entries out.
Approach
Set the date range to the release or sale period, list changes by resource (themes, discounts, products, etc.), and check them against your checklist.
Impact
Missed or unintended changes are easier to catch. With 18 months of retention, you can also review what was done in the same period last year (only for activity since logging began).
Technical notes
Not every action is logged, so design your checklist assuming some changes won't appear in the log.

9One-line summary for proposals

"A new audit log that consolidates store changes by who, what, and when in one place.
Five filters, before-and-after values, direct access from each page, and up to 18 months of retention.
Immediately useful for incident investigation and clarifying responsibilities in shared operations, though changes made before logging began and some actions are not covered."