Functions / Important Notice

Shopify Scripts,
Full discontinuation on June 30, 2026

Custom logic for discounts, shipping, and payments is moving to Shopify Functions. New edits and publishing stop on April 15, and all Scripts stop running on June 30. The starting point for migration is the "Shopify Scripts Customization Report."

On this page
  1. Understand in 30 seconds: What's happening
  2. Two key deadlines to keep in mind (timeline)
  3. The big picture: Scripts → Functions
  4. The three areas being replaced
  5. How to approach the migration (3 steps)
  6. Five points engineers should understand
  7. Three use cases you can apply to your business
  8. One-line summary for proposals

1Understand in 30 seconds: What's happening

Shopify is discounts, shipping, and payments strengthening Shopify Functions for, and is replacing the functionality previously provided by Shopify Scripts .
As a result,Shopify Scripts will be fully shut down on June 30, 2026. Merchants and developers are strongly encouraged to migrate early.

Until now: Shopify Scripts

Custom logic for discounts, shipping, and payments has been written in Scripts. Going forward, you won't be able to edit or publish new ones, and eventually they will stop executing entirely.

Going forward: Shopify Functions

New capabilities for discounts, shipping, and payments are being expanded, letting you build custom logic tailored to your own requirements. It's positioned as the replacement for Scripts.

The migration target isn't just Shopify Functions — public apps are also listed as an option. Which to lean toward is determined by the "Customization Report" described next.

2Two key deadlines to keep in mind

April 15, 2026

New edits and publishing disabled

You will no longer be able to edit or newly publish Shopify Scripts. Since you can't change the content after this, finish your review by April 15.

June 30, 2026

All Scripts stop executing

All Shopify Scripts will completely stop running. Any logic that hasn't been migrated by this date will no longer work.

After April 15, you can no longer fix Scriptsis the key point. Bug fixes and condition changes will also no longer work, so any Scripts that need changes should be started before April 15. The deadline for the migration work itself is June 30.

3Migration overview: Scripts → Functions

Existing Scripts Discounts, shipping, and payments custom logic Items to inventory Customizations Report Sort migration targets Shopify Functions Custom logic for in-house requirements Public apps Replace with off-the-shelf solutions Migration complete By 6/30
To determine "which Scripts can be moved to Functions and which should be replaced with public apps," the article recommends using Shopify Scripts customizations report . Specific report screens, fields, and output formats are not described in the article.

4Three replacement areas

The article clearly states that the enhanced Shopify Functions covers the following three areas. Detailed specifications and supported APIs for each area are not described in the article.

%

Discounts

A replacement for discount logic built with Scripts, such as quantity-based or conditional discounts.

Shipping

A replacement for custom logic such as displaying, reordering, and conditionally showing shipping methods.

Payments

A replacement for logic built with Scripts, such as conditionally showing or reordering payment methods.

5How to proceed with the migration (3 steps)

The minimum steps following the scope described in the article (sort with the report → move to Functions / public apps → refer to the Help Center).

1

Inventory with the report

Use the "Shopify Scripts customizations report" to identify your current customizations.

2

Decide the migration target

Sort each item into either implementing it yourself with Functions or replacing it with a public app.

3

Switch over by 6/30

Implement and validate while referring to the Help Center migration guide. Note that Scripts cannot be modified after 4/15.

The article strongly recommends "starting the migration as soon as possible." Detailed steps are provided on the Shopify Help Center's "Scripts → Functions migration" page.

65 points engineers should keep in mind

4/15

1. The deadline is in two stages

On 4/15, "editing and publishing stop"; on 6/30, "execution stops completely." Scripts that need fixing must be 4/15 is effectively the deadline.

Before After

2. Two migration paths: Functions or public apps

You don't need to rewrite everything as your own Functions. Carve out the parts that can be replaced by off-the-shelf public apps.

3. Start by understanding the current state via the report

The "Shopify Scripts customization report" is the starting point for your migration plan. Make what's running visible before you begin.

4. Scope is the three areas of discounts, shipping, and payments

The strengthened Functions cover these three areas. Build your roadmap based on which of these your in-house Scripts fall under.

5. Detailed specs and APIs are not included in this article

Specific Functions APIs, implementation details, the report's screen layout, supported plans, and so on are not written in this changelog.Check the migration page in the Shopify Help Center for implementation details. Go to the primary source instead of designing on guesswork.

7Three use cases you can apply to your work

USE CASE 1

"Scripts inventory & migration risk assessment" for existing stores

Challenge
You don't have a grasp of how many Scripts are running on your own or your clients' stores, so it's unclear what will break when they shut down on 6/30.
Approach
Use the Shopify Scripts customization report to inventory every Script and classify them into discounts, shipping, and payments. Tag each one with one of three options: migrate to Functions, replace with a public app, or retire.
Outcome
Visualize the impact on sales and operations from the shutdown in advance. Estimate migration effort and deadlines with solid grounding.
Technical notes
Scripts that need changes cannot be edited after 4/15. Finish the inventory before 4/15 and put anything that needs fixing at the top of the queue.
Script Func App
USE CASE 2

Migration project: reimplementing discount logic in Functions

Challenge
Quantity discounts, bundle discounts, and similar logic are built in Scripts, so promotional campaigns will stop when these are shut down on 6/30.
Approach
Reimplement anything the report flags as "needs migration to Functions" as Shopify Functions Discounts. Shift anything replaceable to a public app.
Outcome
Eliminate shutdown risk while migrating to a stronger Functions foundation that can more easily accommodate future requirements.
Technical notes
Specific Functions APIs and implementation methods are not in this changelog. Implement and verify using the Shopify Help Center migration guide as the primary source.
USE CASE 3

Preparing a "migration roadmap" deliverable for clients

Challenge
You maintain multiple Shopify stores and need to communicate the impact of 4/15 and 6/30 and the required actions to each client all at once.
Approach
Summarize the two deadlines, three areas, and two migration destinations (Functions / public apps) on a single page, and distribute per-store roadmaps with the report results pasted in for each store.
Outcome
Reach agreement with clients on "by when, what, and where to migrate," leading to migration project wins and scheduling alignment.
Technical notes
The article doesn't specify which plans are supported, pricing, or whether migration assistance is available. It's safest to note in your materials that confirmed information should be checked in the Help Center.

8One-line summary you can use in proposals

"Shopify Scripts will be fully shut down on June 30, 2026(new editing and publishing will also stop on April 15).
Logic for discounts, shipping, and payments must be migrated to Shopify Functions or a published app .
First, take inventory using the 'Scripts Customization Report,' thenstart migrating nowto stay safe."