Display Who & When a Tag is Added/Removed on order timelines

We use tags for many different reasons. One of the primary uses is to help manage order processing. For example, when an order is printed, the employee who prints it adds the tag “PRINTED” to indicate that it has been acknowledged.

The convenience of using tags is that we do not need to open each individual order. Instead, we can bulk-select orders and apply tags to anywhere from 1 to 50 orders at the same time, which saves a significant amount of time.

We also use tags for a variety of other operational purposes. Some tags trigger code that generates lead times displayed on our website. Because of this, it would be very helpful to know when tags were added, modified, or removed, as well as which user made those changes.

Having this visibility would make it much easier to troubleshoot internal issues, understand unexpected changes, and train employees more effectively.

This is a common challenge for merchants who use tags as part of their operational workflow.

Unfortunately, Shopify does not currently provide a native audit trail showing who added or removed a specific tag and when the change occurred. Order timelines may show that an order was updated, but they don’t expose detailed tag-change history.

Here are a few approaches you can consider:

1. Use Shopify Flow + Logging
If you’re on a plan that includes Shopify Flow, you can create workflows that trigger when an order is updated and log tag changes to:

  • An internal note

  • A metafield

  • Google Sheets

  • Slack

  • An external database via webhook

This creates a historical record of tag changes going forward.

2. Use an Activity/Audit Log App
Several apps provide enhanced staff activity tracking and audit logs. Depending on your requirements, these apps can help identify which staff member performed specific actions and when they occurred.

3. Replace Critical Tags with Structured Workflows
For important process stages such as “Printed”, “Packed”, or “Ready to Ship”, consider using:

  • Shopify Flow

  • Order metafields

  • Fulfillment statuses

  • Custom app workflows

These can provide better traceability than tags alone.

4. Build a Custom Tracking Solution
If tags drive operational logic and lead-time calculations, a custom app can listen for order updates via webhooks and store:

  • Previous tag values

  • New tag values

  • Timestamp

  • Staff member (where available through the API/app action)

This creates a complete audit history for reporting and troubleshooting.

For stores where tags are business-critical, I generally recommend implementing an audit log through Shopify Flow or a custom app, as Shopify’s native tag history is currently quite limited.