WooCommerce Estimated Delivery Dates
Give WooCommerce customers delivery dates you can actually explain.
Regal Delivery Dates calculates estimated arrival dates from your real fulfilment rules — store preparation, carrier calendars, shipping zones and methods, product delays, stock state, cut-offs and holidays — then keeps the customer promise attached to the order.
✓ Explainable calculations ✓ Classic + Blocks support ✓ Saved order delivery promise
More than “add three days to today”
Delivery estimates are only useful when the calculation reflects how your store actually fulfils orders.
Regal Delivery Dates separates preparation from carrier transit, understands when customers can actually receive a delivery, applies shipping and product-specific rules, skips configured closures and preserves the result that was shown at checkout. That gives customers a clearer answer and gives your team a calculation it can inspect later.
1
Model the real fulfilment journey
Use separate store preparation days, carrier operating days and customer no-delivery weekdays, with global or weekday-specific order cut-offs.
2
Adapt to the product and shipping choice
Layer rules for shipping zones, methods and classes with product, variation, category and tag delays, availability dates and stock-state conditions.
3
Keep the original promise visible
Save the calculated estimate with the order so later settings changes do not rewrite what the customer was originally shown.
The problem
One generic delivery window breaks down as soon as your fulfilment gets more complicated.
A date can change because the warehouse is closed, the carrier does not move parcels that day, the customer cannot receive on a certain weekday, an order missed its cut-off, a slower product is in the basket, stock is incoming, or a destination has a holiday. Treating those as one number produces estimates that are difficult to trust or explain.
The Regal IT approach
Calculate the journey in stages and keep a trace of what affected it.
- Count store preparation and carrier transit against their own working calendars.
- Apply shipping-zone, shipping-method and shipping-class adjustments without flattening every service into one estimate.
- Add targeted product rules for extra preparation, availability dates and in-stock, backordered or out-of-stock conditions.
- Use local holiday data and destination calendars without making customer-facing calculations depend on a live external API.
- Inspect the real calculation engine in Diagnostics and see applied or skipped rules against a controlled product, destination and time.
Core features
Model the delivery journey, show it where customers need it and keep the calculation auditable.
Three operational calendars
Configure store preparation days, carrier operating days and weekdays that must never be shown as the customer’s final delivery date.
Shipping-aware rules
Add days, cut-offs, excluded delivery weekdays, carrier calendars and custom wording by WooCommerce shipping zone, method or shipping class.
Targeted product delays
Target products, variations, categories or tags with priority rules, extra preparation, availability dates and stock-state conditions.
Backorders & incoming stock
Apply a global backorder delay, target backordered products directly and explicitly enable estimates for matching out-of-stock products with an availability rule.
National, manual & recurring holidays
Preview and import UK bank holidays from GOV.UK plus US and EU-country dates from Nager.Date, or add local manual and annually recurring closures.
Flexible customer-facing wording
Show a simple date or date range, optional Today/Tomorrow/weekday wording, safe basic HTML, shipping-method wording overrides and placement-specific messages.
Cut-off countdown
Show a live order cut-off countdown in supported WooCommerce locations, by shortcode or with the Delivery Cut-off Gutenberg block, with configurable after-cut-off wording.
Cache-safe dynamic refresh
Optionally refresh cached product, archive, shortcode and Delivery Date block estimates after page load in a single deferred request while retaining the rendered estimate if refresh fails.
Classic + Block storefront coverage
Display estimates on products, archives, cart items, shipping methods, cart/checkout, Classic and Block mini-carts, shortcodes, blocks, order received and account views.
Order snapshots & update workflow
Store a structured estimate and selected shipping-method wording at checkout, then let administrators change the delivery estimate with a reason and optionally email the customer.
Emails that use the checkout promise
Add the saved estimate to selected WooCommerce emails and keep order messaging based on the snapshot rather than whatever the current settings now calculate.
Diagnostics & portable configuration
Run the real calculator against a controlled date, product, destination and shipping method, inspect the trace, and validate JSON configuration imports without silently remapping missing entities.
Feature comparison
Where Regal Delivery Dates goes beyond a basic estimated-date display.
We compared the publicly documented feature sets of three established alternatives and focused on the operational controls that matter when delivery logic becomes more complex.
| Feature | Regal Delivery Dates | PluginHive Estimated Delivery Date | Plugify Estimated Delivery Date & Time | WPC Estimated Delivery Date |
|---|---|---|---|---|
| Separate store, carrier & customer delivery calendars | Included Three distinct calendars |
Partial Store and carrier working days documented |
Not publicly documented | Partial Weekend/holiday exclusions documented |
| Shipping zone, method & class rules | Included Days, cut-offs, no-delivery days, carrier calendar and wording |
Included | Different rule model City/state plus product/category/variation rules documented |
Included / aware Shipping class rules; method/address updates documented |
| Availability dates + stock-state targeted product rules | Included Product, variation, category and tag targets |
Partial Stock/backorder support documented |
Partial In-stock/out-of-stock/backorder rules documented |
Partial Broad product targeting; availability/stock conditions not stated |
| Live cut-off countdown block / shortcode | Included | Cut-off times documented Countdown not stated |
Not publicly documented | Not publicly documented |
| National holiday import with local storage | Included GOV.UK + Nager.Date, stored locally |
Manual/custom holidays documented | Not publicly documented | Holiday/vacation exclusions documented |
| Explainable admin simulator / calculation trace | Included | Not publicly documented | Not publicly documented | Not publicly documented |
| Saved checkout estimate + admin override / customer update workflow | Included Snapshot, audit reason and optional update email |
Order/email display documented Override workflow not stated |
Not publicly documented | Not publicly documented |
| Mini-cart delivery estimate | Classic + Block mini-cart Complete-order estimate |
Theme mini-cart documented Cart/Checkout Blocks also documented |
Not publicly documented | WPC Fly Cart documented Block mini-cart not stated |
Comparison note: Based on features publicly documented by each vendor on 19 September 2026. “Not publicly documented” means the feature was not found in the product materials reviewed; it does not claim the feature is impossible or absent from every edition.
Real use cases
Built for the edge cases that make “delivery in 3–5 days” stop being enough.
Scenario 1
Different carrier services
Give standard and express services their own transit days, carrier calendars, cut-offs and customer-facing wording.
Scenario 2
Made-to-order or seasonal products
Delay preparation for specific products, categories or tags, or prevent preparation before a known availability date.
Scenario 3
International delivery calendars
Apply locally stored destination holiday calendars while keeping customer-facing calculation independent of remote service availability.
Scenario 4
Post-purchase delivery changes
Preserve the original estimate, then record an administrative change and optionally notify the customer if the expected delivery window moves.
How it works
Configure the model, test it, then show the result across WooCommerce.
1
Set your calendars
Choose store preparation days, carrier operating days, customer no-delivery weekdays, cut-offs and default processing/transit times.
2
Add the exceptions
Configure shipping rules, targeted product delays, stock conditions, availability dates and the holiday calendars your store needs.
3
Choose where customers see it
Enable the estimate on product, archive, cart, checkout, mini-cart, shortcode/block, order and email locations with the wording and presentation you want.
4
Verify the calculation
Use Diagnostics to simulate a real product, destination, shipping method and time, then review the calculation trace before going live.
Try it on your WooCommerce store
Turn “when will it arrive?” into a delivery promise your store can explain.
Use the trial to model your real calendars, shipping rules and product exceptions, then verify representative orders in Diagnostics before showing estimates to customers.