Every e-commerce store faces the same recurring nightmare: a customer emails to report their package was lost by the carrier, or arrived damaged, or was stolen from their doorstep. Your carrier absolves themselves of liability. You’re left choosing between issuing a full refund (absorbing the entire cost) or telling the customer to deal with it (losing them forever). Neither option is good — and both represent pure financial losses that were preventable.

ShippingGuard’s Shipping Protection module solves this problem elegantly by offering customer-funded shipping insurance at checkout. Customers opt in (or are automatically enrolled) for a small protection fee — and in exchange, they’re covered for lost, damaged, or stolen parcels. Your store collects the fees, manages claims through a professional centralized dashboard, and pays out only on legitimate claims. For most stores with reasonable loss rates, this creates a net-positive revenue line from shipping logistics — making ShippingGuard one of the most financially impactful woocommerce shipping plugins you can install.

Why Every WooCommerce Store Needs Shipping Protection

The numbers behind shipping loss are significant:

• Industry estimates suggest 1-5% of domestic packages are lost, damaged, or stolen
• The average e-commerce order value for US stores is $80-$100
• Without protection, a 2% loss rate on a store doing $50,000/month in sales means $1,000/month in pure shipping loss costs
• Carrier insurance is expensive, has high deductibles, and requires complex filing processes

With ShippingGuard’s Shipping Protection module:

• Customers with protection pay the fee at checkout (e.g., $2.99 fixed or 2% of order)
• If their order is lost or damaged, they submit a claim — you review and approve it
• You cover the cost of the claim from the collected protection fees
• Customers without protection who experience loss — the resolution is at your discretion, as they declined protection

For a store with $50,000/month in orders and 80% protection adoption at $2.99/order (average 15 orders/day = 450 orders/month): you collect approximately $1,345/month in protection fees. Even if you approve $600/month in claims, you net $745/month — while providing a significantly improved customer experience for claim resolution.

How Shipping Protection Works at Checkout

ShippingGuard displays a premium protection card at checkout — either before the order submit button (on the checkout page) or in the cart totals area (on the cart page). The card shows:

• Protection icon (customizable — defaults to a shield SVG with a checkmark)
• Protection name (customizable — defaults to “Shipping Protection”)
• Checkout label / subtitle (customizable description text)
• Protection fee amount calculated dynamically from cart total
• Toggle checkbox — defaults to enabled (customers must opt out)

The default-on behavior is a critical UX decision that significantly increases protection adoption. Customers who actively want protection don’t need to do anything — it’s already selected. Only customers who actively choose to decline will uncheck the box.

When a customer toggles the protection checkbox, a nonce-verified AJAX call updates their WooCommerce session (shippingguard_fee_enabled). The cart/checkout totals refresh via WooCommerce’s standard update mechanism, showing the fee added or removed in real time. On order completion, the protection status and fee amount are saved to the wp_shippingguard_orders database table along with the order ID.

Three Protection Pricing Models

1. Fixed Fee

A flat dollar amount per order, regardless of cart total. Simple and predictable for customers. Best for stores with consistent order values.

2. Percentage with Maximum Cap

A percentage of the cart subtotal, with a configurable maximum cap to prevent the fee from becoming unreasonably large for high-value orders. Scales naturally with order risk — higher-value orders have higher protection fees.

3. Tiered Pricing Rules

Define custom fee amounts for cart total ranges. Maximum flexibility for stores that want specific rates at specific price points. Tiers are evaluated in order — the first matching range applies.

Checkout Widget Customization

The protection card appearance is fully customizable through ShippingGuard settings:

• Protection Name: The main title of the protection card (e.g., “Package Insurance”, “Order Guard”, “Delivery Protection”)
• Checkout Label: A subtitle description below the name (e.g., “Protect your order against loss, damage, and theft”)
• Custom Icon: Upload your own icon image — or use the default green shield SVG with checkmark
• Visibility Control: Show on cart page, checkout page, or both

Matching the protection card to your brand identity significantly increases trust and adoption rates compared to generic third-party insurance widgets.

Smart Exclusion Rules

ShippingGuard automatically hides the protection option — and disables the fee — when it doesn’t apply to the current cart:

• Digital/Downloadable Products: Auto-exclude carts containing only virtual or downloadable products (configurable — on by default)
• Specific Products: Exclude specific product IDs — if any excluded product is in cart, protection is hidden
• Specific Categories: Exclude entire product categories from protection eligibility, with full category hierarchy support (excludes subcategories of excluded parent categories too)
• Minimum Order Amount: Only show protection for orders above a minimum cart total — avoid offering $2.99 protection on a $5 order

Customer Claims Submission Flow

Customers with protected orders access the claims system through a dedicated “My Claims” tab in their WooCommerce My Account area (added automatically by ShippingGuard via a rewrite endpoint). The claim submission form includes:

1. Order selector — dropdown of the customer’s eligible protected orders
2. Claim reason — Lost / Damaged / Stolen
3. Photo upload — optional photo attachment for damage claims
4. Submit button — claims are saved with Pending status via the REST API (POST /shippingguard/v1/claims/submit)

After submission, the customer sees their claim history with current status (Pending / Approved / Rejected) in the My Claims tab. They receive email notifications at each status change.

Admin Claims Dashboard

The ShippingGuard Claims Center (under the ShippingGuard admin menu) is a professional claims management interface showing all claims from all customers with:

• Claim summary statistics: Total, Approved, Rejected, Pending counts at a glance
• Claim details: Order number, customer name/email, claim reason, submission date
• Photo review: View uploaded damage photos directly in the dashboard
• One-click status update: Approve or Reject each claim with a single click — updates claim status via PUT /shippingguard/v1/claims/{id} and triggers email notifications
• Status filtering: Filter claim list by status to focus on Pending claims needing review

The Claims Dashboard data is fetched from the wp_shippingguard_claims custom database table via REST API, rendered in a React component for instant filtering and status updates without page reloads.

Automated Email Notifications

ShippingGuard’s email engine (handled by ShippingGuard_Emails) sends automated notifications at key events:

• Claim Submitted: Admin notification when a new claim is submitted by a customer
• Claim Approved: Customer notification when their claim is approved, including next steps for resolution
• Claim Rejected: Customer notification when their claim is rejected

All emails use WordPress’ standard wp_mail() system and are compatible with SMTP plugins and WooCommerce email template overrides.

Protection Economics: How It Benefits Your Store

The financial model of shipping protection is straightforward: you collect fees from opted-in customers, and you pay out claims to those with legitimate losses. The key metrics to model:

Beyond the direct financial model, protection also reduces customer service volume — customers with protection have a clear, defined resolution path (claim submission), reducing the ambiguity and frustration of unprotected loss scenarios.

FAQ