inpost / magento2-module-restrictions
Module allows for configuration of restrictions for products not handled by InPost Pay.
Product Restrictions for InPost Pay Integration
Module adds possibility to restrict products from sale in general or for certain delivery types when carts are bound with InPost Pay Mobile App.
License
- This plugin is licensed under the Creative Commons BY-NC-ND 4.0 License.
- You are free to use this plugin in its original, unmodified form for non-commercial purposes only.
- Redistribution, modification, and commercial use are strictly prohibited.
- License details: http://creativecommons.org/licenses/by-nc-nd/4.0/
Compatibility
- Magento Community 2.4.6
- Not tested in other versions
Installation
To enable this extension run following commands:
bin/magento module:enable InPost_Restrictionsbin/magento setup:upgrade
Changelog
All notable changes to this project will be documented in this file.
[2.0.0] - 2025-01-17
Fixed
- Fixed modules dependencies by moving custom logger injection from InPost_Restriction module to InPost_InPostPay module
[1.0.8] - 2024-09-05
Added
- Configuration that allows to set up CRON process for refreshing restricted products list
- CRON job that deletes and regenerates all products restricted by configured restriction rules
[1.0.7] - 2024-08-08
Added
- Configuration that separates delivery methods for restrictions allowing to restrict for example only pickup points
Changed
- Data sent to InPost Pay API - reduced available deliveries if basket item is restricted
- Data sent to InPost Pay API - information about product allowed delivery methods
[1.0.0]
- Initial version
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| v2.7.1 | stable | Not tested | Not yet tested Details | 2026-04-10 08:11:27 |
| v2.7.0 | stable | Not tested | Not yet tested Details | 2026-04-10 08:11:27 |
| 2.4.2 | stable | Not tested | Not yet tested Details | 2026-03-24 21:06:59 |
| v2.6.2 | stable | Not tested | Not yet tested Details | 2026-02-10 12:53:58 |
| v2.6.1 | stable | Not tested | Not yet tested Details | 2026-02-10 12:53:58 |
| v2.6.0 | stable | Not tested | Not yet tested Details | 2026-02-10 12:53:58 |
| 2.5.0 | stable | Pass | Magento 2.4.7-2.4.9 Details | 2026-01-29 16:06:04 |
| 2.4.1 | stable | Not tested | Not yet tested Details | 2025-11-26 13:06:20 |
| 2.4.0 | stable | Not tested | Not yet tested Details | 2025-11-04 09:33:51 |
| 2.3.1 | stable | Not tested | Not yet tested Details | 2025-10-22 17:31:08 |
| 2.3.0 | stable | Not tested | Not yet tested Details | 2025-10-01 20:08:03 |
| 2.2.3 | stable | Not tested | Not yet tested Details | 2025-08-25 10:00:42 |
| 2.2.2 | stable | Not tested | Not yet tested Details | 2025-08-05 21:10:54 |
| 2.2.1 | stable | Not tested | Not yet tested Details | 2025-06-27 08:27:39 |
| 2.2.0 | stable | Not tested | Not yet tested Details | 2025-06-03 13:56:22 |
Requires 6
| Package | Constraint |
|---|---|
| magento/framework | * |
| magento/module-catalog-rule | * |
| magento/module-ui | * |
| monolog/monolog | * |
| php | >=8.1 |
| psr/log | * |
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.
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 inpost
View vendorInPost Pay Magento 2 monorepo — development workspace.
Module integrates InPost Pay Mobile application with Magento store. Implementation for Hyva Checkout
Module integrates InPost Pay Mobile application with Magento store. Implementation for Hyva Theme
Adobe Commerce Support Package for InPost_InPostPay module.
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.