On November 20, 2026, Shopify announced eight new Flow triggers for updates to customers, orders, refunds, fulfillment orders, returns, collections, locations and inventory items. A workflow can monitor up to five fields and starts when a selected field changes. The update expands event-based automation; it is not an AI generator and does not require a model to decide the business action.

Automation starts with the monitored field

In Shopify Flow, the trigger identifies the event that starts a workflow, a condition checks the data, and an action performs the configured operation. The new trigger group monitors changes to existing resources. Separate triggers exist for creating a customer or an order. Shopify presents the new mechanism as an alternative to scheduled checks and intermediate arrangements previously used to discover whether data changed between two inspections.

Selecting fields defines which changes matter to a workflow. At least one and no more than five fields are required, and a change to any monitored field can start execution. Conditions within the workflow then determine whether an action fits the current value. An update event and a business rule are therefore separate layers: the first signals a change, while the second determines the route configured by the administrator.

How an event connects to a business operation

  1. Monitored field

    For example: the order's financial status. Up to five selected fields.

  2. Update detected

    Flow starts with the resource's current values.

  3. Condition checked

    The desired state and required objects are checked.

  4. Configured action

    Notification, tagging or an integration supported by the plan; then execution review.

An employee checking a tablet between warehouse shelves
Tiger Lily

Orders can be monitored by status, totals or line items

For Order updated, the documentation includes tags, notes, financial and fulfillment statuses, totals and line-item properties. When a line's quantity is monitored, adding a line to the order also starts the workflow. Monetary fields ending in Set can contain both the shop currency and the currency presented to the customer. Choosing a subfield allows one of those values to be monitored specifically.

The trigger supplies current values rather than values from before the change. A workflow monitoring tags can inspect the tags present at execution, but does not automatically receive the previous list for comparison. When both order properties and line properties are monitored, the line object can be empty for a change affecting only the order. The documentation calls for checking that data exists before using it in an action.

Customer profiles and consent have their own rules

Customer updated can monitor profile data, addresses, tags and marketing subscription properties. For some changes to the default email address or phone number, Shopify can register an update to the whole object. A workflow monitoring a nested property can start in that situation too. For an action tied specifically to subscription status, the condition must explicitly check the value of that property.

This distinction matters when a store sends data to a custom CRM for the business. Having a profile, being a buyer and subscribing to marketing are different facts. An integration needs to preserve them separately, along with customer identity and field meaning. The new trigger observes an update; it does not itself grant permission to send a message or redefine the segments used in campaigns.

The eight resources receiving update triggers

TriggerMonitored resource
Customer updatedCustomer profile
Order updatedOrder
Refund updatedRefund
Fulfillment order updatedFulfillment order
Return updatedReturn
Collection updatedProduct collection
Location updatedStore location
Inventory item updatedInventory item properties; not quantity

An inventory item is distinct from stock quantity

Inventory item updated monitors properties such as SKU, unit cost, weight and customs information. Shopify explicitly states that this trigger does not monitor inventory quantities. Changes to a variant's quantity have a separate Product variant inventory quantity changed trigger. The names are similar, but the events and monitored data differ. An automation built around cost should not be presented as an out-of-stock alerting mechanism.

The company's announced example is updating a product metafield when the item's cost changes. Implementation depends on the data exposed by the trigger and the chosen action. As with orders, current values are available. If a business needs the difference between the old and new cost, the integration architecture also needs a separate record of the previous value for that comparison.

Collections and fulfillment extend operational coverage

Collection updated can monitor the title, description, sort order or product membership. Monitoring the products field starts the workflow when a product is added or removed. The product object can be absent if the product was deleted or the change concerns another field. A collection used in promotion can therefore also be monitored as an operational resource, with rules tied to actual changes.

Fulfillment order updated covers statuses, destination, assigned location, delivery method and information about fulfillment processing. Some parent-object changes can start the workflow even where a nested field retains the same value. For example, moving to another location can activate monitoring of the location's city even when both locations are in the same city. The workflow condition needs to reflect the exact situation for which the team wants a notification.

Refunds are monitored separately from returns

The eight triggers include Refund updated and Return updated separately. A refund concerns the financial operation, while a return is a distinct resource in the commercial process. Documented refund fields include transaction statuses and order adjustments, among others. Some fields can cause execution when the refund is created because their values are recorded at that point. Trigger selection needs to match the moment the business wants to monitor.

Location updated completes the set for store location data. Together, these events allow more precise descriptions of the relationship between orders, customers and operations. An internal notification, a tag update and sending information to another system are different actions. A workflow diagram needs to show which object changed and which data is available so that the team's message describes the actual situation.

The store plan determines available actions

Shopify Flow is a free app available on Basic, Grow, Advanced and Plus plans. Staff need permissions to access it and activate workflows. The Send HTTP Request action is available on Grow, Advanced and Plus. Tasks created by partners' custom apps are reserved for Plus. Usage limits also depend on the plan's API limits, according to Shopify's documentation.

The update therefore concerns small stores as well as larger configurations, but an external integration needs to be designed for the actual plan. In business automation and application integrations, the event, condition, action and execution history have distinct roles. The November 20 update adds more precise starting points. Time savings or sales effects are measured in the implemented process through eliminated manual operations, correct executions and exceptions reaching the team.