Customer account full-page extensions: event.from changes meaning in 2027-01

What changed

In customer account full-page extensions (customer-account.page.render and customer-account.order.page.render), the Navigation API currententrychange event passes a NavigationCurrentEntryChangeEvent. The meaning of its from property changes in API version 2027-01.

• In 2026-10 and earlier, event.from is the new entry, the same value as shopify.navigation.currentEntry.

• From 2027-01, event.from is the previous entry, the page the customer navigated away from. The Navigation API reference documents it this way.

Shopify's changelog entry is dated 31 October 2026 and flags this as a breaking API change that requires action.

Who is affected

You are affected if your customer account full-page extension reads the new page from event.from in a currententrychange handler, and you are moving it to API version 2027-01 or later. The changelog names the customer-account.page.render and customer-account.order.page.render targets.

Not affected

• Extensions on API version 2026-10 and earlier. Their behaviour does not change.

• Extensions that read shopify.navigation.currentEntry, on any version. This includes extensions that use the useNavigationCurrentEntry hook.

The sources do not say whether other kinds of customer account extension are affected. The changelog describes the change only for full-page extensions.

What to do

Before you move a customer account full-page extension to 2027-01, find every currententrychange handler that reads the new page from event.from. Replace those reads with shopify.navigation.currentEntry.url.

shopify.navigation.addEventListener('currententrychange', (event) => {
  setPath(new URL(event.from.url).pathname);
});

shopify.navigation.addEventListener('currententrychange', () => {
  setPath(new URL(shopify.navigation.currentEntry.url).pathname);
});

The updated code works on API version 2025-10 and later, so you can ship it before you change your API version.

Versions before 2025-10

shopify.navigation.currentEntry is not available in API versions before 2025-10. The Navigation API reference says to use currentEntry on the navigation object from the extension API instead, such as useApi().navigation in React.

Check the change

Navigate between two routes in your extension and confirm that each navigation shows the page you navigated to.

What breaks if you do nothing

Nothing breaks while an extension stays on 2026-10 or earlier, because behaviour on those versions does not change. The break happens when you move the extension to 2027-01 without updating its handlers.

On 2027-01, code that reads event.from.url gets the URL of the page the customer navigated away from, not the page they navigated to.

The changelog gives one example of the effect: an extension that chooses which route to render from event.from keeps showing the previous route after each navigation. The customer moves to a new page, but the extension still renders the one they left.

Deadline

Shopify has not announced a calendar deadline for this change. The behaviour changes when an extension moves to API version 2027-01, not on a fixed date.

The versioning page lists 2027-01 as a release candidate with a release date of 1 January 2027. It lists 2026-10 as accessible until 16 October 2027 at 15:00 UTC. That is the date to plan around for extensions that stay on 2026-10: after it, the versioning page says Shopify falls forward to the oldest accessible stable version. The sources do not say how that fall-forward applies to customer account UI extensions, so check that before relying on it.

The 31 October 2026 date on the changelog entry is when the change was announced. It is not a deadline.