mageworx / module-deliverydate-stock-validation
mageworx/module-deliverydate-stock-validation
Delivery Date and Magento MSI integration
Mageworx Stock Validation Plugin for the Delivery Date module
The module allows you to use stock validation (using the MSI Magento module) to suggest the most correct delivery dates.
*Base extension Mageworx Delivery Date is required
Installation
Upload using composer
- Log into Magento server (or switch to) as a user who has permissions to write to the Magento file system.
- Install package using composer:
composer require mageworx/module-deliverydate-stock-validation
Upload by copying code
- Log into Magento server (or switch to) as a user who has permissions to write to the Magento file system.
- Download the "Ready to paste" package from your customer's area, unzip it and upload the 'app' folder to your Magento install dir.
Enable the extension
- Log in to the Magento server as, or switch to, a user who has permissions to write to the Magento file system.
- Go to your Magento install dir:
cd <your Magento install dir>
- And finally, update the database:
php bin/magento setup:upgrade
php bin/magento setup:static-content:deploy
How to use
This plugin allows you to use the setting "Use Product Salable Quantity" in the Magento 2 Delivery date module.
This setting allows you to hide the estimated delivery feature on the product page if the salable quantity of this product equals or less than 0. This setting also hides the delivery date functionality on the checkout if at least one product with salable quantity equals or less than 0 is added to the cart.
This setting can be helpful if you have the integration with any Pre-order extension, which displays the Pre-order button on the products if their salable quantity equals or less than 0 (i.e. out of stock).
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 4
| Package | Constraint |
|---|---|
| magento/framework | >=102 |
| mageworx/module-deliverydate | >=1.13 |
| magento/module-inventory-sales-api | >=1.0 |
| magento/module-inventory-configuration | >=1.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — 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.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
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
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from mageworx
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.