mage-os / module-inventory-reservations-grid
mage-os/module-inventory-reservations-grid
Add a grid with the list of inventory reservations.
MageOS Inventory Reservations Grid
Overview
The MageOS Inventory Reservations Grid module extends Magento's inventory management by providing an admin grid for viewing reservations and additional actions for managing them.
Features
- View all inventory reservations in a structured grid.
- Manually clean compensated reservations (those resolving to zero) similar to Magento’s built-in cron job.
- Mass delete uncompensated reservations, which can be restricted based on ACL rules.
- Configuration to globally disable the mass delete action for all admins.
Installation
Install via Composer:
composer require mage-os/module-inventory-reservations-grid
bin/magento module:enable MageOS_InventoryReservationsGrid
bin/magento setup:upgrade
Usage
Find the new Inventory Reservations report at Stores > Inventory > Reservations.
Configuration
Navigate to Stores > Configuration > Catalog > Inventory > Reservation to find the following setting:
- Allow Delete Mass Action (
cataloginventory/reservation/allow_delete):- If enabled, allows admin users with the appropriate ACL permissions to delete uncompensated reservations.
- Defaults to
0(disabled). - Can be locked via
env.phporconfig.php.
Blocking reservation deletion
Deleting inventory reservations can be a dangerous action that leaves inventory in an inconsistent state, depending on how your system works. This feature is disabled by default.
You can prevent reservation deletion from being enabled at all by running this command. This locks the setting to disabled in your app/etc/env.php.
bin/magento config:set --lock-env cataloginventory/reservation/allow_delete 0
ACL Permissions
The module introduces fine-grained ACL rules to control access:
- View Reservations (
MageOS_InventoryReservationsGrid::view) - Clean Balanced Reservations (
MageOS_InventoryReservationsGrid::clean) - Mass Delete Reservations (
MageOS_InventoryReservationsGrid::delete)
Best Practices
- Use the View-Only Mode: This module allows viewing reservations without enabling deletion actions.
- Be Cautious with Mass Deletion: Removing uncompensated reservations can cause stock inconsistencies; only grant access to users who understand the implications.
- Lock Configuration: disable the mass delete function globally via
env.phporconfig.php, and enable it only in case if there is specific need for using it.
Additional Notes
Magento already runs a cron job (inventory_cleanup_reservations) to clean up compensated reservations. The manual clean button in this module serves as a fallback for scenarios where the cron does not execute properly. However, merchants needing to fix misalignments caused by external system issues can now remove uncompensated reservations where necessary, under controlled permissions.
License
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.0.5 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-05-09 03:32:25 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2026-04-19 20:42:51 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2026-03-27 13:25:18 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2025-10-24 00:16:04 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2025-10-16 12:40:28 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2025-10-07 16:17:15 |
Requires 11
| Package | Constraint |
|---|---|
| magento/framework | ^103.0 |
| magento/module-backend | * |
| magento/module-config | * |
| magento/module-store | * |
| magento/module-customer | * |
| magento/module-catalog | * |
| magento/module-catalog-inventory | * |
| magento/module-inventory | * |
| magento/module-inventory-admin-ui | * |
| magento/module-inventory-reservations-api | * |
| magento/module-inventory-reservations | * |
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 mage-os
View vendorGCP event sinks for mage-os/mageos-async-events
Combine the power of LLM and domain knowledge to improve admin experience though a chatbot UI.
Turn 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.