Executive summary
- What: Shopify rebuilt the Store activity log under Settings, General, so changes to products, orders, discounts, themes, apps, staff and payments sit in one filterable record.
- Why: retention moves from 250 recent events to 18 months, and every row names the staff member, collaborator or app responsible.
- Who: store owners and staff holding both the Manage settings and Edit permissions, meaning Administrator and Organization administrator roles. Everyone else stays on the previous log.
What changed
The old log answered a narrow question: what happened recently. It held 250 events and scattered the rest across individual timelines, so investigating a change meant opening the product page, then the order page, then the theme library, and assembling a sequence by hand. The rebuilt log replaces that with one queryable surface.
Three things are different. Attribution is explicit on every row, naming the staff member, collaborator or app responsible, or Shopify itself when Shopify staff acted. Some app-driven changes record no individual actor and show the app name instead. Filtering is structured, so you can narrow by actor, action type, resource, the specific field that changed, and a date range. And retention stretches to 18 months, enough to cover a full annual cycle plus a comparison period.
Detail pages for products, orders, discounts, gift cards, collections and domains now carry a View activity action that opens the log already filtered to that record. Two caveats matter: history begins only from the point each change type started being recorded, shortly before this release, so the log will look thin for a while, and not every admin action is captured yet.
Why it matters
For a Plus merchant with several stores, a large staff roster and a dozen installed apps, the cost of a weak audit trail is measured in hours. A price shows up wrong on Monday morning and someone spends an afternoon working out whether it came from a staff edit, a bulk import, an ERP sync or a discount app. Attribution plus field-level filtering collapses that into a query.
The second benefit is governance. Change attribution across an 18 month window is the evidence internal audit, SOC 2 readiness work and enterprise vendor reviews routinely ask for, and until now Plus merchants answered with app logs and screenshots. It is a practical step toward a defensible operational record, covered in our note on security and compliance on Shopify Plus.
Role-specific impact
- Marketers: before blaming a campaign for a margin miss, filter the log by discount and collection changes across the relevant window. Attribution usually settles the question in minutes.
- Developers: theme publishes, app installs and setting changes now carry timestamps you can line up against deploys. Make the log your first stop in incident triage, and keep app-side logging for paths Shopify does not yet record.
- Store admins: access is the first task. Confirm who holds both Manage settings and Edit permissions, since only those users see the new log, and expect a split experience until access widens.
Use-case example
Real-world scenario
A 40 person apparel brand on Plus runs a peak season promotion across three storefronts. On the second morning, margin on one collection sits six points below plan. Previously the merchandising lead would have opened affected products one by one and inferred a cause. With the rebuilt log they filter to the product resource, the compare at price field, and the last 36 hours, and find a pricing app rewrote compare at prices on 212 variants overnight. Investigation drops from roughly two hours to under ten minutes, and the rollback lands before the day's traffic peak.
Implementation checklist
- Confirm which staff hold both the Manage settings and Edit permissions, since only those roles see the new log today.
- Open Settings, General, Store activity log on each store and verify history has started recording.
- Document the changes your team most often needs to trace, then check each appears in the log with usable field detail.
- Note the gaps, meaning actions not yet recorded and app changes without an actor, and keep app-side logs for those paths.
- Add the View activity shortcut to your incident runbook so responders start from the filtered view.
- Re-check coverage quarterly, and retire third-party audit tooling only once native coverage is proven.
FAQ
Q: Does this replace our third-party audit or change-tracking app?
A: Not yet. Coverage is incomplete and history starts from this release, so run both until every action your compliance process depends on is verifiably recorded natively.
Q: How far back can we look?
A: Up to 18 months going forward, but only from the point each change type began being recorded. Anything before this release will not appear, so treat the first year as partial.
Resources
Shopify changelog: the new Store activity log
Need guidance? Talk to Makro.