Title: Daybound Delivery Date for WooCommerce
Author: Edinson Moreno
Published: <strong>November 21, 2026</strong>
Last modified: November 21, 2026

---

Search plugins

![](https://ps.w.org/daybound-delivery-date/assets/banner-772x250.png?rev=3815868)

![](https://ps.w.org/daybound-delivery-date/assets/icon-256x256.png?rev=3815868)

# Daybound Delivery Date for WooCommerce

 By [Edinson Moreno](https://profiles.wordpress.org/master14566/)

[Download](https://downloads.wordpress.org/plugin/daybound-delivery-date.1.0.0.zip)

 * [Details](https://wordpress.org/plugins/daybound-delivery-date/#description)
 * [Reviews](https://wordpress.org/plugins/daybound-delivery-date/#reviews)
 *  [Installation](https://wordpress.org/plugins/daybound-delivery-date/#installation)
 * [Development](https://wordpress.org/plugins/daybound-delivery-date/#developers)

 [Support](https://wordpress.org/support/plugin/daybound-delivery-date/)

## Description

Daybound Delivery Date for WooCommerce lets your customers choose a delivery date
in the WooCommerce **block checkout**. It is built on the official **Block Checkout
Integration API** and the **Store API**, so the date field appears inside the checkout
form, uses WooCommerce’s own validation, and is saved with the order.

When a shopper picks a date, the calendar disables anything they shouldn’t choose—
past days, days inside your lead time, blackout dates, and anything beyond your 
maximum window — and the choice is re-validated **on the server** before it is ever
trusted. Leaving the date empty blocks “Place Order” using WooCommerce’s own native
validation, not a custom error box. The selected date is saved to the order as **
HPOS-compatible order meta** and shown to you in the orders list and on the order
detail screen.

#### Features

 * Delivery-date picker injected into the **block checkout** via the official Integration
   API (not legacy checkout hooks).
 * Calendar that disables past dates, sub-lead-time dates, and dates beyond your
   maximum future window — all computed in your **store timezone**.
 * Configurable **minimum lead time**, **maximum future window** and **blackout 
   dates** (holidays, closed days) from a settings page.
 * **Native** “Place Order” blocking when no date is selected (WooCommerce validation
   store).
 * **Server-authoritative** revalidation of every date via the Store API — client
   checks are never trusted.
 * Delivery date saved to the order as **HPOS-safe** meta (`_daybound_delivery_date`).
 * “Delivery Date” **column on the orders list** (HPOS and legacy) and a read-only
   date on the **order detail** screen.
 * The chosen date is shown back to the customer in the **order totals** (order 
   confirmation and order details).
 * Calendar months and weekdays follow your **site language** and “week starts on”
   setting.
 * A page reload **keeps the date** the shopper already picked.
 * Graceful **fallback to a native date input** if the calendar ever fails to render.
 * Fully **translatable** (ships a `.pot` plus Spanish translations) and **accessible**(
   labelled calendar, live-region announcements).

## Screenshots

[⌊The delivery-date calendar inside the block checkout, with unavailable days disabled.⌉⌊
The delivery-date calendar inside the block checkout, with unavailable days disabled
.⌉[

The delivery-date calendar inside the block checkout, with unavailable days disabled.

[⌊Native "Place Order" validation when no date is selected.⌉⌊Native "Place Order"
validation when no date is selected.⌉[

Native “Place Order” validation when no date is selected.

[⌊The "Delivery Settings" admin page (lead time, maximum window and blackout dates).⌉⌊
The "Delivery Settings" admin page (lead time, maximum window and blackout dates)
.⌉[

The “Delivery Settings” admin page (lead time, maximum window and blackout dates).

[⌊The "Delivery Date" column on the WooCommerce orders list.⌉⌊The "Delivery Date"
column on the WooCommerce orders list.⌉[

The “Delivery Date” column on the WooCommerce orders list.

[⌊The delivery date on the order detail screen.⌉⌊The delivery date on the order 
detail screen.⌉[

The delivery date on the order detail screen.

## Installation

 1. Make sure **WooCommerce 8.3 or higher** is installed and active, on **PHP 8.0+**
    and **WordPress 6.6+**.
 2. Upload the `daybound-delivery-date` folder to `/wp-content/plugins/`, or install
    the zip via **Plugins  Add New  Upload Plugin**.
 3. Activate the plugin through the **Plugins** screen.
 4. Go to **WooCommerce  Delivery Settings** and set your minimum lead time and maximum
    future window.
 5. Open your block checkout — the **Select a delivery date** field appears inside 
    the checkout form.

The plugin declares **High-Performance Order Storage (HPOS)** compatibility, so 
it works whether or not you have HPOS enabled.

## FAQ

### Does this work with the block checkout?

Yes. The field is added through WooCommerce’s official Block Checkout Integration
API, so it renders inside the checkout form and uses native validation.

### Does it work with the classic (shortcode) checkout?

No. Version 1.0 targets the modern **block checkout**, which has been the WooCommerce
default since 8.3. If your store still uses the classic shortcode checkout, switch
to the block checkout to use this plugin.

### Is it HPOS compatible?

Yes. The plugin declares `custom_order_tables` compatibility and reads/writes order
data exclusively through the order object API (`$order->get_meta()` / `$order->update_meta_data()`),
so it is correct on both HPOS and legacy storage.

### Can a customer bypass the date rules by calling the API directly?

No. Every date is re-validated on the server by an authoritative validator that 
derives all boundaries (today, lead time, blackout list, timezone, maximum window)
from your server configuration and ignores anything the client claims. The calendar’s
disabling is a UX convenience, never the security boundary.

### What happens if something goes wrong during checkout?

The plugin is designed to never break a purchase. If the calendar fails to render,
it falls back to a native date input. If the date can’t be saved at order time, 
the order still completes without a date and the issue is logged, so you can contact
the customer to agree on one. Internal failures are written to **WooCommerce  Status
Logs** (source `daybound-delivery`), never shown to the shopper.

### Is it translatable?

Yes. All user-facing strings (PHP and JavaScript) use the `daybound-delivery-date`
text domain, and the plugin ships `languages/daybound-delivery-date.pot`. JavaScript
strings are wired with `wp_set_script_translations()`.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Daybound Delivery Date for WooCommerce” is open source software. The following 
people have contributed to this plugin.

Contributors

 *   [ Edinson Moreno ](https://profiles.wordpress.org/master14566/)

[Translate “Daybound Delivery Date for WooCommerce” into your language.](https://translate.wordpress.org/projects/wp-plugins/daybound-delivery-date)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/daybound-delivery-date/),
check out the [SVN repository](https://plugins.svn.wordpress.org/daybound-delivery-date/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/daybound-delivery-date/)
by [RSS](https://plugins.trac.wordpress.org/log/daybound-delivery-date/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.0

 * Initial public release.
 * Delivery-date picker injected into the block checkout via the official Integration
   API.
 * Store-timezone calendar that disables past, sub-lead-time, beyond-maximum, and
   blackout dates.
 * Native `VALIDATION_STORE_KEY` blocking of “Place Order” when no date is selected.
 * Server-authoritative Store API revalidation; client checks are never trusted.
 * HPOS-safe order meta persistence (`_daybound_delivery_date`) and admin orders-
   list column + order-detail display.
 * Settings page for minimum lead time and maximum future window (capability-gated,
   nonce-protected).
 * Resilience: Error Boundary with native date-input fallback; safe config defaults;
   missing date never blocks the order.
 * 500 ms client debounce, 10 s request timeout (AbortController), and per-session
   2 s server rate limit.
 * Full i18n (ships `.pot`, registers JS translations) and accessibility (labelled
   calendar, live regions, `aria-describedby`).
 * Fixed the textdomain-too-early (`_load_textdomain_just_in_time`) notice by deferring
   dependency-notice translation to after `init`.

## Meta

 *  Version **1.0.0**
 *  Last updated **2 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.6 or higher **
 *  Tested up to **7.1.5**
 *  PHP version ** 8.0 or higher **
 * Tags
 * [block checkout](https://wordpress.org/plugins/tags/block-checkout/)[checkout](https://wordpress.org/plugins/tags/checkout/)
   [delivery date](https://wordpress.org/plugins/tags/delivery-date/)[store-api](https://wordpress.org/plugins/tags/store-api/)
   [woocommerce](https://wordpress.org/plugins/tags/woocommerce/)
 *  [Advanced View](https://wordpress.org/plugins/daybound-delivery-date/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/daybound-delivery-date/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/daybound-delivery-date/reviews/)

## Contributors

 *   [ Edinson Moreno ](https://profiles.wordpress.org/master14566/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/daybound-delivery-date/)