Wix Package Insurance: How to Automate Coverage

A merchant searching for “Wix package insurance” generally starts with an implicit assumption: that the platform offers coverage, just as Shopify does with its built-in insurance. That is not the case. Wix does not offer any native package insurance, and this absence is not an oversight in the documentation—it is structural.

This observation has a direct consequence. On a Wix store, the value of goods in transit is covered by nothing other than the liability of the Carrier, which provides compensation based on weight rather than value. This guide explains what Wix actually covers, what this lack of coverage means for a European merchant, what options are available, and how to automate coverage on the platform.

What Wix Actually Offers in Terms of Shipping

Wix offers a native shipping solution, Wix Shipping, launched in partnership with Shippo. It allows you to purchase and print shipping labels, manage returns, and compare carrier rates right from the dashboard.

This scope pertains to logistics, not insurance. Wix Shipping does not include any coverage for the value of the goods. The available protection options are provided either by the carriers themselves or by third-party apps installed from the Wix App Market.

It is important to understand this difference in business models, because it explains why there is no answer to the question “What is Wix’s package insurance?”: unlike other platforms that include coverage by default, Wix has opted for an open ecosystem where insurance is provided by a third-party service and is the merchant’s responsibility.

A market that's bigger than it seems

It is worth noting the order of magnitude, with a methodological caveat. Market trackers do not agree: depending on the counting method, estimates range from around 980,000 active Wix stores on one hand to more than four million sites using Wix Stores on the other. These discrepancies stem from the criteria used (active store, detected technology, published site), and none of these figures is incorrect in and of itself.

What is more consistent is the geographic distribution. After the United States, Wix’s main markets are in Europe: the United Kingdom, Germany, France, Switzerland, Italy, the Netherlands, Belgium, Austria, and Spain. In other words, a significant portion of the merchants in question ship under European liability regimes, the Limits of which are detailed below.

What the Lack of Built-in Insurance Means in Practice

The risk of transit rests with the merchant

In distance sales to consumers in the European Union, the risk of loss or damage to goods during transit rests with the seller until the goods are actually delivered to the consumer. A package lost between the warehouse and the customer is therefore not a problem that the customer has to bear: it is the merchant who must issue a refund or reship the item, and then seek reimbursement from the Carrier.

It is this asymmetry that makes the issue of coverage so critical. Without package insurance, every shipment represents a net exposure on the merchant's balance sheet.

Carrier's liability is based on weight

In the absence of specific coverage, the only recourse is the liability of the Carrier. This liability is presumed, which provides protection, but it is capped based on weight, regardless of the value of the goods.

The SDR (Special Drawing Right) is a unit of account used by the International Monetary Fund, and its value fluctuates. Only SDR amounts are considered official; euro equivalents are for informational purposes only. National regulations vary from one European country to another: the French standard contract is provided for illustrative purposes only, and each merchant must verify the applicable regulations in their country of shipment as well as the terms and conditions on their delivery company.

The result is inevitable. For a package with a high value-to-weight ratio, the capped indemnity covers only a fraction of the loss. A piece of jewelry weighing a few dozen grams, an electronic component, a designer item—in all these cases, the carrier’s liability leaves a considerable gap. We explain this mechanism in detail in our guide to cargo insurance.

Grounds for Exemption

Furthermore, the carrier’s liability is not automatic. The seller may be relieved of liability if it establishes fault on the part of the buyer, an inherent defect in the goods, circumstances that it could not avoid, or missing or defective packaging. In practice, this last ground is the most common reason for refusing to pay compensation under the contract.

The options actually available to a Wix merchant

There are three options, each with its own rationale and limitations. None is universally superior: the choice depends on the value of the shipments.

The declaration of value with Carrier. It sets the compensation li Limit in exchange for an additional fee. It’s simple, available from all carriers, and sufficient for routine shipments. Its limitation stems from its nature: it remains within the scope of the liability regime set forth at Carrier, and is therefore subject to the same grounds for exemption, the same category exclusions, and the same claim deadlines. It increases the Limit, but does not guarantee compensation. Valuable items (watches, jewelry, art) are, in fact, frequently excluded or subject to very low coverage limits in the carriers’ terms and conditions.

An app from the Wix App Market. Several shipping protection apps are available on the Wix App Market. Installation is simple and integrated into the platform. There are two points worth checking before committing. First, many of these solutions are based on a North American model where protection is offered as a paid option to the end customer at checkout—an approach that does not align well with European distance selling law, under which the seller bears the transit risk. Second, it’s important to verify who bears the risk, what the per- Limit s are, and which categories are excluded—factors that vary significantly from one application to another.

