# etechflow/module-delivery-date

> Let customers pick their own delivery day at checkout. Hyvä native, blackout days, time slots (v0.3+), customer rescheduling (v0.4+), and the four admin-UX wins Amasty doesn't ship — live simulator, conflict detection, versioned config, plain-English help.

`composer require etechflow/module-delivery-date`

Canonical URL: https://packagento.com/etechflow/module-delivery-date

## At a glance

- **Vendor**: etechflow (https://packagento.com/etechflow.md)
- **Latest version**: 1.6.0 — released 2026-06-06
- **Pricing**: Free
- **Package type**: Magento 2 module
- **Status**: active, accepting new buyers

## Installation

Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them.

1. **Sign in or create an account** at https://packagento.com/customer/account/.

2. **Add the package to your account.** Open https://packagento.com/etechflow/module-delivery-date and complete the free checkout. A licence is minted automatically.

3. **Create or pick a project, then activate the licence on it.**
   - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/.
   - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project.

4. **Add the project credentials to your Magento codebase.**

   Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`:

   ```json
   {
     "http-basic": {
       "packagento.com": {
         "username": "ppk_live_...",
         "password": "psk_live_..."
       }
     }
   }
   ```

   Add the Packagento Composer repository to `composer.json`:

   ```json
   {
     "repositories": [
       { "type": "composer", "url": "https://packagento.com" }
     ]
   }
   ```

5. **Install and apply.**

   ```bash
   composer require etechflow/module-delivery-date:*
   bin/magento setup:upgrade
   bin/magento setup:di:compile
   bin/magento cache:flush
   ```

## What it does

Let customers pick their own delivery day at checkout. Hyvä native, blackout days, time slots (v0.3+), customer rescheduling (v0.4+), and the four admin-UX wins Amasty doesn't ship — live simulator, conflict detection, versioned config, plain-English help.

## Changelog

All notable changes to the **ETechFlow Delivery Date Picker** module are documented here.

The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this module adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

---

### [1.5.1] — 2026-06-03 — Billing-period plans (weekly / monthly / yearly)

#### Changed

- **License gate now offers billing periods instead of feature tiers.** Replaced the Starter/Professional/Enterprise cards with **Weekly $9 / Monthly $29 / Yearly $290** (one full-feature price point, USD; yearly ≈ 2 months free). Updated `Controller/Adminhtml/License/Checkout.php` `PLAN_INFO` (`dd_weekly|monthly|yearly`) and the gate template. Matches the eTechFlow portal's new billing-period subscription model.

### [1.4.3] — 2026-05-22 — Move admin menu under eTechFlow top-level sidebar

#### Changed

- **DD admin pages relocated to a dedicated "eTechFlow" sidebar entry.** Previously the Delivery Date group (with Time Intervals + Exception Days children) lived under `Sales → Sales`. Now it sits as a `Delivery Date` column inside a new top-level `eTechFlow` sidebar entry (clusters with other paid-extension vendors above Magento's Stores). Matches the pattern Amasty / Magefan / MageWorx use.
- Each eTechFlow module declares the same `eTechFlow::root` + `eTechFlow::settings` + `eTechFlow::configuration` entries — Magento merges by id, so installing N modules still produces exactly one `eTechFlow` sidebar group. No inter-module dependency added.

#### Migration

```
composer update etechflow/module-delivery-date
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush
```

Admin URL routes unchanged (`etechflow_dd/timeInterval/index` and `etechflow_dd/exceptionDay/index` still work). No schema or behaviour changes — pure menu-layout adjustment.

---

### [1.4.1] — 2026-05-20 — Magewire dependency hotfix

#### Fixed

- **`magewirephp/magewire` moved from `suggest` to `require`.** The `Magewire/Checkout/DeliveryDatePicker.php` class added in v1.4.0 extends `\Magewirephp\Magewire\Component`. On a store without Magewire installed (Hyvä Theme without Hyvä Checkout, or a plain Open Source install), `bin/magento setup:di:compile` would attempt to compile our class against the missing parent and produce broken interceptors — which could surface as random admin breakage. The v1.4.0 CHANGELOG claim that the file would "sit inert on disk" was wrong: di:compile scans every class regardless of whether the layout handle that uses it ever activates.
  - Composer will now install Magewire transitively. It's a tiny package and is the parent of every Hyvä Checkout component anyway, so it's a no-op cost for Hyvä stores and a one-time install for plain Open Source stores.

#### Migration

```
composer update etechflow/module-delivery-date
bin/magento setup:upgrade
bin/magento setup:di:compile
## Restart php-fpm to clear OPcache (mandatory on production with opcache.validate_timestamps=0)
```

---

### [1.4.0] — 2026-05-19 — Magewire-native date picker for Hyvä Checkout

First true Magewire (server-state) date picker in the eTechFlow suite. State now lives on the server and round-trips via wire:click / wire:model.live — distinct from the existing Alpine-only picker which continues to ship for non-Hyvä-Checkout installs.

This release positions DD as a **Hyvä-first** module, not "Hyvä compatible". Most competitors' Hyvä Checkout integration is a bolt-on Alpine block; ours is now a proper Magewire component.

#### Added

_(Changelog truncated for .md surface. Full history on https://packagento.com/etechflow/module-delivery-date.)_

## Recent Versions

| Version | Released |
|---|---|
| 1.6.0 | 2026-06-06 |
| 1.5.1 | 2026-06-03 |
| 1.5.0 | 2026-06-02 |
| 1.4.3 | 2026-05-22 |
| 1.4.2 | 2026-05-21 |
| 1.4.1 | 2026-05-20 |

## Dependencies

### Require

| Package | Constraint |
|---|---|
| magento/framework | ^103.0\|\|^104.0 |
| magento/module-catalog | ^104.0\|\|^105.0 |
| magento/module-checkout | ^100.4\|\|^101.0 |
| magento/module-config | ^101.2\|\|^102.0 |
| magento/module-customer | ^103.0\|\|^104.0 |
| magento/module-quote | ^101.2\|\|^102.0 |
| magento/module-sales | ^103.0\|\|^104.0 |
| magento/module-shipping | ^100.4\|\|^101.0 |
| magento/module-store | ^101.1\|\|^102.0 |
| magewirephp/magewire | ^1.0\|\|^2.0 |
| php | ~8.1.0\|\|~8.2.0\|\|~8.3.0\|\|~8.4.0 |

### Suggest

| Package | Constraint |
|---|---|
| etechflow/module-backorder-eta-display | Pair with BED so the calendar's earliest available day respects per-product restock dates. |
| etechflow/module-next-day-eligibility | Pair with NDE to hide next-day delivery options on ineligible carts automatically. |
| etechflow/module-shipping-table-rates | Pair with STR to filter delivery days by carrier lead time. |
| hyva-themes/magento2-default-theme | Hyvä Theme support is first-class — install Hyvä to enable the native Alpine.js calendar (no extra config). |
| hyva-themes/magento2-hyva-checkout | v1.4+: Magewire-native date picker activates on Hyvä Checkout pages — server-state calendar, wire:click date selection, wire:model.live slot dropdown. Falls back to the Alpine picker if not installed. |

## Quality

Latest release (1.6.0) fails the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers.


### Compatibility

Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | Pass | Pass | – | – |
| 2.4.8 | – | Pass | Pass | – |
| 2.4.9 | – | – | Pass | not tested |


### Code Quality

Advisory checks against the module's source. Never affect the Compatibility verdict — a phpcs finding can't make a module incompatible.

#### Static Analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 343 | 6 errors, 337 warnings (ruleset: Magento2) — 161 auto-fixable with phpcbf |
| PHPMD | Warning | 152 | 152 rule violations (MissingImport:92, NPathComplexity:14, CyclomaticComplexity:13, UnusedFormalParameter:9, TooManyPublicMethods:7) |
| Cpd | Warning | 8 | 8 duplicated chunks spanning 104 total lines (min-lines=5, min-tokens=70) |
| Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) |

#### PHPStan

Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases.

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | 39 | 39 | – | – |
| 2.4.8 | – | 39 | 39 | – |
| 2.4.9 | – | – | 39 | N/A |


### Tests

Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately.

#### Unit Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |

#### Integration Tests

| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | – | – |
| 2.4.8 | – | N/A | N/A | – |
| 2.4.9 | – | – | N/A | N/A |


### Security

Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright.

| Tool | Status | Findings | Summary |
|---|---|---|---|
| Composer audit | Pass | 0 |  |
| Malware scan | Pass | 0 |  |

## Licence and pricing

Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step.

Refundable within 14 days of first purchase via https://packagento.com/account/refunds/.

## Install via Claude Code or any MCP client

The Packagento MCP server can run the licence + project + Composer steps above in one tool call:

```
purchase_and_install_packages(
  composer_names=["etechflow/module-delivery-date"],
  project_id="proj_xxx"
)
```

This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup.

## Vendor

etechflow is a Magento 2 vendor on Packagento. See https://packagento.com/etechflow.md for their full catalogue.