Shopify Scripts stopped executing on June 30, 2026. A Script still visible in an old configuration is no longer checkout logic, so migration work should begin with the behavior the store needs rather than the Ruby implementation it used to run.
Shopify's deprecation announcement recommends using the Shopify Scripts customizations report to inventory existing behavior and plan replacements.
Start with an inventory
For each Script, record:
- The business rule and who owns it.
- The carts, customers, products, delivery options, or payment methods it affects.
- Whether the result is a discount, a delivery or payment-method change, a checkout validation, or another behavior.
- Interactions with native discounts, shipping settings, apps, subscriptions, B2B purchasing, and accelerated checkout.
- Representative carts that should pass, change, and remain unaffected.
Do not treat the Ruby source as the specification. Old code often contains expired campaigns, defensive branches, and implementation details that should not survive the migration.
Map the behavior to a current extension point
Shopify Functions run backend commerce logic for capabilities such as discounts, delivery customization, payment customization, and cart and checkout validation. The correct API depends on the outcome, and plan or distribution restrictions can differ by Function type.
- Discount behavior belongs in Shopify's current Discount Function API or a suitable public app.
- Hiding, renaming, or reordering delivery and payment options belongs in the corresponding customization Function.
- Order, quantity, address, or B2B purchase requirements may fit cart and checkout validation.
- Shopper-facing interface changes are a separate checkout UI extension decision and can carry Shopify Plus requirements.
Native Shopify settings should remain the first option when they fully express the rule. A custom Function is useful when the requirement needs conditions, ownership, or operational controls that the native setting does not provide.
Rebuild the operating workflow
A replacement is more than equivalent checkout output. Decide how the merchant will configure, review, publish, disable, and audit the new rule. Keep drafts and test cases separate from live behavior where the implementation allows it.
Before release, test carts that should qualify, carts that should not qualify, combinations with other discounts or apps, B2B and non-B2B buyers where relevant, and accelerated checkout paths affected by the rule.
Choose an implementation path
Cart Marshal provides managed discount, delivery, payment, and validation rule templates with draft and publish workflows. A custom implementation may be more appropriate when a store has proprietary logic or needs an extension point that a configured product does not cover.
Five Acre Code can plan and implement a Shopify checkout migration or help determine whether native settings, an existing app, Cart Marshal, or custom development is the smallest durable solution.