Shopify has set August 26, 2026 as the deadline for stores on non-Plus subscription plans to replace their legacy Thank you and Order status pages. Stores that have not upgraded by the deadline will be moved to the new pages automatically.
For stores that use Shopify's standard post-purchase experience, the change may require little work. The risk is higher for merchants that added tracking widgets, analytics, redirects, custom messages, or other functionality through additional scripts, script tags, or older apps.
The important point is that Shopify is not removing order tracking. It is removing the legacy ways merchants and apps customized the pages where customers often check that tracking.
The Short Version
- August 26, 2026 is the non-Plus deadline. Stores that have not upgraded will be moved to the new Thank you and Order status pages automatically.
- Additional scripts have been view-only since August 28, 2025. Existing code can no longer be edited from Checkout settings and needs to be replaced rather than patched.
- Order tracking is explicitly included in Shopify's upgrade report. Shopify categorizes detected additional scripts by purpose, including order tracking.
- App compatibility deserves attention first. If an installed app customizes these pages, the relevant functionality needs to be available through Shopify's newer blocks or pixel architecture.
- Shopify's native order tracking remains. What changes is how merchants extend the Thank you and Order status pages around it.
What Actually Changes on August 26?
Shopify is moving non-Plus stores from the legacy Thank you and Order status pages to versions built on its newer checkout and customer accounts architecture. The new pages are customized through Shopify's checkout and accounts editor rather than by inserting arbitrary scripts into the page.
Shopify's migration guide tells merchants to replace older page customizations with app blocks, web pixels, app pixels, built-in Shopify features, compatible Shopify apps, or custom apps, depending on what the old code was doing.
This distinction matters. The deadline does not mean every app installed on a store suddenly stops working. It means functionality that depends on legacy Thank you or Order status page mechanisms can no longer be relied on after the migration.
For example, an app might continue handling fulfilment normally while losing an old widget it injected into the Order status page. Another app might already support the new page architecture and only need its block to be added to the new configuration.
Three Dates Merchants Should Know
| Date | What happened | Why it matters |
|---|---|---|
| August 28, 2025 | Additional scripts became view-only in Checkout settings. | Legacy scripts can no longer simply be edited to fix a problem. Their functionality needs to be replaced. |
| August 26, 2026 | Deadline for non-Plus stores to upgrade the Thank you and Order status pages. | Stores that have not upgraded will be moved to the new pages automatically. |
| After August 26, 2026 | Legacy page customizations are no longer a fallback for non-Plus stores. | Tracking widgets, analytics and other post-purchase customizations need to work with the newer architecture. |
Shopify Plus stores followed an earlier migration schedule, so the August 26 deadline specifically matters to stores on non-Plus subscription plans.
Can a Store Revert After Upgrading?
Only temporarily, and only when specific conditions are met. Shopify allows a non-Plus store to revert to the legacy Thank you and Order status pages before August 26, 2026 if all three of the following are true:
- The store was created before January 6, 2025.
- It already had customizations using additional scripts or apps using script tags.
- The merchant manually upgraded less than 30 days earlier.
That makes reverting a migration safety net rather than a long-term option. If the store remains on the legacy pages when the August 26 deadline arrives, Shopify states that the pages will be upgraded automatically.
There is also a specific exception for paused stores. Stores placed on Shopify's Pause and Build plan are upgraded automatically, and Shopify states that this upgrade cannot be reverted even after the store is unpaused.
What Shopify's Native Order Tracking Already Does
Before replacing an old tracking customization, it is worth understanding what Shopify already provides. Some stores may discover that part of their old code is no longer necessary.
When a tracking number is added to a fulfilled order, customers can follow the shipment through the Order status page, shipping notification emails, and the Shop app.
| Capability | Native Shopify support |
|---|---|
| Tracking number | Added automatically with eligible Shopify shipping labels or manually during fulfilment. |
| Carrier recognition | Shopify recognizes tracking numbers from hundreds of carriers worldwide. |
| Automatic tracking link | Generated for recognized carriers. |
| Shipment location updates | Displayed on the Order status page when supported by the carrier. |
| Unknown carrier | The merchant can select another carrier or enter the carrier's full tracking URL. |
| Customer notifications | Shipping notifications can be sent at key points in the delivery process. |
| Shop app | Supports order status updates, shipping milestone notifications, estimated delivery dates and live-map tracking when data is available. |
| Carrier-level tracking | Customers can follow the tracking link to the carrier's own website for additional carrier information. |
This is an important part of the migration decision. A store does not necessarily need another tracking app simply because its old Order status page contained tracking code.
The question is what the merchant needs beyond Shopify's native tracking.
Where Native Tracking Can Become Limiting
The limitations tend to become more visible as a store adds markets, fulfilment partners and carriers.
Shopify can recognize tracking numbers from hundreds of carriers, but support is not identical across every carrier. Detailed in-page shipment updates depend on supported carrier data, and an unrecognized carrier requires the merchant to supply the tracking URL manually.
There is also a difference between showing a customer where a parcel is and managing delivery performance across a business.
A merchant shipping a few hundred orders through one national carrier might need little beyond Shopify's built-in experience. A business using postal operators, regional couriers, cross-border consolidators and several 3PLs may need a layer that normalizes those carrier events into one view.
That is where the upgrade becomes more than a technical migration. It is an opportunity to decide which post-purchase capabilities are actually required.
Why Tracking Customizations Need to Be Checked
Shopify explicitly lists order tracking as one of the purposes used to categorize detected additional scripts in its upgrade guide.
That does not mean every store with tracking has a problem. It means merchants that previously added tracking-related behavior through the legacy page need to identify how that behavior is implemented.
Examples can include:
- a third-party tracking widget embedded into the Order status page;
- custom JavaScript that changes or supplements tracking information;
- a carrier redirect generated by a legacy app;
- analytics code measuring interactions with post-purchase tracking;
- custom delivery messages based on an order or fulfilment state;
- an app that injects content into the legacy page using a script tag.
Some of these functions can be replaced with Shopify's built-in features. Others need an updated app, app block, pixel, or custom implementation.
Which Migration Path Applies to Your Store?
| What you find | What it means | Next action |
|---|---|---|
| Upgrade guide is empty | Shopify did not detect legacy customizations that need replacing. | Review the new pages and proceed with the upgrade. |
| Compatible installed app | The developer has added support for the new pages. | Follow Shopify's instructions to configure its blocks or pixels. |
| Incompatible app | The app still depends on functionality that has not been migrated. | Check with the developer or evaluate another app. |
| Additional script | Custom logic is still attached to the legacy page. | Identify what the script does and replace it with a built-in feature, compatible app, pixel, or custom app. |
| Order tracking customization | Tracking-related logic was detected on the legacy page. | Compare what the customization does with Shopify's native tracking before rebuilding it. |
How to Audit the Upgrade in Four Steps
- Go to Settings, then Checkout. Review the Configurations section. If Shopify displays a notice to upgrade the Thank you and Order status pages by August 26, the store is still using the deprecated versions.
- Open the customization review. Shopify automatically generates an upgrade guide based on the customizations it detects.
- Check incompatible apps before rewriting scripts. Shopify separates apps that already support the new pages from apps that still require work from their developer. External developer work can create more uncertainty than a script that your own team controls.
- Review every additional-script category. If order tracking, authentication, analytics, or another function appears, identify what business process depends on it before choosing a replacement.
If the upgrade report is empty, Shopify says merchants can move directly to publishing the replacement pages. There is no benefit in rebuilding functionality that is not there.
Six Questions to Ask Before Rebuilding Tracking
If tracking does need to be replaced, copying the old setup exactly may waste the opportunity. The better approach is to define what the post-purchase experience needs to do now.
1. How many carriers does the store really use?
Do not count only contracted carriers. Include postal partners, last-mile handoffs, regional couriers, 3PL-selected carriers and international delivery partners. Cross-border orders often involve more networks than the merchant books directly.
2. Can the system follow a parcel across carrier handoffs?
A tracking number can move through more than one network during an international delivery. The customer should not need to understand which operator owns each leg of the shipment.
3. Does tracking expose exceptions, not just milestones?
"In transit" and "Delivered" are useful, but many support contacts are caused by what happens between them. Customs holds, failed delivery attempts, address issues, pickup availability and other exceptions are often the events that need action.
4. Can the operations team see every carrier in one place?
A customer-facing page solves only one side of tracking. Merchants using several carriers also need a practical way to find delayed or problematic shipments without opening a separate carrier portal for each network.
5. Where does the customer go after clicking Track?
A carrier website can be enough for simple shipping setups. Other merchants prefer to keep tracking within a branded post-purchase experience, particularly when several carriers are involved.
6. Who communicates when delivery changes?
Tracking becomes more useful when delivery events can trigger customer communication. That can include shipment progress, delivery exceptions, availability for collection and final delivery.
What Not to Do Before August 26
The first mistake is treating the deadline as a reason to install a large tracking stack without checking what Shopify already provides. Start with the upgrade report and identify the exact legacy dependency.
The second is assuming that an installed app is compatible because the rest of the app still works. The relevant question is whether its Thank you or Order status page functionality has been rebuilt for Shopify's current architecture.
The third is waiting until the final day to discover that an app still requires work from its developer. Shopify's upgrade guide already separates incompatible apps for this reason.
The fourth is migrating the page without testing the customer path. Place a test order, add tracking, open the Order status page, check the tracking link, review the mobile experience, and confirm that any notifications or post-purchase blocks behave as expected.
Where Ship24 Fits
For merchants that decide Shopify's native tracking is enough, there is no reason to add another tracking layer simply because of the August 26 migration.
For stores that need broader multi-carrier tracking, a branded tracking experience, centralized shipment visibility, or more detailed delivery notifications, a tracking app becomes more relevant.
Ship24 AI Order Tracking currently lists more than 2,500 connected couriers on the Shopify App Store. Its free plan includes end-to-end multi-carrier tracking, a shipment dashboard, branded tracking page, delivery notifications, carrier estimated delivery dates, and an Order Status Page Widget.
AI carrier auto-detection, AI-optimized tracking updates, smart event categorization, and additional customization are listed under the Essential plan rather than the free tier. This distinction matters when comparing what is needed for the migration with what might be useful later.
Whichever app a merchant chooses, its compatibility should still be checked inside the store's own Shopify upgrade guide before the old pages are replaced.
Quick Answers
Who does the August 26, 2026 Shopify deadline apply to?
It applies to stores on non-Plus Shopify subscription plans that still use the legacy Thank you and Order status pages. Pause and Build stores are upgraded automatically, while Shopify Plus stores followed a separate earlier migration schedule.
Is Shopify order tracking going away?
No. Shopify's native order tracking remains available. The change affects the legacy methods used to customize the Thank you and Order status pages, including additional scripts and apps that depend on older script-based mechanisms.
What can stop working after the upgrade?
Functionality tied to additional scripts, legacy script tags, or incompatible app customizations can disappear if it has not been recreated for the new pages. Shopify recommends blocks and pixels for compatible page customizations and tracking.
What happens if a merchant does nothing?
Shopify states that non-Plus stores still on the legacy pages will be upgraded automatically on August 26, 2026. Legacy customizations should not be assumed to carry across to the replacement pages.
Can the upgrade be reversed?
Only before August 26, 2026 and only when the store meets Shopify's three revert conditions: it was created before January 6, 2025, had pre-existing additional-script or script-tag customizations, and was manually upgraded less than 30 days earlier.
How can a merchant tell if an app is incompatible?
Open the Shopify upgrade guide from Settings > Checkout. Shopify lists apps that support the new pages and separates apps that still require an update from their developer.
Use the Deadline to Remove Technical Debt
August 26 should not be treated as a deadline to reproduce every line of legacy code. It is a deadline to identify what still has a business purpose and rebuild only what the store still needs.
For a small store using one or two well-supported carriers, Shopify's native tracking may cover most post-purchase needs. For a merchant shipping internationally through several carriers and 3PLs, the same review may expose gaps in carrier coverage, exception handling, customer communication, or operational visibility.
The best outcome is not a new Order status page that looks exactly like the old one. It is a post-purchase setup with fewer dependencies on legacy code and a clearer answer to a question customers will keep asking long after August 26: where is my order?
Sources & Methodology
- Shopify Help Center, primary source: Non-Plus guide for upgrading and replacing the Thank you and Order status pages. Used for the August 26 deadline, automatic upgrade, compatibility process, additional-script restrictions, Pause and Build treatment, and revert conditions.
- Shopify Help Center, primary source: Order tracking at Shopify. Used for native tracking behavior, carrier recognition, tracking links, Order status page updates, and Shop app capabilities.
- Shopify App Store, primary product listing: Ship24 AI Order Tracking. Used for current courier coverage, product features, plan availability, and the distinction between Free and Essential functionality.
