---
title: >-
  Shopify Flow Order updated trigger: fields and old values
description: >-
  What Shopify Flow's Order updated trigger can watch and what it sends, next
  to ten order triggers that carry the value before and after each change.
source_url:
  html: >-
    https://docs.workflow-trigger-extensions.app/order-updated-trigger-comparison
  md: >-
    https://docs.workflow-trigger-extensions.app/order-updated-trigger-comparison.md
---

# Flow's Order updated trigger and the order triggers of this app

Flow's **Order updated** trigger starts a workflow when one of up to five order fields changes. Shopify's help page describes what the workflow gets in two sentences: "The Order updated trigger provides only the current values of the order and its line items." and "The previous values of the fields that changed aren't available in the workflow."

This app has ten triggers for changes to an existing order. Each one fires for one kind of change and carries the value before and after. This page puts both next to each other, field by field, so you can choose per workflow.

## What Order updated can watch

The fields of Shopify's help page, as of November 20, 2026:

| Group | Fields |
| --- | --- |
| Order | `cancellation`, `customAttributes`, `displayFinancialStatus`, `displayFulfillmentStatus`, `email`, `metafield.value`, `note`, `phone`, `tags` |
| Totals | `subtotalPriceSet`, `totalCapturableSet`, `totalDiscountsSet`, `totalPriceSet`, `totalReceivedSet`, `totalRefundedSet`, `totalRefundedShippingSet`, `totalShippingPriceSet`, `totalTaxSet`, `totalTipReceivedSet` |
| Line items | `lineItems.currentQuantity`, `lineItems.customAttributes`, `lineItems.discountedTotalSet`, `lineItems.discountedUnitPriceAfterAllDiscountsSet`, `lineItems.discountedUnitPriceSet`, `lineItems.duties`, `lineItems.merchantEditable`, `lineItems.originalTotalSet`, `lineItems.priceAfterAllDiscountsBeforeTaxesSet`, `lineItems.quantity`, `lineItems.taxLines` |
| Shipping lines | `shippingLines` |

What Shopify's page adds:

- You select at least one field and at most five. A metafield definition or a whole namespace counts as one of the five.
- A field ending in `Set` holds an amount in two currencies. A change to either amount starts the workflow. To watch one of them, select its `shopMoney` or `presentmentMoney` field.
- Adding a line item counts as a change to that line item, and adding or removing a shipping line starts a workflow that watches `shippingLines`.
- When you watch order fields and line item fields together, the Line Item variable can be empty when the workflow runs.
- For a new order, Shopify points to the Order created trigger.

Not on the list: the shipping and billing address, the customer, fulfillments and tracking numbers, and transactions.

## Field by field

| What changed | Flow's Order updated | Trigger of this app | What the workflow gets on top |
| --- | --- | --- | --- |
| Tags | `tags`: the tag list after the change | Order Tags Added, Order Tags Removed | `addedTags`, `removedTags`, `previousTags`, `currentTags` |
| Note | `note`: the new note | Order Note Changed | `oldNote`, `newNote` |
| Payment status | `displayFinancialStatus`: the new status | Order Financial Status Changed | `oldFinancialStatus`, `newFinancialStatus` |
| Fulfillment status | `displayFulfillmentStatus`: the new status | Order Fulfillment Changed, Order Display Status Changed | the status before and after, each line item that was fulfilled or unfulfilled, each tracking update with number, URL and carrier, and the delivery status of each shipment before and after |
| Custom attributes | `customAttributes`: the attributes after the change | Order Attributes Changed | per attribute in `changes.items`: `changeType` (added, removed, changed), `key`, `oldValue`, `newValue` |
| Line items | `lineItems.quantity`, `lineItems.currentQuantity` and nine more, current values | Order Line Items Changed | per line in `changes.items`: `changeType` (added, removed, quantity_changed, price_changed, variant_changed) with the old and new quantity, price and variant |
| Shipping address | not on the list | Order Shipping Address Changed | `shippingAddress` and `oldShippingAddress`, and every part of both as its own field |
| Order metafield | `metafield.value`: the new value | Order Metafield Update | `metafield.value`, `metafield.previousValue` |
| Totals | ten total fields, each in two currencies | Order Update, or the custom trigger template **Order total changed (before and after)** | the total before and after |
| Email, phone, cancellation, shipping lines | `email`, `phone`, `cancellation`, `shippingLines` | Order Update fires on these updates. No trigger of this app carries their old value | |
| Any number of these in one workflow | five at most | Order Update, narrowed to the fields you tick | `changes.fields` and `changes.items` with `field`, `oldValue`, `newValue` |

