Checkout / Improvement

In checkout,
you can now set and manage a "default address"

Signed-in customers can now set a default address during checkout. This replaces the previous "last used address" logic. The default address can be updated at any time, either from checkout or from the account profile.

On this page
  1. What's actually changing (understand in 30 seconds)
  2. How it works: how the default address is determined
  3. When the default address is "set automatically"
  4. Previous (last used) vs. default address comparison
  5. Conditions and what's not stated
  6. 5 key points for developers
  7. 3 use cases you can apply to your business
  8. A one-line summary you can use when pitching

1What's actually changing

Previously, for signed-in customers, the shipping address "last used address" was selected automatically.
From now on, customers themselves can explicitly set and manage a "default address", and this replaces the old logic.

Previous: last used address

The most recently used address was selected as-is. When the "address you usually ship to" differed from the "address you happened to use last," you had to re-select every time.

New: default address

The address the customer designates as "my default" is selected preferentially. It can be changed at any time, either from checkout or from the account profile.

2How it works: how the default address is determined

Signed-in customer Checkout starts Is there a default address? When adding the first address / placing the first order, one address is automatically set as the default Check the default Apply the default to the shipping address ★ Default address Other addresses can also be selected Show the default rather than the last used address Update anytime From checkout · From the account profile Managed by the customer
The key point is the shift from "last used address" to "a default address chosen by the customer". It is explicitly stated that the same default address can be updated frombothcheckout and the account profile.

3When the default address is "set automatically"

The article explicitly lists two conditions for automatic setup. The default address is set automatically when the customer registers their first address, or when they place their first order.

① When the first address is added

When a customer registers their first address, that address is automatically set as the default.

② When the first order is placed

When a customer places their first order, that address is automatically set as the default.

Even after automatic setup, the customer cancheckoutorthe account profilechange the default address fromat any time.

4Comparison: previous (last used) vs. default address

ItemPrevious: last used addressNew: default address
Address selected Most recent Last used address Default The default address set by the customer
Customer control No explicit specification (depends on history) Customer can set and manage it
Initial setup — Automatically set on first address added / first order placed
Where it can be updated Not specified (depends on history) Checkout + account profile
Target During checkout,logged inCustomers

5Conditions and items not documented

Customers this applies to

During checkout,logged-incustomers are the target. The article does not document the behavior for guest checkout.

?

Points marked "not documented" in the article

Supported regions, eligible plans, the timing of the gradual rollout, handling of billing addresses, and behavior in the Admin API / Webhooks are not documented in this article.

This article falls under the Changelog's "Improvement / Checkout" category.The article only describes the behavior above, and anything else (API specs, whether configuration is required, etc.) should not be inferred — verify in the Shopify admin or official documentation if needed.

65 points engineers should keep in mind

1. This is a logic replacement

The "last used address" logic is being replaced with "default address." Because the address auto-selection behavior is changing, you should check any existing flows that assume address selection (especially how reorders and subscription renewals appear).

2. There are two update paths

The default address can be updated frombothcheckout and the account profile. Updating from either side updates the same default address — it's natural to think of it as a single value tied to the customer account.

3. The initial value is filled in automatically

Because the default is set automatically on the first address added / first order, a state where "the default is unset and empty" basically shouldn't happen. There's little need to prompt new customers to configure this during onboarding.

4. Logged-in customers are the premise

The target is "customers who are logged in during checkout." The value of flows that encourage account login (login CVR) goes up another notch in the form of reduced address-entry effort.

API ?

5. API / Webhook specifications are not documented in this article

The Changelog body only describes customer-facing behavior. How to read and write a Customer's default address via the Admin GraphQL or Webhooks, and how to reference it from themes / Checkout Extensions, arenot mentioned in this article. If you need automation or integrations, verify separately in the official API documentation (don't infer).

73 use cases you can apply to your business

★Default
USE CASE 1

Reduce cart abandonment by instantly selecting the "usual shipping address" for repeat orders

Problem
On repeat purchases by members, the most recently used address (such as a gift recipient) would be selected, forcing customers to switch it back to "home" every time.
Action
Switch to an operation where customers set their "usual shipping address" as the default address. Guide them through a flow where the default is set automatically at the time of account creation or the first order.
Effect
Less effort spent correcting addresses, and a smoother checkout completion for logged-in members. You can also expect a reduction in delivery issues caused by address mistakes.
Technical notes
The behavior assumes "logged-in customers." The more you strengthen the account login flow, the greater the effect. Guest behavior is not documented in the article.
USE CASE 2

Preventing "billing and shipping address mismatches" for subscriptions / recurring orders

Problem
There was a risk that, if a subscription member shipped a one-off gift and the subscription renewal ran immediately afterward, the "last used address" would be carried over unintentionally.
Action
Have customers explicitly set their regularly used delivery address as the default, so that "default = recurring delivery destination" becomes the norm. Changes can be made anytime from the account profile.
Impact
Address selection shifts from history-dependent guesswork to a "customer-defined default," reducing a common source of misdeliveries.
Technical notes
The article doesn't specify how subscription apps reference the default address. Verify integration behavior in advance — don't build on assumptions.
USE CASE 3

Turning CS "which address?" inquiries into self-serve

Problem
Requests like "I want to change my delivery address" or "please switch it back to my usual address" used to come into CS, and operators handled them manually.
Action
State clearly in the FAQ and post-order emails that customers can update their default address themselves from the account profile, steering them toward self-serve.
Impact
Reduces address-related inquiry volume. Customers can update their address either during checkout or from their account, completing the change without waiting for CS.
Technical notes
The article specifies two update paths: "checkout" and "account profile." FAQ copy only needs to cover these two routes.

8One-line summary for pitching

"At checkout for logged-in customers, address selection movesfrom "the last-used address" to a customer-chosen "default address.".
It's auto-set on the first address add / first order,and can be changed anytime from either checkout or the account..
An improvement that reduces the friction of fixing addresses on repeat purchases and lowers misdelivery risk."