ppl / module-dev-create-store

ppl/module-dev-create-store

PPL Dev Tool add-on for creating repeatable Magento 2 development store setup data and configuration.

magento2-module Compatibility: 2.4.7-2.4.9 Code Quality: Warning Tests: N/A Security: Pass proprietary

PPL Dev Create Store for Magento 2

PPL Dev Create Store creates or completes a repeatable Magento development store baseline for checkout, catalog, tax, demo, and smoke-test work.

What It Adds

  • Store setup workflow for local and QA environments
  • Baseline configuration for catalog, customer, directory, offline payment, store, and tax testing
  • Foundation data for later product, customer, and order generation

Requirements And Dependencies

  • PHP: >=8.1
  • Magento packages: magento/framework, magento/module-backend, magento/module-catalog, magento/module-config, magento/module-directory, magento/module-eav, magento/module-offline-payments, magento/module-store, magento/module-tax
  • PPL packages: ppl/module-dev-tool

Installation

Composer installation:

composer require ppl/module-dev-create-store
bin/magento module:enable Ppl_Hub Ppl_DevTool Ppl_DevCreateStore
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:clean

Manual app/code installation: copy the module to app/code/Ppl/DevCreateStore, install the dependencies listed above, then run the same Magento commands without the Composer step.

First Use

  • Install Ppl_DevTool and Ppl_Hub first.
  • Review the generated configuration options before running in any shared environment.
  • Use Ppl_DevCreateTaxes for richer country VAT presets and dedicated tax workflows.

Admin entry: PPL Hub > PPL Dev Tool > Create Store.

Integrations And Boundaries

  • Works with Ppl_DevCreateTaxes and Ppl_DevQuickSetup for fuller scenario setup.
  • Intended for development, QA, demo, or disposable staging environments. Do not treat generated data as production merchant data.

Localization

The package includes translation CSV files for 12 locales: de_DE, en_US, es_ES, fr_FR, it_IT, ja_JP, nl_NL, pl_PL, pt_BR, ru_RU, tr_TR, zh_CN.

Documentation

  • Screenshot inventory: docs/images/ppl-dev-create-store/ in the repository documentation tree

Support

Support contact: [email protected]. Include the module version, Magento version, enabled PPL companion modules, and the relevant admin or storefront screenshot when reporting an issue.

Changelog

1.2.0

  • Adapted to the updated PPL Hub: admin navigation, ACL, and menu integration aligned to the PPL Hub 1.2 line
  • Minor fixes and stability improvements

1.0.0

  • Initial release.
  • Scaffold a complete Magento store structure (website, store group, store view, root and child categories, tax classes) on demand.
Versions
Version Stability QA Status Compatibility Released
1.2.0 stable Pass Magento 2.4.7-2.4.9 Details 2026-07-07 14:12:03

Requires 14

Package Constraint
magento/framework >=103.0.0 <104.0.0
magento/module-backend >=102.0.0 <103.0.0
magento/module-catalog >=104.0.0 <105.0.0
magento/module-config >=101.2.0 <102.0.0
magento/module-directory >=100.4.0 <101.0.0
magento/module-eav >=102.1.0 <103.0.0
magento/module-offline-payments >=100.4.0 <101.0.0
magento/module-store >=101.1.0 <102.0.0
magento/module-tax >=100.4.0 <101.0.0
php >=8.1
ppl/module-dev-tool ^1.2
ppl/module-hub ^1.2
psr/log ^1.0 || ^2.0 || ^3.0
symfony/console ^6.4 || ^7.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.

Compatibility matrix (Magento × PHP)
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 Pass

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.

Static analysis results
Tool Status Findings Summary
PHPCS Pass 0
PHPMD Warning 5 5 rule violations (ExcessiveClassLength:1, TooManyMethods:1, ExcessiveClassComplexity:1, ExcessiveParameterList:1, ExcessiveMethodLength:1)
Cpd Pass 0
Composer validate Info 1 valid; 1 advisory note (composer validate --strict)

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.

PHPStan results by Magento and PHP version
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 Pass

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

Unit tests results by Magento and PHP version
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

Integration tests results by Magento and PHP version
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.

Security results
Tool Status Findings Summary
Composer audit N/A 0 no resolvable dependency tree to audit: Your requirements could not be resolved to an installable set of packages. Problem 1
Malware scan Pass 0
License
proprietary

More from Pawel Pliousnin Digital Solutions

View vendor
Make it pay

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.