[Order triggers, step by step](https://docs.workflow-trigger-extensions.app/order-trigger-tutorials.md) has a worked example for each of the ten order triggers.

## What we saw when both ran on the same order

On November 20, 2026 we created one order on a development store and changed it at known times, with a workflow on Order updated and the triggers of this app active side by side. The full table is in [Flow's updated triggers and Workflow Trigger Extensions](https://docs.workflow-trigger-extensions.app/flow-updated-triggers-compared.md). Three results matter for order workflows:

- **Creation counted as a change.** The order was created from a draft order. Before anyone edited it, Order updated had started twice, once for the financial status and once for the fulfillment status. The triggers of this app remember a new order and fire from its first real change on.
- **Every write is a run.** Three tags added within one second started three runs. Two of them already showed all three tags, so the same state was handled more than once. This app sent one event that listed the three tags.
- **A run shows the order as it is when it runs.** Two note changes within one second started two runs, and both showed the final note. Order Note Changed sent one event with the note before the first change and the note after the last one.

![The Flow trigger events block on an order page: financial status pending to paid, and a note added](https://cdn-dev.eu.codecreationlabs.cloud/crm-tool/uploads/SjJ78gKLnLlocopCui3Cs62dJbGZ7F1n/31c03082c5bb39cd.png)
*An order's page in the Shopify admin with the events block of this app: the status before and after, and the note that was added.*

## Workflows that need the value before

**Release an order when a pending payment arrives.** Order Financial Status Changed with the condition `oldFinancialStatus` **Equal to** `pending` and `newFinancialStatus` **Equal to** `paid`. A workflow that only sees "paid" cannot tell this order from one that was paid at checkout. Ready to use: [Tag orders when a pending payment is received](https://docs.workflow-trigger-extensions.app/template-tag-payment-received.md).

**Tell the warehouse when the address changes after checkout.** Order Shipping Address Changed carries the address before and after, so the message can say where the parcel was going and where it goes now. Ready to use: [Tag orders when the shipping address changes after checkout](https://docs.workflow-trigger-extensions.app/template-tag-address-changed.md).

**Review edited orders.** Order Line Items Changed lists each line that was added, removed or changed, with the quantity before and after. A condition on `changeType` separates a removed item from a changed quantity. Ready to use: [Tag orders when their line items are edited](https://docs.workflow-trigger-extensions.app/template-tag-edited-orders.md).

**Act on one tag.** Order Tags Added and Order Tags Removed name the tags that changed. See [Run a workflow when one specific tag is added or removed](https://docs.workflow-trigger-extensions.app/specific-tag-added-or-removed.md).

**React to a changed gift message or delivery date.** Order Attributes Changed carries the key of each attribute that changed, with its old and new value, so a workflow can act on one attribute and ignore the others.

![The workflow in Shopify Flow: Tag orders when a pending payment is received](https://cdn-dev.eu.codecreationlabs.cloud/crm-tool/uploads/SjJ78gKLnLlocopCui3Cs62dJbGZ7F1n/ed367d6254083bf6.png)
*The template for a pending payment that arrives: the trigger, a condition on the old and the new status, one action.*

## When Order updated is the right choice

- You want a quick alert when one of a few fields changes and the current values are enough.
- You watch a total in one currency, tips, duties, tax lines or shipping lines.
- You watch the order's email, phone or cancellation details.
- The workflow has to start within a second or two of the change.

Both can run in the same store. A change that both watch starts both workflows, so give each job to one of them.

### Does Order updated give the previous value?

No. Shopify's help page says the trigger provides only the current values of the order and its line items. The order triggers of this app carry the value before and after.

### Does Order updated run when an order is created?

Shopify points to the Order created trigger for new orders. In our test an order created from a draft order still started Order updated twice, for the financial status and the fulfillment status. Add a condition if a workflow on status fields should not act on new orders.

### Can I get the old shipping address of an order in Flow?

Yes, with Order Shipping Address Changed. It carries the address before and after the change, as formatted text and in parts. The shipping address is not among the fields Order updated can watch.

### Can Order updated tell me which tag was added?

No. It shows the tag list after the change. Order Tags Added names the added tags and Order Tags Removed the removed ones.

### Which orders does this app watch?

By default the orders of the last 60 days. You can extend the range in the app, to 180 days, 12 months, 24 months or a date of your choice.

### Can I use both on the same store?

Yes. They do not interfere. Decide per workflow which trigger starts it.

## Next steps

- [Order triggers, step by step](https://docs.workflow-trigger-extensions.app/order-trigger-tutorials.md) - every order trigger with an example.
- [Old and new values: what a workflow can do with them](https://docs.workflow-trigger-extensions.app/old-and-new-values.md) - all values before and after, by trigger.
- [Fulfillment order, Refund and Return updated triggers, and what this app adds](https://docs.workflow-trigger-extensions.app/fulfillment-refund-return-updated-triggers.md) - fulfillment orders, refunds and returns.
