What a Founder Should Know Before Turning On Shipping Guarantee Revenue

Most founders think about shipping guarantee as an insurance product they have to buy, when it is actually structured as revenue they get to keep. That framing mistake costs more than a missed opportunity. It means the economics never make it onto the founder's spreadsheet at all.

Before turning on shipping guarantee at checkout, a founder should model it the way they would model any new revenue line: attach rate, payout rate, margin, and the trust dividend that comes from keeping the entire experience inside their own store.

The revenue is structured differently than most founders assume

In the shipping guarantee model, the merchant collects a small fee from customers who opt in at checkout. That fee is the merchant's revenue, not a pass-through to an insurer.

The merchant only pays out when a customer files a resolution for a package that is actually lost, damaged, or stolen in transit. Because those events are a small share of total orders, the merchant keeps the large majority of what customers pay for the guarantee.

This is the part founders miss when they lump shipping guarantee in with shipping costs on a P&L. It behaves nothing like a cost center. It behaves like a high-margin add-on, closer to an extended service upsell than a carrier expense.

Model your attach rate first

Attach rate is the share of checkouts where a customer opts in to the guarantee. This is the first number to estimate before turning anything on, because every other number in the model scales off of it.

Attach rate depends heavily on how the offer is presented at checkout: default-on with an easy opt-out typically drives meaningfully higher attach than an unchecked opt-in box. Price point matters too. A guarantee fee that feels proportional to order value will convert better than a flat fee that feels arbitrary on a low-cost order.

Do not guess this number from a vendor's best-case marketing example. Ask what attach rate similar stores in your vertical and price range actually see, and model your own revenue off a conservative version of that number for the first few months.

Model your resolution rate next

Resolution rate is the share of guarantee-covered orders where a customer actually files a resolution for a lost, damaged, or stolen package. This is the number that determines your payout side of the ledger.

Because actual loss and damage in transit is uncommon relative to total order volume, the resolution rate is typically a small fraction of guarantee-covered orders. This is exactly why the revenue is high margin: you are collecting a fee on every opted-in order but only paying out on the minority that need it.

Ask your vendor for their actual resolution rate benchmarks, broken out by shipping method and destination if possible. A founder who understands this number going in will not be surprised by the margin, and will not overestimate the payout risk when deciding whether to launch.

Do the margin math before you launch, not after

Once you have a reasonable attach rate and resolution rate estimate, the margin math is straightforward. Guarantee revenue collected, minus payouts on filed resolutions, minus any per-transaction vendor cost, equals net margin on the program.

Because this is revenue you did not have before, even a conservative estimate usually shows the program contributing positive margin from month one. That is a different proposition than most operational line items on your P&L, which start as costs and have to earn their way to breakeven.

Run this math before launch so you know what a "normal" month looks like. That way, if a month's payout rate runs higher than expected, you can look at the underlying cause instead of reacting to a number you never modeled in the first place.

The trust dividend nobody puts in the spreadsheet

The margin math is the easiest part of this decision to quantify. The harder part to quantify, but just as real, is what happens to customer trust when a resolution stays inside your own store instead of routing to a third party.

When a customer files a resolution and never leaves your site to do it, they experience your brand handling a problem well. That is a retention moment, not just a support ticket. When a customer gets redirected to an unfamiliar third-party claims portal, the moment becomes confusing at best and damaging to trust at worst.

Founders often weigh vendor options purely on fee percentage without factoring this in. A slightly higher take rate from a vendor that keeps everything branded and in-house can be worth more than a marginally cheaper vendor that sends your customers somewhere else at the exact moment they need reassurance.

Walk the model through a simple scenario

It helps to see the shape of this math even in rough form before you commit to real numbers. Say a meaningful share of your checkouts opt into the guarantee at a small flat fee. That fee, multiplied across a month of orders, becomes a new revenue line that did not exist before.

Now subtract payouts. Because only a small share of guarantee-covered orders ever turn into an actual lost, damaged, or stolen package resolution, the payout side of the ledger stays a fraction of the revenue side. Subtract any per-transaction cost from your vendor, and what is left is net program margin.

Run this scenario with your own store's order volume and your vendor's actual attach and resolution benchmarks, not industry averages pulled from a blog post. The shape of the math holds regardless of your specific numbers: revenue collected on volume, payouts on a minority of that volume, margin on the difference.

Do not confuse this with your existing shipping cost line

Founders sometimes fold shipping guarantee into the same mental bucket as shipping cost negotiation, carrier accounts, or fulfillment SLAs. Those are real levers too, and separately, tightening carrier rates or improving fulfillment speed can meaningfully cut costs elsewhere in the business.

But shipping guarantee revenue does not offset a cost you are already paying. It adds a new revenue line on top of whatever cost work you are already doing. Keep the two separate in your model so you can see the full picture: cost savings on one side, incremental high-margin revenue on the other.

What to actually decide before you flip the switch

Before turning on shipping guarantee revenue, a founder should be able to answer four questions with real numbers, not guesses.

What attach rate am I modeling, and is it based on comparable stores or wishful thinking? What resolution rate am I budgeting for, and does it match what my vendor sees across their book of business? What is my projected net margin in a normal month and in a bad month? And does the resolution experience stay inside my own store, or does it send my customers to a portal with someone else's name on it?

Get real answers to those four, and shipping guarantee stops being a checkout add-on you are not sure about. It becomes a modeled, high-margin revenue line with a customer trust benefit attached, and that is a much easier decision to make.

ShipAid's Shipping Guarantee lets merchants keep the guarantee revenue, resolve issues without sending customers off-site, and see the underlying attach and resolution numbers to model the program with confidence. See how the economics work for your store.