Shopify Scripts stopped running June 30, 2026. Non-Plus stores lost checkout.liquid and Additional Scripts entirely on August 26, 2026. Shopify's automatic upgrade was best-effort — it carried over the easy cases and quietly dropped the rest. Most stores are running with custom logic silently missing, and nobody's checked.
Each engagement is fixed-scope. No open-ended retainers to start, no "let's hop on a call to figure out pricing."
We review one client store and tell you exactly what's broken:
# deliverable: written report, severity-ranked. No commitment beyond it.
Book an auditWe rebuild your Ruby Script logic as native Shopify Functions:
# tested against realistic cart sizes before deploy · docs + exported rule config included
Get a quote See the full migration process →Ongoing coverage for agencies running Plus checkout logic across multiple stores:
# built for agencies, not single-store merchants
Talk to usOne point of contact for every client store, not a new vendor relationship per client. Become a design partner and we migrate your first client store free — the rules we build become reusable Rulic config you deploy to the next client yourself. That's the whole idea: service work today becomes product you self-serve tomorrow.
Every rule compiles to a native Function running inside Shopify's WASM sandbox, with hard technical ceilings most teams discover in production — usually the hard way. We design around them from day one, on every audit and every migration.
These aren't edge cases — they're the reason a Scripts-to-Functions port isn't a copy-paste job. A rule that worked fine on Scripts can fail outright once it's a Function, if nobody accounts for these.
Every rule we build during an audit or a migration is delivered back to you as portable Rulic configuration — not a one-off repo only we understand. Once your logic lives in Rulic, changing a rule or deploying it to the next client store is something you do yourself, in minutes, without opening another ticket with us.
Start with the audit if you're not sure anything's actually broken. Go straight to the migration if you already know it is. Either way, tell us what you're running and we'll tell you plainly what it needs.
Need something outside these three? Tell us what you're building.