As of August 31, 2026, changing the shipping address on an unfulfilled order through the GraphQL mutation recalculates the order's taxes against the new destination. Previously, saved the new address but left the original tax lines unchanged, so the order's totals no longer matched the destination it was shipping to.
Why it matters
The order's financial data is now corrected as part of the update, now totals stay accurate to the shipping destination. After updating a shipping address, query the order to read the updated , , and totals, as you would for any other order edit. You don't need to make any changes to adopt this.
How it works
This change applies to all Admin GraphQL API versions. Taxes are recalculated only when the change is safe to apply, not on every address update. The address change always succeeds; only the tax recalculation is conditional.
Taxes aren't recalculated when:
- The order is partially fulfilled: On entirely unfulfilled orders, taxes are recalculated. On partially fulfilled orders, the address is saved but taxes are left unchanged, because some units have already shipped to the original destination, and recalculating the whole order against the new address would apply the new destination's tax to units that didn't ship there, producing totals that don't match what was actually fulfilled.
- The order can't be edited: Recalculation runs through order editing, so the same order-editing considerations apply. When an order isn't eligible for editing, the address is saved but taxes aren't recalculated.
Subscribers to the webhook receive a notification when an address change results in a tax recalculation.
To learn more, see the mutation.