See all services → Shopify Plus Partner
Action Required Developer

Fix Customer Account Navigation Reads Before API 2027-01

API version 2027-01 flips what currententrychange reports in customer account full-page extensions. Extensions reading the destination from event.from will render the wrong route, silently, with no error raised.

Executive summary

What changed

Customer account UI extensions can register a listener for navigation changes. On API version 2026-10 and earlier, that listener received an event whose from property actually held the new entry, the same value already exposed as shopify.navigation.currentEntry. The reference documentation described from as the previous entry. Starting with 2027-01 the behaviour matches the documentation: from is the previous entry, and the destination has to be read from shopify.navigation.currentEntry.

Nothing changes on 2026-10 or earlier, and nothing changes for extensions that already read shopify.navigation.currentEntry or use the useNavigationCurrentEntry hook. The correction bites only where event.from was used as a shortcut to the current page.

Why it matters

The failure mode is quiet, which is what makes it worth scheduling rather than discovering. An extension that picks its route from event.from.url does not throw on 2027-01. It renders the page the shopper just left, one step behind on every click. On a logged-in account area carrying order history, reorder flows, subscription management or B2B account tools, that reads to the buyer as a broken portal, not a version mismatch.

For Shopify Plus merchants who have moved to new customer accounts and built self-service into that surface, the account area is increasingly where repeat revenue is handled. Multi-route extensions are the norm there: an order lookup that drills into a detail view, a quote request that steps through a form, a returns portal. Each of those is the affected pattern. If you are still weighing the move, our guide to new customer accounts versus classic covers the tradeoffs.

Remediation is cheap if taken early. The replacement code runs on 2025-10 and later, so it can ship now, decoupled from any version bump.

Role-specific impact

Use-case example

Real-world scenario

A distributor running new customer accounts on Plus ships a three-route reorder extension: order list, order detail, and a cart builder. The router reads event.from.url to decide which view to mount. On 2026-10 this works. After the move to 2027-01, a buyer tapping an order sees the order list again, taps a second time, and only then lands on the detail view. The extension never errors, so dashboards stay green while support tickets climb. The fix itself is a two-line change in one file. Catching it in staging costs about fifteen minutes of QA. Catching it in production cost this merchant a week of degraded self-service on an account area that handled 38 percent of repeat orders the previous quarter.

Implementation checklist

  1. Inventory your extensions on the customer-account.page.render and customer-account.order.page.render targets.
  2. Search the codebase for currententrychange and flag every handler that reads the from property.
  3. Replace destination reads with shopify.navigation.currentEntry.url, keeping event.from only where the previous page is genuinely what you want, such as back behaviour or navigation analytics.
  4. Deploy the corrected handlers on your current API version. The new code is supported from 2025-10 onward, so it need not wait.
  5. In a development store, navigate between two routes and confirm each click renders the destination rather than the origin.
  6. Only then move the extension to API version 2027-01, and repeat the navigation test against the new version.

FAQ

Q: Can we defer this until we are forced onto 2027-01?

A: You can, but the corrected code runs on 2025-10 and later, so there is no reason to couple it to the version bump. Fixing it now removes a dependency from the upgrade and shrinks the regression surface of that release.

Q: How do we tell whether we are exposed without reading all the code?

A: Search for currententrychange across your extension source. If no handler reads the from property, you are not affected. Extensions already reading shopify.navigation.currentEntry, including those using the useNavigationCurrentEntry hook, were correct to begin with.

Resources

Navigation API reference for customer account UI extensions

Need guidance? Talk to Makro.