Commerce Architecture
Shopify Scripts (Deprecated)
Definition
Shopify's legacy Ruby-based checkout customization platform for Shopify Plus, used for custom discount, shipping, and payment logic. Shopify froze Script editing on April 15, 2026 and stopped executing Scripts on June 30, 2026; Shopify Functions is the replacement.
By Herzel MishelFounder, AgentisLast reviewed
Shopify Scripts was the first programmatic checkout customization layer Shopify offered, available only on Shopify Plus. Merchants used the Script Editor app to write small Ruby programs that ran during checkout. There were three script types: line item scripts (discounts and price changes on cart items, the most common use), shipping scripts (hiding, renaming, or discounting shipping rates), and payment scripts (hiding, renaming, or reordering payment methods). For years it was the main way to implement checkout logic beyond what Shopify's native discounts supported, such as tiered discounts, discount caps, or customer-tag-based pricing. Shopify replaced Scripts with Shopify Functions, which compile to WebAssembly and run inside Shopify's infrastructure with a more predictable performance and security model. The timeline is now complete: Script editing and publishing froze on April 15, 2026, and Scripts stopped executing on June 30, 2026. Logic that was still in Scripts at that point simply stopped running; there was no fallback, so a discount cap or payment filter that lived in a Script no longer applies unless it was rebuilt. Migration options depend on the merchant. Teams with developers can rewrite Scripts logic as Functions, which requires Rust or JavaScript, the WebAssembly toolchain, and Shopify's Function schemas. Others use apps that ship pre-built Functions for common cases, or move simple logic into Shopify's native discount settings, which have gained combination and usage controls. Some logic turns out not to be needed and can be dropped. For merchants whose Scripts protected margin, for example by capping discounts on low-margin SKUs, the in-checkout part of that protection belongs in Functions or discount settings. A separate question is whether orders are still shipping below margin once current COGS, freight, fees, and FX are counted, which checkout rules generally cannot see. That is where a post-order check fits. Agentis is not a Scripts replacement and does not run in checkout: it reads each order after it is placed, computes true net margin within 60 seconds, and flags the order or holds it before fulfillment under merchant-approved rules. Merchants rebuilding Scripts logic can use both: Functions for the checkout rule, and a post-order margin check as the backstop.
Sources
Related Terms
Commerce Architecture
Shopify Functions
Shopify's platform for customizing backend commerce logic, such as discounts, cart and checkout validation, delivery and payment customization, cart transforms, and order routing. Functions are compiled to WebAssembly and run inside Shopify's infrastructure. They replaced Shopify Scripts, which stopped executing on June 30, 2026.
Commerce Architecture
WASM Checkout (WebAssembly at Checkout)
The use of WebAssembly modules to run merchant-defined logic inside checkout. Shopify Functions, the replacement for Ruby-based Shopify Scripts, is the best-known implementation: logic is compiled to WebAssembly and executed in a sandbox within Shopify's checkout.
Profit Governance
Checkout Governance
The set of rules applied inside checkout that decide which discount combinations, shipping options, payment methods, and order configurations a buyer can complete. It acts before the order is placed, which makes it distinct from post-order margin controls that act before fulfillment.
More in Commerce Architecture
See how Agentis compares to other ecommerce profit tools → View all comparisons