---
title: >-
  Shopify Flow fulfillment order, refund and return updated
description: >-
  What Flow's Fulfillment order, Refund and Return updated triggers watch, and
  how the order triggers of this app add the status before and after a change.
source_url:
  html: >-
    https://docs.workflow-trigger-extensions.app/fulfillment-refund-return-updated-triggers
  md: >-
    https://docs.workflow-trigger-extensions.app/fulfillment-refund-return-updated-triggers.md
---

# Fulfillment order, Refund and Return updated triggers, and what this app adds

Three of Flow's updated triggers work on records that belong to an order: **Fulfillment order updated**, **Refund updated** and **Return updated**. This app has no trigger for these three records. If a workflow is about the details of a fulfillment order, a refund or a return, Flow's own triggers are the right tool, and this page says so plainly.

What this app adds is the view from the order: the fulfillment status and the payment status **before and after** a change, each shipment's tracking update, and the old shipping address. Many workflows about shipping and refunds are easier to build from there.

## What the three Flow triggers can watch

The fields of Shopify's help pages, as of November 20, 2026. Each trigger takes 1 to 5 of them and, in Shopify's words, provides only the current values.

| Flow trigger | Fields |
| --- | --- |
| Fulfillment order updated | `destination`, `fulfillAt`, `fulfillBy`, `requestStatus`, `status`; the delivery method and its promise and delivery dates; the assigned location and its address; line items with `remainingQuantity` and `totalQuantity`; fulfillments with `status`, `estimatedDeliveryAt` and tracking company, number and URL; `fulfillmentHolds`; `merchantRequests` |
| Refund updated | `refundLineItems` and their subtotal in two currencies; `transactions`, `transactions.fees`, `transactions.status`; `orderAdjustments` |
| Return updated | `closedAt`, `decline`, `requestApprovedAt`, `status`; return line items with quantity, refundable, refunded and unprocessed quantity and restocking fee; `exchangeLineItems`; return shipping fees; reverse fulfillment orders, their line items and status |

Notes from Shopify's pages that are worth knowing before you build:

- **Fulfillment orders.** When a fulfillment order moves to another location, a workflow that watches any field of the assigned location runs, even if that field's value is the same. Placing or releasing a hold starts a workflow on `fulfillmentHolds` once for each hold. Flow also has triggers for single events, such as Fulfillment order placed on hold, moved and split.
- **Refunds.** A refund cannot be edited in the Shopify admin. Shopify records subtotals, order adjustments and some fees while it creates the refund, so creating a refund can start the workflow. A workflow on a subtotal field also runs when returned items are restocked after the refund. For "an order was refunded", Shopify points to the Refund created trigger.
- **Returns.** Adding or removing a line item, a restocking fee, an exchange item or a return shipping fee starts a workflow that watches that group. Flow also has a trigger for each stage of a return, such as requested, approved, declined and closed.
- **Empty variables.** On all three, the variables for line items, holds, transactions and similar items can be empty when the workflow runs. Shopify recommends a condition that checks them before an action uses them.

## What this app adds from the order

| You want to know | Trigger of this app | What the workflow gets |
| --- | --- | --- |
| The order went from unfulfilled to partly or fully fulfilled | Order Fulfillment Changed | `oldFulfillmentStatus`, `newFulfillmentStatus` |
| Which line items were just fulfilled, or unfulfilled again | Order Fulfillment Changed | one entry per line item in `changes.items`, with the product and variant title |
| A tracking number was added or changed | Order Fulfillment Changed | an entry with the tracking number, URL and carrier of that shipment |
| The order went on hold, or a shipment was delivered | Order Display Status Changed | `oldDisplayFulfillmentStatus`, `newDisplayFulfillmentStatus`, and the delivery status of each shipment before and after |
| The order was partly refunded, or fully after a partial refund | Order Financial Status Changed | `oldFinancialStatus`, `newFinancialStatus` |
| The delivery address changed after checkout | Order Shipping Address Changed | the address before and after, as text and in parts |
| Items were removed from the order | Order Line Items Changed | each removed line, and for changed lines the quantity before and after |

## Using them together

**Refund follow-up by size of the step.** Refund created or Refund updated tells a workflow that a refund exists and what is in it. Order Financial Status Changed tells it what that meant for the order: `oldFinancialStatus` **Equal to** `paid` and `newFinancialStatus` **Equal to** `partially_refunded` is the first partial refund, `partially_refunded` to `refunded` is the order being refunded completely. A workflow can treat the two differently.

**Shipping updates to the customer or a channel.** Fulfillment order updated can watch the tracking number of a fulfillment. Order Fulfillment Changed fires on the order with an entry that is marked as a tracking update, so a workflow that should act only on tracking changes needs no further condition on what else changed.

**Address changes while an order is being packed.** Fulfillment order updated can watch `destination`, with the new address only. Order Shipping Address Changed carries the address before and after, so the warehouse sees where the parcel was going.

**Holds.** For the moment a fulfillment order goes on hold, Flow's Fulfillment order placed on hold trigger is the direct way. Order Display Status Changed adds the order's status before and after, for workflows that should act when the whole order leaves the on hold state.

> [!NOTE]
> **What we saw in our tests**
> On November 20, 2026 a workflow on Fulfillment order updated ran next to our test suite on a development store. A run reads the fulfillment order when it starts: in one of fourteen runs the record no longer existed at that moment, and the trigger step failed. Keep that in mind for workflows on records that can disappear soon after a change.

### Does this app have a trigger for refunds or returns?

No. For refunds and returns use Flow's own triggers: Refund created, Refund updated, Return updated and the triggers for each stage of a return. This app adds Order Financial Status Changed, which carries the payment status of the order before and after a refund.

### Can I get the previous fulfillment status of an order?

Yes. Order Fulfillment Changed carries `oldFulfillmentStatus` and `newFulfillmentStatus`. Flow's updated triggers provide the current values only.

### How do I run a workflow when a tracking number is added?

Either with Flow's Fulfillment order updated trigger watching the tracking number of a fulfillment, or with Order Fulfillment Changed, which fires on the order and marks the entry as a tracking update with number, URL and carrier.

### Does Refund updated run when a refund is created?

It can. Shopify's help page explains that a refund cannot be edited in the admin and that Shopify records some values while it creates the refund. For a workflow about new refunds, Shopify points to the Refund created trigger.

## Next steps

- [Flow's Order updated trigger and the order triggers of this app](https://docs.workflow-trigger-extensions.app/order-updated-trigger-comparison.md) - Flow's Order updated trigger and the ten order triggers of this app.
- [Order triggers, step by step](https://docs.workflow-trigger-extensions.app/order-trigger-tutorials.md) - every order trigger with an example.
- [Flow's updated triggers and Workflow Trigger Extensions](https://docs.workflow-trigger-extensions.app/flow-updated-triggers-compared.md) - the overview of all nine updated triggers.
