Diagnose Delivery Dates estimates

Updated September 20, 2026

Delivery Dates diagnostics explain why a product has received a particular delivery estimate. The simulator uses the real calculation engine with a controlled product, destination, shipping method and time. It is read-only and does not create a persistent diagnostic log.

Delivery Dates diagnostics: run an estimate#

1. Open WooCommerce > Delivery Dates > Diagnostics.
2. Search for the product or variation that needs checking.
3. Enter the quantity, customer destination country and postcode.
4. Select the shipping method if the scenario depends on a specific service. Otherwise, leave it as Automatic / none.
5. Set the simulated date and time, then select Calculate estimate.
6. Read the estimate summary, chronological trace and delivery calendar together.

Read the trace and delivery calendar#

The trace records the calculation in order. Each calculation date appears directly below its related event on the left, making the sequence easier to scan. It can show a cut-off taking effect, a shipping or product rule adding days, a non-working weekday being skipped, a holiday extending preparation or transit, a backorder delay and the final estimate.

The Delivery calendar starts on Monday and labels every weekday across the top. It highlights the simulated calculation date and the estimated delivery date so you can quickly see how the scenario moved through the calendar. A trace date is evidence for that step, not automatically the final customer promise.

Follow practical diagnostics examples#

Example: delivery changed after cut-off#

Choose a normal in-stock product and run the same scenario twice: once a few minutes before the configured cut-off and once a few minutes after it. The later trace should show the cut-off taking effect and processing beginning on the next eligible store day. If it does not, check the WordPress timezone, the global cut-off and any earlier matching rule cut-off.

Example: one shipping service delivers later#

Run one scenario with each relevant shipping method selected. Compare the trace and final estimate. A matching shipping-method rule can add days, use a different carrier working calendar or exclude delivery weekdays, so the estimates may legitimately differ even for the same product and address.

Example: a destination holiday affects one country only#

With Apply destination holidays enabled and the appropriate calendar imported, run the same product near a holiday for two destination countries. A holiday imported for the United States can affect a United States delivery estimate, but it should not affect a United Kingdom estimate. Check that the correct country and year are imported and enabled before concluding that a calculation is wrong.

Example: a product needs extra preparation#

Choose a product or variation covered by a Product delays rule. The trace should identify the targeted delay and show the extra working days. If it does not, confirm the selected product, variation, rule target, enabled status and priority. Product rules take precedence over category rules, then tag rules.

Checks for an unexpected estimate#

• Confirm the WordPress timezone and simulated time.
• Check whether the current day is allowed to count and whether the relevant cut-off has passed.
• Review the selected variation’s shipping class and stock status.
• Confirm the destination matches the intended shipping zone and method instance.
• Check store processing, carrier operation and no-customer-delivery weekdays separately.
• Confirm the required holiday country and year were imported and enabled.
• Review targeted rule specificity and numeric priority.

If the wider store environment is relevant, the WooCommerce System Status guide explains the platform report used for compatibility checks.