Route vs. Self-Insured Shipping Protection: Who Keeps the Spread?
Self-insured reorders beat buying Route past roughly 5,000 orders a month. A cart-transform Function charges your own protection fee, claims pay from the pool, and the spread over 1–2% typical loss rates stays on your P&L (illustrative math). Route wins when you want zero claims ops or real insurer backing on high-value shipments. Under 2,000 orders a month, charge nothing and reorder on goodwill.
Your profile — see how the verdict shifts
- Confidence
- High — Follows the parent shipping-protection verdict: the fee-minus-claims spread is mechanical at volume, and the app's genuine service is claims ops. Route model unverified (illustrative)
- Reference scenario
- $20M–$100M GMV · 8,000 orders/mo · agency dev bench · single storefront
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Under 2,000 orders/mo | WAIT | Claims are countable on one hand most months. Reorder on goodwill, charge nothing, and revisit when volume makes a pool statistical (illustrative math). |
| 2,000–5,000 orders/mo · lean support | DEPENDS | The pool works but claims ops is real; buy Route if support is already stretched, self-insure if a few claims a week fit the queue. |
| 5,000+ orders/mo · dev bench | BUILD | The parent verdict: a cart-transform Function charges your fee, claims pay from the pool, and the spread over 1–2% loss rates stays yours (illustrative math). |
| High-value or theft-prone mix | BUY | Real insurer backing earns it where single claims are large: jewelry-grade AOVs or porch-piracy-heavy metros can outrun a pool's variance. |
What Route vs. self-insured reorders (the no-app lane) Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Customer experience | High | A lost package handled with an instant reorder is a loyalty moment; the same package disputed for a week is a churn event. |
| Revenue — indirect | Medium | A protection option at checkout reassures first-time buyers in theft-prone metros, and the fee revenue itself funds the promise (illustrative math). |
| Operational efficiency | Medium | A claims runbook with reorder-first resolution keeps each case to minutes; without one, every lost package becomes a negotiation. |
| Data & insight | Medium | An owned loss ledger by carrier, lane, and metro shows where packages actually vanish and prices every future protection decision. |
Spend ceiling: Anchor spend to your loss line: at 1–2% typical loss rates (illustrative math), protection economics are a rounding error under 2,000 orders a month and a real P&L line past 5,000. Size the effort to the ledger, not the anxiety.
What buying enables (top apps)
- + Claims ops fully offloaded: intake, verification, and resolution run by the vendor
- + Insurer backing for high-value shipments a self-funded pool shouldn't absorb
- + A polished customer claims flow live in days
- + Package tracking bundled alongside protection
What building additionally unlocks
- + The fee-minus-claims spread stays on your P&L instead of a vendor's (illustrative math)
- + A checkout with no third-party widget on your highest-stakes page
- + Claims policy you control: reorder-first, no-questions thresholds, VIP handling
- + An owned loss ledger that prices carriers, lanes, and any future vendor pitch
Find Your Verdict in 3 Questions
Are you under roughly 2,000 orders a month?
Yes: Your verdict: WAIT — reorder on goodwill, charge nothing, and keep checkout clean; revisit at volume.
No: Go to question 2.
Can support absorb a few claims a week with a reorder-first runbook?
Yes: Go to question 3.
No: Your verdict: BUY — Route's zero-ops claims flow is the genuine service here.
Do high-value single shipments demand real insurer backing?
Yes: Your verdict: BUY — vendor backing exists for exactly this exposure.
No: Your verdict: BUILD — charge your own fee via a cart-transform Function and keep the spread (illustrative math).
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 | Route installs in days with the premium widget live at checkout; the self-insured Function build runs an estimated $10,000–$25,000 (Deploi estimate, illustrative). | ||
| Recurring fees | Premiums your shoppers pay flow to the vendor's side of the table (model varies); self-insured fees stay on your P&L and fund the claims pool. | ||
| Maintenance & upgrades | The vendor maintains widget and claims flow; the Function needs checkout API-version upkeep at ~15–20% of build cost per year (Deploi estimate). | ||
| Switching & exit | Removing Route means unwinding a customer-facing promise and open claims; your own fee and pool switch off with a deploy and a policy decision. | ||
| Risk | |||
| Vendor risk | Claims outcomes on your brand ride a vendor's policies and staffing; the no-app lane has no vendor at all. | ||
| Security & compliance surface | Route carries actual insurer backing where that matters; self-insurance needs wording discipline: sell a reorder guarantee, not regulated insurance, and get advice at scale. | ||
| Platform-deprecation exposure | Both lanes ride checkout surfaces: the widget rides checkout extensibility, and the Function is first-party Shopify Functions (July 2026 research). | ||
| Value | |||
| Fit to requirement | Route bundles claims UX and tracking; the Function charges exactly the fee you design, with policy rules you set. Different fits, both real. | ||
| Time to market | Days versus an estimated 4–8 weeks for the Function, pool accounting, and claims runbook (Deploi estimate, illustrative). | ||
| Performance & scale | A cart-transform Function runs server-side in checkout with no injected script; a widget adds a third-party surface to your highest-stakes page. | ||
| Data ownership & AI-readiness | Claims, loss rates, and premium revenue land in the vendor's dashboard; self-insured, the whole loss ledger is your data. | ||
| Focus & opportunity cost | Claims ops is real work someone must own; that ownership is the genuine service you buy, and the honest cost of the build lane. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Route | Live — The insurer-backed category's best-known name: customer-paid toggle, claims portal, and a claims desk you never staff | Customer-funded per-order fees in a $1–$5 band, revenue-share economics (illustrative) | Zero claims ops with insurer backing |
| Redo | Live — Newer entrant pairing returns with checkout-funded coverage | Shopper-funded coverage model rather than flat SaaS | Protection and returns in one shopper-funded package |
| Self-insured reorders (no-app lane) | Build lane — The lane head-to-heads hide: a cart-transform Function charges your fee, claims pay from the pool, and the spread stays on your P&L, per the parent shipping-protection decision | $10,000–$25,000 build (Deploi estimate, illustrative) | Keeping the fee-minus-claims spread at 5,000+ orders/mo |
The Build Path
- Charge nothing, reorder anyway (the quiet third lane): Skip the fee, bake 1–2% loss into margin (illustrative math), and reorder on claims as goodwill. Zero code, zero widget, and the checkout stays clean.
- Cart-transform Function + claims pool: A Function adds your protection fee as a checkout line you fully control: an estimated $10,000–$25,000 (Deploi estimate, illustrative). Fees accrue to a pool, claims pay from it, and the spread stays on your P&L.
- Claims runbook + Flow triage: A one-page claims policy, a Flow-tagged intake path, and reorder-first resolution keep claims ops to minutes per case (included tooling).
- Effort band
- $10,000–$25,000 for the Function, pool accounting, and claims runbook (Deploi estimate, illustrative) — lands in the $10–25K contact-form band
- Typical timeline
- 4–8 weeks including checkout testing and the claims runbook (Deploi estimate, illustrative); Route is live in days
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate), roughly $2,000–$5,000/yr (Deploi estimate, illustrative): checkout API version bumps and quarterly loss-rate reviews.
- What you own — and what you take on
- You own: the fee, the pool, the loss ledger, and every claims decision. You take on: claims ops in the support queue and the wording discipline of a guarantee that is not regulated insurance.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$1,000 (setup + widget QA) | $10,000–$25,000 (Function + runbook) |
| Years 1–3 (recurring) | $0–$3,600 merchant-side software | $6,000–$15,000 (maintenance + claims-ops time) |
| 3-year total | ≈$0–$4,600 software | ≈$16,000–$40,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Route column: shopper-paid premiums with merchant software cost held near zero (model varies); the foregone premium spread is the real economics, shown in the caption.
- † Build column: Function build plus claims-ops time; claims payouts excluded from both columns (both lanes pay for lost packages somehow); three-year horizon.
What the Sticker Price Hides
On the buy path
- — The premium your customers pay becomes the vendor's revenue line; at volume the foregone spread dwarfs any software fee (illustrative math)
- — Claims denials and slow payouts land on your brand, not the vendor's (community-reported theme for protection apps)
- — The checkout widget is a conversion variable on your highest-stakes page; test with it off, too
On the build path
- — Claims ops is real: intake, verification, and reorder logistics all land in support's queue
- — Loss-rate variance bites small pools; one porch-piracy wave in one metro can eat a quarter's spread (illustrative math)
- — Wording discipline matters: market a reorder guarantee, never insurance, and review the language before scaling it
What Merchants Say
Protection-app threads repeat one arc: merchants notice the premiums their customers pay would have covered claims several times over, then re-run the math on keeping the fee themselves.
The complaint shape on protection widgets: customers blame the store when a claim is denied or slow, and support ends up handling the ticket anyway.
If You Change Your Mind Later
If you bought and outgrow it
Leaving Route means resolving open claims under the old terms, removing the widget, and deciding same-day what replaces the promise: your own fee, or goodwill reorders. Customers who bought protection on past orders keep that coverage through its window, so overlap the transition and script support for it.
If you built and want out
The Function switches off with a deploy, and the pool is just your money: wind-down is a policy decision, not a migration. Honor the guarantee on orders that paid the fee through their delivery window. The loss ledger you accumulated stays yours and prices any future vendor conversation.
When This Answer Changes
We're watching for:
- ▸ Volume crossing roughly 5,000 orders/mo — the pool turns statistical and the BUILD math firms up (illustrative math)
- ▸ AOV or theft exposure climbing into insurer territory — single large claims are what vendor backing is actually for
- ▸ Route model or terms changing (verify quarterly; protection-app economics move)
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Is Route worth it for a mid-market Shopify store?
Route earns its place when you want zero claims ops or genuinely need insurer backing for high-value shipments. Past roughly 5,000 orders a month, the parent shipping-protection verdict flips to self-insuring: typical loss rates run 1–2% (illustrative math), so the premiums your customers pay usually exceed the claims they fund. The spread is the price of convenience.
How does self-insured shipping protection work on Shopify?
Self-insuring works in three moves: a cart-transform Function adds your own protection fee at checkout (an estimated $10,000–$25,000 build, Deploi estimate, illustrative), fees accrue to a claims pool, and support resolves claims reorder-first from a short runbook. At 1–2% typical loss rates (illustrative math), the pool covers claims with spread left over. Word it as a reorder guarantee, not insurance.
Can we just offer free reorders without charging a fee?
Yes, and under roughly 2,000 orders a month charging nothing is often the best lane: claims stay rare enough to reorder on goodwill and bake into margin (illustrative math). The checkout stays clean, no widget taxes conversion, and the customer story is simply generous. Add a fee, or an app, only when volume makes losses a steady statistical line rather than an occasional annoyance.
Your Next Steps
If you're going with BUILD(matches your selected profile)
- Pull 12 months of lost-and-damaged data and compute your real loss rate against the 1–2% envelope (illustrative math)
- Scope the cart-transform Function and fee logic: flat, tiered, or percentage (Deploi estimate, illustrative for the build)
- Write the one-page claims runbook: intake, verification, reorder-first resolution
- Word the offer as a reorder guarantee, not insurance, and review the language
- Review pool-versus-claims monthly for two quarters, then quarterly
If you're going with BUY
- Verify Route's current model, coverage terms, and claim SLAs before install
- A/B the widget's conversion impact with protection on and off
- Script support for claim-denial escalations; the brand risk stays yours
- Track premiums collected versus claims paid on your orders; that delta prices the build lane
- Diary a self-insurance re-check at 5,000 orders a month
Official Docs & Sources
- Checkout UI extensions — shopify.dev
- About product bundles — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Shipping Protection on Shopify?
Shipping protection is a self-insure build for most mid-market Shopify stores past roughly 5,000 orders a month.
Should You Build or Buy a Shipping Rules Engine on Shopify?
A shipping rules engine is a buy for most mid-market Shopify stores; build a custom carrier-service engine when mispriced rates become a measurable margin leak.
Should You Build or Buy Your 3PL Integration on Shopify?
3PL integration is a buy when your 3PL maintains a real Shopify connector; build custom Fulfillment-API middleware when the warehouse is bespoke or EDI-only.
Should You Build or Buy a Branded Tracking Page on Shopify?
Branded order-tracking pages are a build once orders clear roughly 5,000 a month.
Should You Build or Buy a Returns Portal on Shopify?
A returns portal splits by return economics: WAIT on native for simple flows, BUY exchange-first in the mid-market, BUILD at 3PL scale.
Ready to keep the protection spread?
We'll compute your real loss rate, build the cart-transform Function and claims runbook if the math says self-insure, and say so plainly if goodwill reorders or Route's zero-ops lane fits you better.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; Route's model here is illustrative 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.