Build or Buy Free-Shipping Thresholds & Logic on Shopify?
Free shipping thresholds and logic are a BUILD once rules pass one storewide bar: a $3,000–$12,000 Functions build (Deploi estimate, illustrative) encodes exclusions, market splits, and member gating as code you own. Native settings ship the simple threshold free on every plan, and Scripts, the old Plus home for this logic, stopped executing June 30, 2026. Buy a rules app only when marketing must change thresholds monthly without a deploy.
Your profile — see how the verdict shifts
- Confidence
- High — Scripts' shutdown settled the surface question: Functions are the sanctioned home, the scope is small, and lock-in is low
- Reference scenario
- $20M–$100M GMV · multi-market shipping · agency dev bench
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under $2M revenue | WAIT | A price-based free shipping rate plus a free-shipping discount covers one threshold, included with the plan. Spend nothing here. |
| $2M – $15M | DEPENDS | One threshold for everyone still fits native settings; the first SKU exclusion or market split starts the Function conversation. |
| $15M – $75M | BUILD | Exclusions, market-specific bars, and member gating are margin policy — a one-time Function beats renting checkboxes that almost fit. |
| $75M+ | BUILD | Multi-market thresholds and subsidy governance at this volume demand rules that run in-checkout, versioned and testable like the code they are. |
What Free shipping thresholds & logic Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | A well-placed threshold lifts AOV mechanically: shoppers add items to clear the visible bar, and the subsidy math is yours to tune per market. |
| Customer experience | High | Free shipping is the checkout expectation shoppers name most, and a clear, honest threshold removes the surprise-cost moment that kills orders. |
| Operational efficiency | Medium | Rules as code end the promo-week scramble of hand-toggling shipping settings across profiles and markets. |
| Data & insight | Medium | Threshold experiments keyed to AOV and contribution margin show what the subsidy buys — the evidence finance keeps asking for. |
Spend ceiling: Free shipping is a margin lever wearing a UX costume: the real spend is the subsidy itself. Keep the rules layer in the low four figures and put the serious money into threshold experiments.
What buying enables (top apps)
- + A rules UI marketing changes without a deploy
- + Preset exclusion and zone patterns proven across many stores
- + Fast seasonal toggles — thresholds up for promo, back down after
What building additionally unlocks
- + Threshold policy no checkbox expresses: SKU and collection exclusions, member-only offers, market-specific bars, post-discount subtotals
- + In-checkout evaluation with no network hop, so the rule can't slow checkout or fail open mid-promo
- + One policy source feeding storefront messaging and checkout behavior consistently
- + No subscription for logic that changes twice a year
Find Your Verdict in 3 Questions
Does one storewide threshold with no exceptions describe your offer?
Yes: Your verdict: WAIT — a price-based free shipping rate plus a free-shipping discount ships it today, included with your plan.
No: Go to question 2.
Did the threshold logic live in a Shopify Script before June 30, 2026?
Yes: Your verdict: BUILD — the script is dark; rebuild the rules as Functions now, before promo season finds the gap.
No: Go to question 3.
Do exclusions, markets, or member rules change monthly, run by marketing?
Yes: Your verdict: BUY — a rules app gives marketing the UI; verify it runs on Functions, not legacy surfaces,.
No: Your verdict: BUILD — a one-time Function encodes the policy and retires the subscription.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A rules app configures in a day; the Function build runs an estimated 1–3 weeks including edge-case testing (Deploi estimate, illustrative). | ||
| Recurring fees | Rules apps bill monthly for logic most stores change twice a year; a shipped Function costs nothing per month. | ||
| Maintenance & upgrades | Vendors track platform changes for you; the Function needs a redeploy on the ~6-month API cycle and a pre-peak test. | ||
| Switching & exit | Threshold rules re-enter quickly on either side; native settings keep covering the simple case the day anything is turned off. | ||
| Risk | |||
| Vendor risk | Shipping-discount apps are a thin category with regular churn; a Function depends only on Shopify's own runtime. | ||
| Security & compliance surface | Modest data either way; owned code still means one less vendor reading cart contents. | ||
| Platform-deprecation exposure | Scripts-era threshold logic died June 30, 2026; Functions are the surface Shopify sanctions, and apps must ride it too. | ||
| Value | |||
| Fit to requirement | Rule builders cap at their checkboxes; a Function encodes your exclusions, market bars, and stacking policy exactly. | ||
| Time to market | Today versus a couple of weeks; buy wins a promo already on the calendar. | ||
| Performance & scale | Functions evaluate in-checkout with no network hop, so the rule can't slow checkout or fail open mid-promo. | ||
| Data ownership & AI-readiness | Owned policy plus order data keys threshold experiments to AOV and contribution margin — the analysis that justifies the subsidy. | ||
| Focus & opportunity cost | The scope is a week or two of focused work — small enough that the opportunity-cost argument barely applies. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Native free-shipping settings | Native — Price-based free shipping rates per zone plus free-shipping discounts with minimums, included on all plans (July 2026 research) | Included with your Shopify plan | One storewide threshold with no exceptions |
| Shipping-discount apps (category) | Category — Shortlist; confirm each runs on Functions, not script-era surfaces | $10–$80/mo bands (illustrative) | A rules UI marketing can change without a deploy |
| Delivery & shipping-discount Functions | Build lane — This page's build path: your threshold policy as code | One-time $3,000–$12,000 (Deploi estimate, illustrative) | Exclusions, market splits, and member gating no checkbox expresses |
The Build Path
- Shipping-discount Function: Grants the free-shipping subsidy by rule — subtotal bars, collection and SKU exclusions, member checks, post-discount subtotals.
- Delivery customization Function: Shapes what shoppers see once the bar is met: hide paid rates, rename options, keep the picker honest per market.
- Policy spec + storefront messaging: One documented rulebook feeds the Function and the theme, so the storefront promises exactly what checkout enforces.
- Effort band
- $3,000–$12,000 one-time (Deploi estimate, illustrative) — at or below the $10–25K contact-form band floor
- Typical timeline
- 1–3 weeks including edge-case testing (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): a redeploy on the ~6-month API cycle and a test pass before each peak season.
- What you own — and what you take on
- You own: the threshold policy, the exclusion lists, the market rules, and the margin analysis they feed. You take on: edge-case discipline — discounts, gift cards, and currency rounding all touch the bar.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $100–$800 | $3,000–$12,000 |
| Years 1–3 (recurring) | $360–$2,900 | $1,500–$6,000 (maintenance) |
| 3-year total | ≈$460–$3,700 | ≈$4,500–$18,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy path: light rules-app tier held flat across the horizon.
- † Build path: both Function classes plus policy spec and testing; three-year horizon.
What the Sticker Price Hides
On the buy path
- — A monthly fee for logic that changes twice a year is the quiet overpay (community-reported pattern)
- — Anything still leaning on script-era behavior died June 30, 2026 — verify the execution surface before paying
- — Rule builders cap at their checkboxes; the first genuinely custom condition sends you to Functions anyway
On the build path
- — Threshold edge cases multiply: discounts at the bar, gift cards, multi-currency rounding — spec them before coding
- — Hiding a paid rate and granting the subsidy are different Function classes; scope both halves
- — The theme must tell shoppers the rule — checkout enforcing what the storefront never said breeds support tickets
- — ~15–20% of build cost per year in upkeep (Deploi estimate)
What Merchants Say
Scripts-deadline anxiety ran hot through 2026 — Plus stores that carried threshold logic in Ruby for years describing the scramble to rebuild before the shutoff.
The recurring rules-app complaint: the checkbox matrix almost fits, and 'almost' surfaces mid-promo as free shipping on the one collection it should never touch.
If You Change Your Mind Later
If you bought and outgrow it
Threshold rules re-enter quickly, so app exit is mostly painless: record the rule matrix, confirm nothing script-era lingers, and rebuild in native settings or a Function. The offer your customers learned is the continuity that matters — keep the bar itself stable through the switch.
If you built and want out
Functions retire cleanly: native settings resume covering the simple case the day you turn custom logic off. The policy spec and margin data stay yours, and any future app starts from a documented rulebook.
When This Answer Changes
We're watching for:
- ▸ Native discount and shipping settings absorbing more rule types — check the changelog quarterly; each one shrinks the build
- ▸ Functions gaining richer cart and buyer inputs
Verdict change log:
- 2026-06-30While the Ruby ran, keeping it was free and rational. The hard stop ended that: threshold exceptions that lived in Scripts need a new home, and the sanctioned one is Functions. Legacy checkout scripts follow on August 26, 2026.
Common Questions
What free-shipping rules does Shopify cover natively?
Native settings cover the simple case: a price-based free shipping rate above a subtotal, per shipping zone, plus free-shipping discount codes and automatic discounts with a minimum purchase. Included on every plan. The gaps appear at exceptions — excluding oversized SKUs, splitting thresholds by market, gating the offer to members, or counting subtotals after discounts. Those rules take a Function — an estimated 1–3 week build (Deploi estimate, illustrative) — or an app.
How do you set the right free-shipping threshold?
Set the threshold just above your current average order value — a common starting rule places it 15–30% higher, then lets the data adjust it (illustrative heuristic, not a quote). The mechanism: shoppers add items to clear a visible bar, so AOV rises while the shipping subsidy eats part of the gain. Run the math on contribution margin per market, and revisit quarterly; the threshold is a lever, not a setting.
What replaced Scripts for free-shipping logic on Plus?
Shopify Functions replaced Scripts: threshold logic that hid, renamed, or adjusted shipping rates in Ruby stopped executing June 30, 2026, and legacy checkout scripts are removed August 26, 2026. The rebuilt version runs as delivery and shipping-discount Functions — in-checkout, no network hop — for an estimated $3,000–$12,000 one-time (Deploi estimate, illustrative). Stores that never used Scripts feel nothing; their native settings keep working.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Write the policy spec first: thresholds, exclusions, markets, member rules, discount interactions
- Scope both Function classes — shaping delivery options and granting the subsidy
- Mirror the rule in storefront messaging so checkout never surprises anyone
- Test the edges before peak: discounts at the bar, gift cards, multi-currency rounding
- Review threshold economics quarterly against AOV and contribution margin
If you're going with BUY
- Verify the app runs on Functions — script-era surfaces died June 30, 2026
- Recreate your exact exclusion list in a trial before paying
- Check per-market threshold support; many rule builders assume one market
- Diary a re-decision when rules stabilize — stable logic is a build, not a fee
Official Docs & Sources
- Combining discounts — Shopify Help Center
- About discounts — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy B2B Tiered & Volume Pricing on Shopify?
Building B2B tiered pricing as a Function over native catalogs wins for mid-market wholesale; wait if three catalogs cover you.
Should You Build or Buy BOGO Automation on Shopify?
Building BOGO logic on Shopify Functions wins once your offers outgrow native Buy X Get Y discounts.
Should You Build or Buy Discount Stacking Rules on Shopify?
Customizing wins for discount stacking on Shopify: native combinations cover the common matrix, and a Functions policy layer protects the margin.
Build or Buy Bulk Discount Code Generation on Shopify?
Bulk discount code generation is the cleanest BUILD in the discounts stack: a one-time script replaces a subscription that wraps the same API.
Should You Build or Buy Volume & Tiered Bundle Pricing on Shopify?
Building volume-tiered bundle pricing on Shopify Functions wins for mid-market stores with any dev capacity; buy only for speed.
Ready to run free shipping as policy, not a plugin?
Your threshold is margin policy. We spec the rules, build the Functions, and make the storefront promise exactly what checkout enforces.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.