Services

Did your Scripts migration actually work?

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.

Entry point€400 checkout audit, 48-hour turnaround
Main engagementScripts migration, from €1,800 per store
For agenciesVolume pricing + one free first-store migration
Three ways in

Start small, or start with the migration.

Each engagement is fixed-scope. No open-ended retainers to start, no "let's hop on a call to figure out pricing."

service / 01

Checkout Audit

€400 · 48 hours

We review one client store and tell you exactly what's broken:

  • Script logic that didn't survive the migration
  • Functions failing silently on large carts (11M instruction limit)
  • Metafields over 10,000 bytes returning null in function input
  • Discount, shipping, and payment rules not behaving as intended

# deliverable: written report, severity-ranked. No commitment beyond it.

Book an audit
service / 03

Checkout Retainer

from €600/month

Ongoing coverage for agencies running Plus checkout logic across multiple stores:

  • Rule changes as client requirements shift
  • New client stores onboarded
  • Monitoring for silent Function failures

# built for agencies, not single-store merchants

Talk to us
For agencies

Managing multiple Plus clients?

5 spots — first client store migrated free

Volume pricing across your whole book of business.

One 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.

Volume pricing across stores One point of contact Migration → reusable config
Why trust the migration

We've hit the real Shopify Functions limits.

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.

Constraints we build around by default

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.

11M instruction limit — functions fail on large carts 128kB function input cap Metafields over 10,000 bytes return null in function input
Where this leads

The service is the entry point. Rulic is the business.

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.

Not sure which one you need?

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.