PHPackages                             magenxcommerce/module-sample-data - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. magenxcommerce/module-sample-data

ActiveMagento2-module[Utility &amp; Helpers](/categories/utility)

magenxcommerce/module-sample-data
=================================

Sample Data fixtures

100.4.1(4y ago)0110OSL-3.0PHPPHP ~7.3.0||~7.4.0

Since Oct 13Pushed 4y ago1 watchersCompare

[ Source](https://github.com/magenxcommerce/module-sample-data)[ Packagist](https://packagist.org/packages/magenxcommerce/module-sample-data)[ RSS](/packages/magenxcommerce-module-sample-data/feed)WikiDiscussions default Synced today

READMEChangelog (10)Dependencies (1)Versions (47)Used By (0)

Magento sample data includes a sample store, complete with more than 250 products (about 200 of them are configurable products), categories, promotional price rules, CMS pages, banners, and so on. Sample data uses the Luma theme on the storefront.

Installing sample data is optional.

Technically, sample data is a set of regular Magento modules, which can be deployed and installed together with the Magento instance, or later in the scope of upgrade.

Deploy Sample Data
------------------

[](#deploy-sample-data)

You can deploy sample data from one of the following sources:

- From the Magento composer repository, optionally using Magento CLI
- From the Magento GitHub repository

If your Magento code base was cloned from the mainline branch, you can use either source of the sample data. If it was cloned from the `develop` branch, use the GitHub repository and choose to get sample data modules from the `develop` branch.

### Deploy Sample Data from Composer Repository

[](#deploy-sample-data-from-composer-repository)

To deploy sample data from the Magento composer repository using Magento CLI:

1. If your Magento instance is already installed, skip this step. Otherwise, in the Magento root directory, run: `# composer install`.
2. In the Magento root directory, run: `# bin/magento sampledata:deploy`. This command collects the dependencies from the `suggest` sections of the `composer.json` files of modules, which suggest to install sample data (like `Magento_Catalog`, `Magento_Sales`, and so on).

To deploy sample data from the Magento composer repository without Magento CLI:

1. Specify sample data packages in the `require` section of the root `composer.json` file, for example:

```
{
    "require": {
        ...
        "magento/module-catalog-sample-data": "{version}",
        "magento/module-configurable-sample-data": "{version}",
        "magento/module-cms-sample-data": "{version}",
        "magento/module-sales-sample-data": "{version}"
        ....
    }
}

```

Where `` is the version of the packages; it should correspond to the version of the Magento instance.

Each package corresponds to a sample data module. The complete list of available modules can be viewed in the \[sample data GitHub repository\] ()

2. To update the dependencies, in the Magento root directory, run: `# composer update`

### Deploy Sample Data from GitHub Repository

[](#deploy-sample-data-from-github-repository)

To deploy sample data from the GitHub repository:

1. Clone sample data from `https://github.com/magento/magento2-sample-data`. If your Magento instance was cloned from the mainline branch, choose the mainline branch when cloning sample data; choose the `develop` branch if Magento was cloned from `develop`.
2. Link the sample data and your Magento instance by running: `# php -f /dev/tools/build-sample-data.php -- --ce-source=""`

Install Sample Data
-------------------

[](#install-sample-data)

Once the sample data is deployed, it will be installed automatically when you install or upgrade your Magento instance by using the command line.

Uninstall Sample Data
---------------------

[](#uninstall-sample-data)

To remove the sample data modules from the code base, run one of the following commands from the Magento root directory:

- If sample data was deployed from the composer repository, run: `# bin/magento sampledata:remove`
- If sample data was deployed from the GitHub repository and linked to your Magento instance, run: `# php -f /dev/tools/build-sample-data.php – --command=unlink --ce-source=""`

To delete all the products and other entities provided by the sample data modules, delete the database and reinstall Magento with a clean database.

Reinstall Sample Data
---------------------

[](#reinstall-sample-data)

If you have deleted certain entities provided by sample data and want to restore them, take the following steps:

1. From the Magento root directory, run the following command: `# bin/magento sampledata:reset`
2. Upgrade Magento as usual.

The deleted sample data entities will be restored. Those entities, which were changed, will preserve these changes and will not be restored to the default view.

Documentation
-------------

[](#documentation)

You can find the more detailed description of sample data manipulation procedures at .

###  Health Score

28

—

LowBetter than 57% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity10

Limited adoption so far

Community4

Small or concentrated contributor base

Maturity63

Established project with proven stability

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

36

Last Release

1616d ago

Major Versions

2.3.0.x-dev → 100.3.02021-10-13

2.3.1.x-dev → 100.3.12021-10-13

2.3.2.x-dev → 100.3.2.x-dev2021-10-13

2.3.7.x-dev → 100.4.1.x-dev2021-10-20

PHP version history (7 changes)2.4.3.x-devPHP ~7.3.0||~7.4.0

2.3.0.x-devPHP ~7.1.3||~7.2.0

2.3.3.x-devPHP ~7.1.3||~7.2.0||~7.3.0

100.2.7.x-devPHP ~7.0.13||~7.1.0||~7.2.0

100.2.6.x-devPHP ~7.0.13|~7.1.0|~7.2.0

100.2.5.x-devPHP ~7.0.13|~7.1.0

100.1.6PHP ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0

### Community

Maintainers

![](https://www.gravatar.com/avatar/652aa98d25f6bb0dbacf7a805a9110b66e83d8222c60ca2d1b20fa31782a81d3?d=identicon)[magenxcommerce](/maintainers/magenxcommerce)

### Embed Badge

![Health badge](/badges/magenxcommerce-module-sample-data/health.svg)

```
[![Health](https://phpackages.com/badges/magenxcommerce-module-sample-data/health.svg)](https://phpackages.com/packages/magenxcommerce-module-sample-data)
```

###  Alternatives

[sllh/composer-versions-check

Checks if packages are up to date to last major versions after update

2352.3M12](/packages/sllh-composer-versions-check)[verbb/buttonbox

A collection of utility field types.

8961.8k](/packages/verbb-buttonbox)[opensoft/rollout-bundle

A Symfony2/3/4 Bundle for opensoft/rollout

42121.8k](/packages/opensoft-rollout-bundle)[armincms/json

A Laravel Nova field.

25146.9k3](/packages/armincms-json)[tomschlick/laravel-linkable

URL binding for Laravel models

2530.5k](/packages/tomschlick-laravel-linkable)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
