QuickShipD – Estimated Delivery Date for WooCommerce

Yes. Under WooCommerce → QuickShipD → Display → Product delivery date, choose Soonest date, Latest date, or Delivery range. This applies to product pages, variations, and shop estimates. Cart and checkout follow the selected shipping method.

Does QuickShipD work without WooCommerce?

Is there a shortcode?

Without product_id it needs a product in context, so it works on product pages, in a builder’s product template, and inside product loops. On a normal page, post, or widget there is no product to read and it prints nothing, so pass one: [quickshipd product_id="123"] . Add context="shop" for the compact style with no countdown. The Help tab in the plugin settings has the full table.

Yes. Go to WooCommerce → QuickShipD → Display → Orders & Emails . Turn off “Save on the order” to store nothing at all, or leave it on and untick individual emails under “Show in these emails”. Developers can also use the quickshipd_save_order_item_date and quickshipd_show_in_email filters.

Yes — QuickShipD does not break the block-based checkout. Full block checkout integration (rendering the estimate inside the block) is on the roadmap for v1.1.

No. The delivery date is calculated in PHP on page load — no external API calls, no database queries beyond standard wp_options reads. Frontend assets (CSS + JS) are under 2 KB combined and are only loaded on pages where the delivery estimate is shown.

Yes — set Min delivery days and Max delivery days to the same value in WooCommerce → QuickShipD → Delivery . The plugin automatically switches to the single-date template (“Get it by {date}”).

QuickShipD calculates the delivery date estimate using your delivery days, shipping method, cutoff time, holidays, and non-dispatch days.

Go to WooCommerce → QuickShipD → Delivery → Holidays . Add a single date or a date range with the date pickers, optionally enable Repeats every year for annual holidays, then click Add. Ranges must stay within the same calendar year.

Yes — go to WooCommerce → QuickShipD → Style → Text Templates . Three templates are available: single-date text, date-range text, and countdown text. Each supports simple placeholders: {date} , {start} , {end} , {countdown} .

Yes — open the product in the WooCommerce product editor, go to the Shipping tab, and check “Disable delivery estimate for this product”. You can also set per-product minimum/maximum days in the same tab.

Yes. The delivery date is hidden until a variation is selected; then a lightweight AJAX request fetches the correct estimate for that variation.

Set Minimum delivery days to 0 in WooCommerce → QuickShipD → Delivery , and set the Order cutoff time to your last dispatch run of the day. Delivery days are counted after dispatch, so 0 means the parcel arrives on the day it goes out. Use 0 and 0 for a single same-day date, or 0 and 1 if a late order might slip to tomorrow. Orders placed after the cutoff, or on a non-dispatch day, automatically move to the next dispatch day.

Yes — a small vanilla JS script (no jQuery) ticks the countdown every second and hides it when it reaches zero. If JavaScript is disabled, the static delivery date text remains visible; only the countdown is affected.

PDF invoice and packing slip plugins read the order line meta directly, so unticking an email under WooCommerce → QuickShipD → Display → Orders & Emails will not remove it from a printed slip. Turn off Save on the order to stop storing it altogether, or use the quickshipd_save_order_item_date filter to skip it for specific orders. Existing orders keep whatever they were given at checkout.

No. QuickShipD will always have a complete free version.

Yes. QuickShipD makes no external HTTP requests, stores no personal data, and sets no cookies.

QuickShipD reads the WordPress timezone setting (Settings → General) and uses it for all calculations. After changing your timezone, you may need to clear any page-caching plugins.

The plugin uses WordPress’s date_i18n() function, so day and month names are automatically translated to your active locale. It is compatible with WPML, Polylang, and similar translation plugins.