Estimated Delivery Date FAQ and translating

No. Activation creates a Product is Any rule at 2–5 business days, so every shippable product shows an estimate straight away. Change those numbers to your real window and you are done.

There is no zone to configure and no shipping method to add.

Most often it is virtual, external, or has no price — nothing is being shipped, so nothing is promised. It might also be set to Hide for this product, or match no rule at all.

No, and the wording is deliberately “estimated”. The plugin counts your dispatch days; it does not track a parcel. If a carrier is late, the estimate does not know.

It attaches to standard WooCommerce hooks, so it works with classic and block themes alike. If the badge lands somewhere awkward, change Display → Position on product page — that moves it earlier or later within the product summary.

Dates are cached for up to an hour, and the cache clears when you save settings. Product and category pickers in the rule builder search on demand rather than loading your whole catalogue.

Yes, with one thing to watch. The date caches fine — it is measured in days. The countdown does not: it ticks in the browser but starts from a value the server wrote into the page, so a cached page freezes it at the moment it was generated. Does it work with page caching? covers what to exclude.

No. The estimate is frozen onto the order at checkout, so order emails, the thank-you page and My Account keep showing what the customer was actually promised.

Use the shortcode [edfw_estimated_delivery] on a product template.

Yes — both are declared compatible, along with HPOS (High-Performance Order Storage).

Yes. It is exposed on the WooCommerce Products and Orders REST API and on the Store API, which is what a headless storefront would read.