Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Starting with API version 2027-01 for customer account full-page extensions, event.from becomes the previous history entry in customer-account.page.render and customer-account.order.page.render.
- Full-page extensions on 2027-01+ are affected only when they use event.from to identify the new page; behavior remains unchanged in 2026-10 and earlier versions.
- Read the newly opened page from shopify.navigation.currentEntry.url. currentEntry and the useNavigationCurrentEntry hook are unaffected in every version.
- currentEntry.url works with API versions 2025-10 and later, so you can migrate the code before planning a version upgrade.
Confirm the version and extension scope first
Shopify announced the change in its developer changelog on October 31, 2026. It takes effect in API version 2027-01 for customer account full-page extensions. As of this article's first publication date, November 6, 2026, the changelog index identifies 2027-01 as a release candidate. That describes the version's status; it does not mean every store switches automatically on January 1, 2027, and the announcement sets no universal upgrade deadline. Check the API version configured for your extension separately.
The scope is the currententrychange navigation event in customer account full-page extensions. The announcement names the customer-account.page.render and customer-account.order.page.render targets. Do not infer from the version notice alone that every Shopify app or account page is affected; confirm your extension type, render target and API version.
Understand the change from destination to previous page
In these two full-page extension targets, the currententrychange event carries a Navigation Current Entry Change Event. In API 2026-10 and earlier, event.from points to the newly opened page and has the same value as shopify.navigation.currentEntry. Starting in API 2027-01, event.from instead refers to the history entry the customer navigated away from: the previous page.
As a result, code that reads event.from.url as the current destination will receive the previous page's URL in 2027-01+. A handler that selects page content or a route from that value may keep showing the page the customer left. The compatibility issue applies to code that treats event.from as the new page on the affected versions; the older version behavior has not changed at the same time.
Read the destination from currentEntry
When a handler needs to know which page navigation just opened, read the current entry's URL from shopify.navigation.currentEntry.url, then keep your existing path extraction or route matching. Do not keep using event.from.url to infer the destination, and do not rewrite the entire routing decision just for this change. Preserve the page mapping and replace only the source used to read the destination.
shopify.navigation.currentEntry itself is unaffected by this change in every API version, and extensions using the useNavigationCurrentEntry hook are also unaffected. Shopify says currentEntry.url works with API versions 2025-10 and later, so a team can make this code change before upgrading to 2027-01 and avoid debugging a version switch and a changed event meaning at the same time.
Review both full-page targets
Cover every currententrychange handler in customer-account.page.render and customer-account.order.page.render, and confirm the API version each one runs on. Look for event.from.url being treated as the current path, including uses passed through helper functions or destructured into another variable. Only reads that identify the page just opened need to switch to currentEntry.url.
In 2027-01+, event.from means the previous page. If a handler genuinely needs to record the page that was left or retain the previous history entry, decide whether to keep that use based on its meaning; do not remove every event.from reference mechanically. If the extension still supports an earlier API version, confirm the intended use against that version's event semantics.
Check the result by navigating between two routes
Shopify recommends navigating between two routes and checking that each navigation shows the destination. For example, plan a check from route A to route B and back to A, comparing currentEntry.url with the rendered route after each event. This is a proposed check for your team, rather than a completed store test.
If the previous route still appears, check the extension version and target actually loaded, then look for destination reads of event.from that remain in helper functions. Keep the reproduction path and previous and current URLs to narrow the investigation. Passing this check verifies that navigation case; it does not establish that every extension feature or business flow works.
Sources
Frequently Asked Questions
Can I apply the replacement directly on a version older than 2025-10?
The announcement explicitly supports the currentEntry.url replacement on 2025-10 and later, without making the same compatibility statement for older versions. Check the target version available to your extension and its documentation first. Unchanged event behavior on 2026-10 and earlier does not mean every old version supports this replacement.
Does this change also alter plan eligibility, regions or fees?
The announcement describes navigation-event semantics and version migration. It states no new plan, country or charging conditions, so it does not establish expanded eligibility or new free access. Check the current official requirements for the particular extension capability separately.