Property insurance purchased from a third party. This is a property insurance policy that is independent of the Carrier : it compensates for property damage based on the insured value, without requiring a determination of the Carrier ’s liability. It therefore covers situations in which the is exempt from liability and applies regardless of the Carrier used. The trade-off is that it requires a separate policy, which means an additional step that needs to be automated. This is the principle ofad valorem insurance, the workings of which we detail in a dedicated guide.

The decision criterion is the same in all three cases: compare the capped compensation you would receive (weight in kilograms multiplied by the mode cap) to the actual value of your shipments. As long as the two amounts are close, the standard plan is sufficient, and there is nothing more to consider. As soon as the gap widens, the question becomes a serious one.

Automating Coverage on Wix: Backend Event Integration

This is where the innovation lies, and it deserves a detailed explanation precisely because it differs from the traditional implementation model.

Claisy is not available on the Wix App Market. Integration is handled through a Velo backend event—the development layer built into Wix. Specifically, an event handler is added to your site: when an order changes to "shipped" status and a tracking number is recorded, the event is automatically triggered and sends the order, which activates coverage without any manual intervention.

The decision to use this event—rather than a trigger based on the order—is not insignificant. At the time the order is placed, neither the Carrier nor the tracking number is known. By linking to the shipping update, the integration has the information needed to track the package from the very first call.

What that really means, honestly

This method requires no programming skills: all you have to do is copy a provided code snippet and paste it in the right place. But it’s not a one-click installation, and it would be misleading to present it that way. Three conditions must be met:

• Your site must have an active Wix Stores shop, which requires a suitable paid plan;
• Developer mode must be enabled on the site;
• The site must be published; the code never runs in Preview mode.

Allow about ten minutes for the initial setup. On the other hand, the integration is invisible to your customers, has no impact on the checkout process, and requires no further maintenance.

Universal Shipping Coverage for All Carriers

Claisy Works With All Carriers

Unlike marketplace modules, which are sometimes limited to certain carriers, Claisy automatically covers all your shipments regardless of the carrier:

import { fetch } from 'wix-fetch';
import { orders } from 'wix-ecom-backend';
import { elevate } from 'wix-auth';

export async function wixEcom_onFulfillmentsUpdated(event) {
  const getOrder = elevate(orders.getOrder);
  const order = await getOrder(event.entity.orderId);
  
  await fetch('https://api.claisy.com/functions/v1/wix-webhook', {
    method: 'post',
    headers: {
      'Content-Type': 'application/json',
      'api-key': 'VOTRE_CLE_API',
    },
    body: JSON.stringify({ event, order }),
  });
}

Technical Considerations

Keep your API key confidential. It identifies your account. The backend files of a Wix site are not accessible to visitors, but the key can be read by anyone with access to your site’s editor. Treat it like a password, and change it if it has been shared.

The events.js file is shared. Other extensions or developments may have added event handlers to it. Overwriting it may break existing features on your site.

Preview mode does not trigger anything. This is the most common cause of a failed test: the code runs only on the published version.

Insurance must be arranged before the goods are delivered to Carrier. Regardless of the solution chosen, goods that have already been entrusted to Carrier cannot be covered retroactively: the risk has already begun. This is why automating the process at the time of shipment is preferable to a manual declaration made after the fact, which is often overlooked.

Sources

• Wix Launches Wix Shipping in Partnership with Shippo: https://www.prnewswire.com/news-releases/wix-launches-wix-shipping-a-native-solution-powered-by-shippo-to-provide-faster-cheaper-and-more-reliable-delivery-301814594.html
• Wix Developers, Velo documentation, and backend events: https://dev.wix.com/docs/build-apps/develop-your-app/api-integrations/events-and-webhooks/about-webhooks
• CMR Convention, Articles 17, 23, and 24
• Montreal Convention, Revision of Liability Limits as of December 28, 2024, ICAO: https://www.icao.int/news/international-air-travel-liability-limits-set-increase-enhancing-customer-compensation-0
• CIM (COTIF) Rules, Article 30, Section 2, CIT-Rail: https://cit-rail.org/en/freight-traffic/case-law-old/
• General Standard Contract, Decree No. 2017-461 of March 31, 2017, Légifrance: https://www.legifrance.gouv.fr/jorf/id/JORFTEXT000034330431
• Breakdown and volume of Wix stores: StoreLeads (https://storeleads.app/reports/wix) and BuiltWith (https://trends.builtwith.com/shop/Wix-Stores), distinct methodologies