Blog / Guide
How package protection works, and why owning it pays
Every store that ships enough orders ends up with a few that go missing, arrive crushed or disappear off a porch. The usual fix is to add a package protection app at checkout, collect a small fee, and let the provider deal with claims. It works. But before you sign up, it helps to look at who keeps the money, who talks to your customer when something goes wrong, and what that does to the next order.
How third-party protection usually works
The setup is simple. At checkout, the shopper sees an option to protect their order for a dollar or two, or a small percentage of the cart. Most say yes. The fee goes to the protection company, not to you.
When a package goes wrong, the customer files a claim with the provider. Depending on the provider, that can mean a form, photos, sometimes a police report, and then a wait. If the claim is approved, the provider pays for the refund or reshipment. Either way, the provider keeps every fee it collected, including the ones on orders that arrived fine.
Follow the money
A protection company makes money on the gap between fees collected and claims paid. Here’s a simple example for a store doing 10,000 orders a month:
| Metric | Example |
|---|---|
| Average order value | $100 |
| Protection fee (2%) | $2 |
| Orders that buy protection | 6,000 (60% of 10,000 orders a month) |
| Fees collected | $12,000 a month |
| Claims filed | 120 (2% of protected orders) |
| Average claim cost | $75 (product plus shipping) |
| Claims approved | 96 (80%), costing $7,200 |
| Left over for the provider | $4,800 a month |
Now push the numbers a little. If 5 to 7% of protected orders file a claim and almost all of them get approved, the same program starts losing money. No company runs at a loss for long, so the business only works if payouts stay low. In practice that means more denials, more steps in the claim form, or a process slow enough that some customers give up.
That doesn’t make these companies bad. It just means their goal and yours aren’t the same. You want the customer fixed up quickly so they order again. They need claims to stay small.
It starts after the customer is already upset
Most programs wait for the customer to notice the problem and file the claim. So the first thing your customer experiences is a missing package, and the second is paperwork. Even if a third party runs the claim, the customer remembers your brand.
What third-party protection does well
To be fair, there are real reasons stores use these services:
- The provider can take order-issue tickets off your plate.
- Shoppers get some reassurance at checkout.
Those are worth something. The question is whether they’re worth the fee revenue, control over the outcome, and a claims experience that isn’t yours.
Running protection yourself
The alternative is to run protection as your own program. The fee is added at checkout under your name and paid to your store like any other line on the order. When something goes wrong, you decide what the customer gets. The fees you collect become a fund for fixing shipping problems quickly, instead of revenue that leaves the business.
The obvious worry is the work: if the provider isn’t handling those tickets, your team is. That’s the part OrderCtrl is built to make easy.
How OrderCtrl handles it
OrderCtrl’s package protection adds the option to your WooCommerce checkout with your own name and pricing: a flat fee, a percentage, a percentage with a minimum, or tiers by cart value. OrderCtrl doesn’t take a cut of the fee. Here’s how the rest fits together.
Problems get caught before the customer writes in
OrderCtrl tracks every shipment against your delivery promises and flags packages that are lost, damaged or have stopped moving. An automation can open a claim for your team, approve it on the spot, or email the customer and let them pick a replacement or a refund.
Customers report the rest in your portal
For problems tracking can’t see, customers report them in your branded portal with photos. Your rules can approve the simple ones right away and send the unusual ones to your team.
Your rules decide who gets what
Claim policies can look at whether the order was protected, its value, the product, the carrier, and the customer’s order and return history. A protected order from a loyal customer can be approved instantly, while a large claim from a brand-new account waits for a person.
Your agents get the whole story in their helpdesk
OrderCtrl doesn’t answer tickets for you, but it means your team rarely has to dig. An OrderCtrl card sits inside Gorgias, Zendesk, Help Scout, Freshdesk, Gladly, Kustomer, Re:amaze and Richpanel, next to the ticket. Agents see the customer’s orders, every box and its latest scan, open and recent claims, and which fixes your policy allows for the problem in the ticket, with a link to start the claim. Through the OrderCtrl API, it can also draft a reply from that context for the agent to send as is or edit. Your newest agent can give the same answer as your most experienced one, in a fraction of the time.
What you get out of it
- The fees stay with you and help cover the cost of claims.
- Fewer surprises. Stuck and lost packages get flagged before customers have to chase you.
- Fast, consistent answers. Rules handle the routine claims, and agents have the context and a draft reply for the rest.
- One experience. Tracking, claims and fixes all happen in your branded portal, not someone else’s.
Bottom line
Shipping problems will happen no matter what you do. What customers remember is how quickly you made it right. Third-party protection can work, but you hand over the fee and the conversation. Running your own program keeps both, and with the right tools it doesn’t have to mean more work for your team.