---
title: >-
  Shopify Flow Location updated trigger: fields, old values
description: >-
  What Shopify Flow's Location updated trigger can watch and when it runs,
  next to five location triggers that list each changed field with old and new
  value.
source_url:
  html: >-
    https://docs.workflow-trigger-extensions.app/location-updated-trigger-comparison
  md: >-
    https://docs.workflow-trigger-extensions.app/location-updated-trigger-comparison.md
---

# Flow's Location updated trigger and the location triggers of this app

Flow's **Location updated** trigger starts a workflow when one of up to five fields of a location changes. Shopify's help page: "The Location updated trigger provides only the current values of the location." and "The previous values of the fields that changed aren't available in the workflow."

This app has five location triggers. **Location Updated** lists the fields that changed with their old and new values, without any setup, and four more fire when a location is activated, deactivated, created or deleted.

## What Location updated can watch

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

| Group | Fields |
| --- | --- |
| Location | `deactivatedAt`, `fulfillsOnlineOrders`, `isActive`, `metafield.value`, `shipsInventory` |
| Address | `address` and below it `address1`, `address2`, `city`, `countryCode`, `latitude`, `longitude`, `phone`, `provinceCode`, `zip` |

Shopify's page adds that `address` watches any change to the address with one of your five fields, and that a metafield definition or a whole namespace counts as one field.

The name of a location is not on the list.

## Field by field

| What changed | Flow's Location updated | Trigger of this app | Before and after |
| --- | --- | --- | --- |
| Name | not on the list | Location Updated | `name` in `location.changes`, with `oldValue` and `newValue` |
| Address | `address` or one of its parts, new value only | Location Updated | each changed part (`address1`, `address2`, `city`, `province`, `provinceCode`, `countryCode`, `zip`, `phone`) with `oldValue` and `newValue` |
| Fulfills online orders | `fulfillsOnlineOrders`, new value only | Location Updated | `fulfillsOnlineOrders` with `oldValue` and `newValue` |
| Activated or deactivated | `isActive`, `deactivatedAt`, new value only | Location Activated, Location Deactivated, and `active` in Location Updated | one trigger for each direction, no condition needed |
| Location metafield | `metafield.value`, new value only | Metafield Update for locations | `metafield.value`, `metafield.previousValue` |
| Ships inventory, latitude, longitude | `shipsInventory`, `address.latitude`, `address.longitude` | no trigger | |
| A location is created or deleted | not part of this trigger | Location Created, Location Deleted | the new location, or the id of the deleted one |

![Shopify Flow's trigger picker inside Workflow Trigger Extensions, searched for Location](https://cdn-dev.eu.codecreationlabs.cloud/crm-tool/uploads/SjJ78gKLnLlocopCui3Cs62dJbGZ7F1n/6d4ae5ce66f3c53d.png)
*The five location triggers of this app in Flow's trigger picker.*

## What we saw in our tests

On November 20, 2026 we ran a workflow on Location updated next to the triggers of this app on a development store.

- **Several fields in one save are one run.** Deactivating a location changes `isActive` and `deactivatedAt` together. Flow started one run, and the workflow is not told which of its fields changed. In this app, Location Deactivated fires for the event itself, and Location Updated names `active` as the changed field with its old and new value.
- **Shopify's own follow-up writes count too.** After an address was changed, Shopify worked out the coordinates and wrote latitude and longitude. A workflow watching `address` ran again for that write, although nobody had edited the location a second time. To avoid it, watch the address parts you care about instead of the whole address.

## Workflows that need the value before

**Tell carriers and marketplaces when a warehouse moves.** Location Updated carries each changed part of the address with its old and new value, so the message can say "moved from this street to that street" and does not need a second lookup.

**Update pickup texts when a shop is renamed.** A new name has to reach theme texts, emails and other systems that still use the old one. Location Updated carries the name before and after. Flow's trigger cannot watch the name.

**React when a location stops fulfilling online orders.** A condition on the change of `fulfillsOnlineOrders` from `true` to `false` is true once, at the switch, and stays quiet on every other edit of the location.

**Run a checklist when a location is deactivated.** Location Deactivated fires for exactly that, with the location. No field selection and no condition are needed.

**Notify customer service when pickup hours change.** Hours kept in a location metafield arrive with the value before and after. See [Location metafield trigger](https://docs.workflow-trigger-extensions.app/location-metafield-trigger.md).

> [!NOTE]
> **Good to know**
> - Location Updated is on by default and sends `location.changes` with every event. You can switch it off on the **Triggers** page when you only need the more specific triggers.
> - `location.changes.fields` names the fields that changed, and `location.changes.items` holds one entry per field with `field`, `oldValue` and `newValue`.
> - The first update of a location the app has no stored values for is only remembered. It fires with old and new values from the next change on.

### Does Location updated give the previous address?

No. Shopify's help page says the trigger provides only the current values of the location. Location Updated in this app lists each changed part of the address with its old and new value.

### Can Flow's Location updated trigger watch the name of a location?

The name is not among the fields listed on Shopify's help page. Location Updated in this app reports a name change with the old and the new name.

### Why did my workflow on the address field run twice?

In our test Shopify wrote the latitude and longitude after an address change, and a workflow watching the whole `address` ran again for that write. Watch single parts of the address, such as `address.city` and `address.zip`, if that is not what you want.

### Is there a trigger for a location being deactivated?

Yes. Location Deactivated and Location Activated fire for exactly these two events.

## Next steps

- [Location triggers, step by step](https://docs.workflow-trigger-extensions.app/location-trigger-tutorials.md) - every location trigger with an example.
- [Flow's Inventory item updated trigger, and SKU, cost and stock in this app](https://docs.workflow-trigger-extensions.app/inventory-item-updated-trigger-comparison.md) - stock per location with the quantity before and after.
- [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.
