Every settings tab and rule in the admin panel, documented in full below — including the exact priority order used when more than one rule could apply to the same product.
1. Settings tabs overview
All settings live under WooCommerce > Estimated Delivery, split across six tabs:
- General: enable/disable, global min/max delivery days, order cut-off time, business days, which pages show the estimate (product/cart/checkout), date format, the three message templates (date range, minimum-only, maximum-only), and the optional same-day dispatch countdown.
- Shipping Zones: override the global day range per WooCommerce shipping zone (zones are defined under WooCommerce > Settings > Shipping).
- Holidays: a list of specific dates excluded from the delivery-day count (public holidays, warehouse closures).
- Postcode Rules: per-postcode day overrides, payment-method restrictions, and full delivery blocks, with CSV bulk import/export.
- Appearance: background/text/border colors for the normal estimate box and the restricted (not-deliverable) box, with a live preview.
- Simulator: pick a product, country, state, postcode, and a simulated order date/time, and see exactly which rule wins and what message the customer would see — without placing a real order.
Category overrides live on the category edit screen, shipping-class overrides on Products > Shipping classes, product overrides in a product's own "Delivery Estimate" tab, and variation overrides inside each variation row on the Variations tab of a variable product.
2. Which rule wins: the priority order
Only one delivery-day rule is used per product — the plugin checks each level in order and stops at the first one that applies:
- Variation override — for a variable product, a min/max range set on the exact variation in the cart/order. Always wins if set.
- Product override — a min/max day range set directly on that one product (or the parent product, if no variation override applies).
- Category override — checked only if the product has no override of its own. If the product belongs to more than one category with an override enabled, the first matching category found wins.
- Shipping class override — the override for the product's assigned shipping class (Products > Shipping classes), checked only if nothing above applied.
- Postcode rule's own days — if the customer's postcode matches a Postcode Rule that itself sets min/max days, that is used next (see point 3 below for how a postcode match is chosen).
- Shipping zone override — the override for whichever WooCommerce shipping zone matches the customer, checked only if nothing above applied.
- Global default — the General tab's min/max days, used only when none of the above match anything.
In short: variation > product > category > shipping class > postcode > shipping zone > global. The Simulator tab shows which of these seven actually resolved the estimate for any test you run, so there's no guessing.
3. Postcode Rules in detail
How a postcode match is chosen
If a rule exists for that exact postcode and the customer's country, it is used first. Otherwise, a rule saved for that postcode with no country set (a country-independent/wildcard rule) is used instead.
Three independent effects
- Delivery days — only applied if the rule itself sets min/max days (see priority order above).
- Allowed payment methods — any gateway not in the rule's allowed list is hidden at checkout for that postcode, on both classic and block checkout. Leaving the list empty allows every enabled gateway (no restriction).
- Restrict delivery — marking a postcode as restricted blocks checkout entirely for it, with the message "Sorry, we do not currently deliver to this postcode/zip code." This check runs independently of the day-priority rule above.
CSV columns for bulk import/export: postcode, country, min_days, max_days, allowed_payment_methods, is_restricted — payment methods are pipe-separated gateway IDs (e.g. cod|bacs), is_restricted is 0 or 1, and a header row is optional.
4. The [nacs_edd_estimate] shortcode
Shows the estimate anywhere a shortcode can run — a page, post, or widget — not just on WooCommerce's own templates.
[nacs_edd_estimate] with no attribute: on an actual product page it shows that product's estimate; anywhere else (a normal page or post) it falls back to the customer's current cart and shows the slowest item's estimate. If the cart is empty, it shows nothing.
[nacs_edd_estimate id="123"]: always shows that specific product's estimate, regardless of the page or cart — the right choice for a landing page built around one product.
- In both forms, a customer whose postcode is marked restricted sees the red "not deliverable" message instead, anywhere the shortcode is placed.
5. Order, account, and email display
The resolved estimate message is saved on the order itself (order meta _nacs_edd_estimate_message) at the time it's placed, so it stays fixed even if settings change later. It's shown on the thank-you page, the customer's My Account > Orders view, the admin order screen, and in transactional order emails sent to the customer (processing, completed, etc.) — both HTML and plain-text email formats are supported. It is not added to the admin's own new-order notification email.
6. Same-day dispatch countdown
An optional live countdown (e.g. "Order within 2h 15m for same-day dispatch") shown next to the estimate on the product, cart, and checkout pages. It is enabled and worded from the General tab's "Countdown timer" field, using the {countdown} placeholder. It only appears while today is still a configured business day and the cut-off time has not passed yet — once the cut-off passes, or on a non-business day, it is hidden automatically rather than showing a stale or negative countdown. The countdown ticks client-side in the visitor's browser, so it stays accurate without reloading the page.
7. Appearance and translation
The Appearance tab controls the background/text/border colors of both the normal estimate box and the restricted box, plus whether a small clock icon is shown, with a live preview of the exact customer-facing message. All plugin text uses the nacstech-estimated-delivery-dates text domain, and the message templates — including the countdown wording — are additionally registered with WPML String Translation and Polylang so multilingual stores can translate the customer-facing wording per language.