WooCommerce free-shipping threshold: how to pick the right number

A free-shipping threshold is an economic rule, not a universal growth trick. It can make an existing shipping offer easier to understand, but it can also subsidise orders that would have happened anyway. No threshold or progress bar guarantees a higher average order value or conversion rate.

The useful question is therefore not “what multiple of AOV should I use?” It is: under which observed basket, margin and shipping conditions does this candidate threshold protect contribution?

1. Keep the WooCommerce method authoritative

WooCommerce core configures free shipping inside a shipping zone. The method can have no requirement, require a coupon, require a minimum amount, or combine amount and coupon conditions. It can also evaluate the minimum before or after a coupon discount. Review the current official free-shipping documentation before modelling a storefront message.

Write down one source-of-truth row for every active zone: currency, method, minimum amount, coupon requirement, before/after-discount policy, tax display and the address used for testing. If those rows do not share one economic threshold, a single global progress value is a poor fit.

2. Pull distributions, not only an average

Use a recent period that represents normal trading and collect:

1. Basket subtotal distribution, including percentiles and the number of orders near each candidate threshold.
2. Contribution by basket: revenue minus COGS, payment fees, discounts, returns provision and other variable costs.
3. Actual carrier cost by zone, method, weight and parcel profile—not the amount charged to the shopper.
4. Existing shipping revenue that would disappear when an order becomes eligible.
5. Coupon, tax and currency behavior matching the exact WooCommerce eligibility rule.

AOV alone hides the shape of the basket distribution. Two shops with the same AOV can have very different numbers of orders sitting €2, €10 or €30 below a candidate threshold.

3. Model sensitivity instead of inventing a lift rate

Pick a candidate threshold T. For each historical basket below T, calculate its gap G = T − subtotal. Then model at least four scenarios for the share of those baskets that might top up: 0%, 5%, 10% and 20%. These are sensitivity inputs, not claimed outcomes.

For each scenario, compare the incremental contribution from modelled top-up items with the carrier cost and shipping revenue absorbed across all newly free orders. Keep already-qualifying baskets separate: they can create subsidy cost without any top-up.

If the candidate is negative at 0% and remains negative under a modest response, reject it. If it works only under the 20% scenario, treat it as fragile until a controlled store test provides evidence.

4. Diagnose three common basket shapes

A narrow cluster just below the threshold

This is the scenario worth testing first. Measure whether the usual product mix contains credible add-ons that close the gap without creating disproportionate picking, returns or parcel costs. Do not assume that a €5 gap produces a €5 incremental sale.

Many orders already above the threshold

The rule may mainly give away shipping on orders that already convert. Quantify that existing-order subsidy before attributing any modeled top-up revenue to the program.

Thin contribution or highly variable carrier cost

A single threshold may be too blunt. Compare flat-rate, tiered or zone-specific shipping instead. If the viable amount differs by currency or destination, the checkout rule and storefront message need the same conditional model.

5. Visibility and eligibility are different jobs

A shopper-facing progress bar can expose the amount remaining on the product page, mini-cart, cart and checkout. It does not grant free shipping. The WooCommerce method selected for the customer address remains the source of truth.

Shipping Promise Booster 0.2.2 uses one manually configured numeric threshold and compares it with the cart subtotal. It does not read shipping-zone or method thresholds, and it does not maintain separate values by zone or currency. The merchant must keep the visible number aligned with the real method.

Before choosing the implementation, use the WooCommerce free-shipping progress buyer lab to reproduce the exact 0.2.2 calculation, inspect product-to-checkout scenes and check coupon, holiday, currency, theme and carrier boundaries. Then open the verified product experience for release, SHA-256, compatibility and purchase evidence.

6. Release as a measured hypothesis

1. Reproduce every zone, coupon and tax path on staging. The message and the actual free-shipping method must become eligible together.
2. Record a baseline: eligible sessions, cart subtotal distribution, checkout completion, contribution and carrier cost.
3. Roll out to a bounded audience or time window without changing other major cart mechanics at the same time.
4. Compare contribution, not only AOV. Segment new subsidy cost, top-up behavior and already-qualifying orders.
5. Recheck after carrier-rate, catalogue, coupon, tax, currency or zone changes. A manual display threshold is a second setting to maintain.

Bottom line

Choose a candidate from your basket and contribution distributions, model several response assumptions, and reject thresholds that depend on optimistic behavior. Keep WooCommerce eligibility authoritative, treat the storefront bar as a display layer, and measure the released result without promising a lift.