Scripts to Functions
Shopify Scripts, the Ruby-based customisation layer for Plus checkouts, was retired on 30 June 2026. Any discount, shipping or payment logic that still lives in Scripts needs to be rebuilt as Shopify Functions. Mojito Labs inventories every script, rewrites the logic as Functions, replays it against last year's orders to prove it behaves the same, and releases it market by market.
Two to six weeks for most stores. Scope and fixed price in writing after a one-day inventory of your scripts.
What you probably have in Scripts.
Tiered discounts, buy-X-get-Y, segment pricing, bundle pricing, gift with purchase. These become discount Functions.
Hidden or renamed rates, free shipping thresholds, rules by pin code or customer tag. These become delivery customisation Functions.
Cash on delivery limits, hidden gateways per market or cart value. These become payment customisation Functions.
Written by a previous agency, edited in the Script Editor, undocumented. The inventory finds them before customers do.
What we do.
Same behaviour, proven by replay, then a cleaner ruleset than you started with.
Most Scripts accumulated years of exceptions. The rewrite is the moment to retire rules nobody uses and to make the remaining ones configurable by marketing through metafields, so the next promotion does not need a developer.
How it runs.
Two to six weeks, depending on how many rules survive the inventory.
Fixed scope, fixed price, agreed after the inventory. How we work.
Technical notes.
Functions are not Scripts with new syntax. Scripts ran Ruby on every cart change with few limits. Functions run WebAssembly inside checkout with strict budgets for time and instructions, and they are deployed as part of an app, not edited in the admin. Logic that looped over large carts or called out to data must be redesigned, not translated.
Configuration moves to metafields. Thresholds, tiers and eligible collections live in metafields or the discount's own settings, so marketing changes them without a deploy.
Discount combinations are explicit. Functions declare how they combine with other discounts. Part of the specification is deciding what stacks with what, which Scripts often left implicit.
Replay is the acceptance test. We export the last twelve months of orders, run the cart through the new Functions, and compare totals line by line. The migration is done when the diff is explained.
Asked about Scripts to Functions.
Scripts were retired on 30 June 2026 and are no longer supported. If promotions or shipping rules depend on them, confirm what is actually applying at checkout today; a one-day inventory tells you. The free readiness audit includes a Scripts dependency check.
Sometimes. Discount apps cover common patterns and are built on Functions themselves. When your rules are standard, we recommend the app; when they are yours, a custom Function is cheaper to own over time.
Custom Functions for discounts, delivery and payment customisation are available to Plus stores. Public apps built on Functions can be installed more broadly. The assessment tells you which path fits your plan.
Only where you decide they should. The replay against last year's orders surfaces every difference before release, and you approve each one.


