Test the shipping promise before shoppers see it.
WooCommerce decides whether shipping is actually free. This module makes one manually configured threshold visible and adds a Mon–Fri delivery window. Reproduce the calculation, inspect the real surfaces and decide whether release 0.2.2 matches your store.
- €49/yr
- current annual self-hosted package, ex VAT
- 0.2.2
- current package verified by SHA-256
- WC 8.0–10.7
- package header boundary; stage the exact stack
- WP 6.0–6.9
- package header boundary; not a universal guarantee
The visible promise and the real shipping rule must agree.
Name the real shipping rule
WooCommerce free shipping is configured inside a shipping zone and may require an amount, a coupon, both or neither. That method—not this progress bar—decides checkout eligibility.
Copy one approved number
Release 0.2.2 stores one manual numeric threshold. It does not read the active zone, shipping method or currency-specific target. Ownership of keeping both settings aligned stays with the merchant.
Define the amount basis
The bar uses the WooCommerce cart subtotal excluding tax and shipping. Core free shipping can evaluate coupon conditions differently, so test the exact before/after-discount policy used by each zone.
Bound the delivery statement
The window uses WordPress site time, one cutoff hour and Mon–Fri processing/transit days. Holidays, closures, zones, methods and carrier calendars are not part of the calculation.
Reproduce the shopper-facing threshold and weekday window.
Change the same fields available in the shipped package. Start with a Friday order after the cutoff to see the weekend roll-forward.
- Processing starts
- Mon, Jul 20, 2026
- Configured delivery window
- Wed, Jul 22, 2026 – Tue, Jul 28, 2026
Mirrors release 0.2.2 only. Uses Mon–Fri weekdays and one manual threshold. Excludes holidays, closures, zones, methods, carrier calendars, tax/coupon eligibility and currency-specific thresholds. A configured window is not a carrier guarantee.
Inputs stay in this browser; with analytics consent only navigation events may be counted.
Follow the same threshold from product to checkout.
1. Introduce the current cart gap on the product page
The block places the manually configured goal, remaining amount and weekday window beside the purchase action. The remaining amount comes from the current cart subtotal, not from the viewed product alone.
Open this exact product scene →
2. Recalculate from the live cart subtotal
The cart repeats the same configured target and recalculates progress as cart contents change. This is where coupon, tax-display and actual free-shipping eligibility mismatches should be staged.
Open this exact product scene →
3. Verify the promise against the final shipping method
At checkout, compare the displayed threshold state with the shipping method WooCommerce actually offers for the customer address. A matching message is evidence; the message itself never grants free shipping.
Open this exact product scene →
Prove that the message and WooCommerce become eligible together.
| Mismatch risk | What 0.2.2 does | What you must test |
|---|---|---|
| Manual threshold drifts | One numeric value is stored in Shipping Promise Booster; no zone or method lookup runs. | Change the real WooCommerce threshold and confirm your release checklist catches the second setting. |
| Coupons change eligibility | The bar compares its threshold with cart subtotal; it does not reproduce every core coupon requirement. | Test no coupon, amount coupon, free-shipping coupon and the zone’s before/after-discount option. |
| Address selects another zone | The visible threshold remains the same because 0.2.2 has no per-zone or per-country rules. | Enter one address per active shipping zone and compare the message with offered methods. |
| Holiday moves fulfilment | The date loop skips Saturday and Sunday only. It has no holiday or closure calendar. | Run an order across every closure period; disable the promise or widen the configured range when needed. |
| Timezone or cutoff is wrong | The package uses the WordPress site timezone and rolls to the next weekday at the configured whole hour. | Test one minute before and after the business cutoff, plus Friday evening and Sunday. |
| Theme suppresses a surface | WooCommerce hooks, Blocks fallbacks and CSS classes are included, but custom drawers and templates can change placement. | Inspect product, mini-cart, cart and checkout on desktop and mobile with the production theme. |
Keep WooCommerce as the source of truth.
WooCommerce grants free shipping
Configure the actual method inside each shipping zone. Core supports no requirement, coupons, a minimum amount, or combinations of amount and coupon. Keep this checkout rule authoritative.
Read the official source ↗Shipping Promise Booster displays one model
Use it when one manual threshold and a straightforward Mon–Fri window match the shop. It adds visibility on configured surfaces but does not replace WooCommerce shipping logic.
Inspect the real plugin →Use a deeper engine for conditional dates
If dates differ by product, stock, country, zone, method, holiday or carrier, 0.2.2 is not feature-equivalent to a rules-based delivery extension. Compare the exact scope before choosing.
Read the official source ↗A simple promise is useful only when the fulfilment model is simple too.
Good fit · one threshold, simple weekdays
The store uses one economically approved threshold in its active currency, ships on a stable Mon–Fri model and wants the same message on product, cart and checkout surfaces.
Conditional fit · custom theme or coupon policy
Blocks, classic checkout, cart drawers, tax display and coupon policy can all affect what the shopper sees. Proceed only after the exact production stack passes staging.
Not a fit · conditional fulfilment engine
Choose another path if you need per-zone, per-method, per-country or per-currency thresholds, holiday closures, carrier APIs, delivery slots, a date picker or a carrier guarantee.
Before you publish a shipping promise
- Does version 0.2.2 read the threshold from WooCommerce shipping zones?
- No. It stores one manual numeric threshold in its own settings. Copy the approved target from the relevant WooCommerce free-shipping method and include both settings in every threshold-change checklist.
- Which amount does the progress bar use?
- The delivered 0.2.2 code calls WC()->cart->get_subtotal() and treats it as subtotal excluding tax and shipping. It does not independently reproduce every coupon or free-shipping eligibility rule configured in WooCommerce.
- Does the delivery window exclude public holidays or closures?
- No. It skips Saturday and Sunday only. If a holiday or warehouse closure changes fulfilment, widen or disable the message, or use a delivery engine with explicit excluded-date support.
- Can I configure different thresholds by zone, method or currency?
- Not in 0.2.2. The release stores one numeric threshold and formats it in the active WooCommerce currency. If the economic target differs by zone, method or currency, this release is not a verified fit without a carefully staged external integration.
- Does it work with WooCommerce Cart and Checkout Blocks?
- The package declares Blocks and HPOS compatibility and includes block-render plus classic-hook fallbacks. That is not a promise for every theme, cart drawer or extension combination. Stage product, mini-cart, cart and checkout on the exact stack.
- Is the displayed date a carrier guarantee?
- No. It is a configured weekday window calculated without carrier APIs, live capacity, weather, strikes, holidays or address-specific transit data. Phrase it as an estimate and validate it against the fulfilment operation.
- Will a free-shipping bar increase conversion or average order value?
- There is no guaranteed lift. The bar exposes a rule that already exists; shopper response depends on economics, traffic, product mix, shipping cost and presentation. Establish a baseline and measure attributable behavior after release.
- What compatibility evidence is currently published?
- The verified 0.2.2 package header requires WordPress 6.0 and WooCommerce 8.0, and declares testing through WordPress 6.9 and WooCommerce 10.7.0. The exact patch, PHP version, theme, Blocks/classic path and extensions still require staging.
Open the real product, cart and checkout path.
The product experience keeps the current release, SHA-256, compatibility boundary, screenshots, settings and purchase terms together. Buy only after the manual threshold and weekday model pass staging.