What's actually happening
Shopify announced the deprecation of Script Editor in 2025. Three dates matter:
April 15, 2026
Script editing disabled. Existing scripts kept running, but you couldn't change them.
June 30, 2026
Execution stops. Any active payment script silently fails. Payment methods that you previously hid will appear at checkout. Methods you renamed revert. Methods you reordered shuffle back to Shopify's default order.
Post-June 30
Shopify Functions is the supported replacement. Apps built on Functions (like PayLogic) run natively in checkout with the same hooks Scripts used.
If you're still on Scripts, you've got a hard deadline and a non-optional migration. The question isn't whether to move — it's where to move and how fast.
Your three options
Option 1: Rewrite as a custom Shopify Function
If you have engineering resources and your payment logic is genuinely unique, you can build your own Shopify Function in Rust or JavaScript and deploy it through the Shopify CLI. Expect a few days of dev time plus ongoing maintenance. Sensible for enterprise teams with full-time Shopify devs.
Option 2: Use a payment customization app
For 95% of Scripts use cases — hiding Cash on Delivery, restricting payment methods by country, gating by customer tag — a purpose-built app does the same job in minutes with no code. PayLogic is one of these apps, built specifically for the Scripts migration window.
Option 3: Do nothing and let your rules break
Not recommended. The most common Scripts use cases — hiding Cash on Delivery for high-cart-value orders, blocking prepay for first-time customers, hiding payment methods in restricted countries — exist for real reasons (chargeback prevention, fraud reduction, regulatory compliance). Removing them silently on June 30 can cost real money.
Common Scripts patterns and their PayLogic equivalents
Most production Scripts boil down to a small set of patterns. Here's how the common ones map to PayLogic rules:
| Scripts pattern | PayLogic rule |
|---|---|
Hide Cash on Delivery when cart.subtotal_price > 20000 |
Hide Cash on Delivery when cart total ≥ $200 |
Hide PayPal when cart.shipping_address.country_code == 'BR' |
Hide PayPal when shipping country is Brazil |
Hide all non-credit-card methods if customer.tags.include?('high-risk') |
Hide payment methods when customer is tagged high-risk |
| Block COD if customer has no prior orders | Hide Cash on Delivery for first-time customers |
Hide methods when cart.line_items.any? { |i| i.product.tags.include?('preorder') } |
Hide payment methods when cart contains a product tagged preorder |
| Rename "Manual" to "Bank Transfer" for B2B customers | Rename Manual → Bank Transfer when customer is tagged b2b |
| Move Shop Pay to position 1 for repeat customers | Move Shop Pay to position 1 when customer has ≥ 1 prior order |
| Hide COD when cart item count exceeds 5 | Hide Cash on Delivery when cart has ≥ 5 items |
| No Scripts equivalent | Hide Cash on Delivery when Shopify's risk signals classify the order as high-risk (PayLogic Plus tier — most common use case in MENA, SEA, and LATAM markets where COD return abuse is high) |
The last row is the differentiator. Static rules — by cart total, country, or tag — replicate what Scripts already did. The risk-composite rule uses Shopify's order risk signals to dynamically gate COD on a per-order basis, which Scripts never exposed. For merchants in high-return-abuse markets, this single rule typically eliminates 60–80% of COD chargebacks.
Want to see your own Scripts mapped automatically? Paste them into our free Scripts → PayLogic Rules converter. Runs in your browser, no signup, no upload.
The three-step migration
- Install PayLogic on your store Available on the Shopify App Store. Free Development plan for Shopify Partner dev stores; production plans from $1.99/month with a 3-day trial.
- Run the Scripts importer Open PayLogic in your admin, click Import from Scripts. PayLogic reads your existing Script Editor configuration, identifies the patterns above, and creates equivalent rules. Patterns that don't map cleanly are flagged so you can address them manually.
- Test on a draft order, then enable Place a draft order on a test cart that matches each of your rules. Confirm the right payment methods are hidden, reordered, or renamed at checkout. Once verified, leave Scripts running in parallel until June 30 if you want belt-and-suspenders coverage — there's no conflict; PayLogic's Functions run alongside Scripts.
Why PayLogic specifically
- Native Shopify Functions. Runs at checkout with sub-50ms latency. Same execution model as Scripts but on the supported, future-proof platform.
- One-click Scripts importer. Reads your existing payment scripts and converts the common patterns to PayLogic rules automatically.
- Free Development plan for Shopify Partner dev stores. Test PayLogic on every client project before committing to a paid plan. All paid-tier features unlocked on dev stores.
- Risk-gated hide (composite). Dynamic COD gating using Shopify's order risk signals. Unique to PayLogic's Plus tier — Scripts never exposed this.
- Built for the migration window. Pricing intentionally low ($1.99 / $4.99 / $9.99 per month) so you can adopt without budget review.
FAQ
- Can I run Scripts and PayLogic in parallel during testing?
- Yes. Functions and Scripts run independently. Use the overlap to verify PayLogic's output matches your Scripts' output, then disable Scripts in Script Editor once you're confident. After June 30 the parallel period ends automatically.
- What if my Scripts have custom Ruby logic the importer doesn't recognize?
- PayLogic's templates cover the ~95% of payment Scripts that follow common patterns. For genuinely custom logic (e.g., calling an external API mid-script), PayLogic's rule engine supports AND/OR composition across all conditions, which handles most edge cases. For the truly bespoke 5%, you'd write a custom Function — but those merchants typically already have engineering resources.
- Do my rules survive if I uninstall PayLogic?
- Rule configuration is stored in Shopify metafields tied to your shop, so uninstalling and reinstalling preserves your rules. Uninstalling stops the Function from executing — if you uninstall before June 30 with Scripts still active, Scripts continues to apply.
- What about shipping customization or discount Scripts?
- The June 30 deadline applies to all Scripts, not just payment Scripts. PayLogic only covers the payment side. For shipping customization, look at apps in the "Shipping methods" category; for discount Scripts, look at the "Discounts" category. PayLogic's roadmap may add shipping in V2 — for now, focus on the payment migration.
- I'm not on Shopify Plus. Does this affect me?
- If you used Script Editor, you're on Plus (Script Editor was Plus-only). Non-Plus merchants weren't able to use Scripts in the first place, so this deprecation doesn't affect them.
- I'm a Shopify Partner building stores for clients. How does pricing work across client stores?
- The Free Development plan applies on any Shopify Partner development store, so you can install and test PayLogic on every client project at no cost. When the client store transitions to production, the client picks a paid plan. There's no per-partner license — each client store has its own subscription.
Migrate before June 30.
Free on dev stores. $1.99/month on production. 10 minutes to install and import.
Install PayLogic on the App Store