Duplicate Magento Store View

Duplicate Magento Store View

September 28, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Duplicate Magento Store View

Duplicating Magento Store Views: A Comprehensive Guide

As an experienced Magento developer, I often encounter clients who need to create new store views that inherit all the custom settings from an existing one. This is particularly common in multilingual eCommerce sites where each language requires a separate store view with its own translations and preferences.

The default Magento interface doesn’t provide a built-in feature for duplicating store views, which can lead to time-consuming manual replication of configurations. However, there are several ways to achieve this programmatically or via extensions.

Understanding the Challenge

Let’s first understand what happens when you create a new store view in Magento:

  1. Default Settings: The newly created store view inherits the default values set for the system configuration and product attributes.
  2. Translation Inheritance: By default, Magento uses the ‘Use Website’ setting for category and attribute translations. This means the new store view will initially use the default language (usually English) for these fields.

To overcome this limitation, you need to update all the relevant tables manually or programmatically after creating the new view. This includes:

  • core_config_data: For system-wide settings.
  • catalog_product_entity_varchar, catalog_category_entity_varchar, etc.: For product and category attribute translations.
  • cms_page and related tables: For CMS page content.

Duplicating Store Views Programmatically

The most flexible approach is to write a custom Magento module that duplicates the desired store view. Here’s an outline of the process:

  1. Create a new module: Follow the standard Magento module creation process. You’ll need a registration file, etc/config.xml for configuration, and any necessary controllers or observers.

  2. Identify the tables to update: Determine which database tables contain the data you want to duplicate. For most store view settings, this will be core_config_data.

  3. Fetch the source store view’s values: Use Magento’s API or direct database queries (with caution) to retrieve all the relevant records for the source store view.

  4. Insert into the target store view: Loop through the retrieved data and insert new records for each field in the target store view’s table(s). Be sure to use the appropriate scope_id for the new view.

For example, here’s a basic PHP snippet to duplicate core_config_data records:

foreach ($sourceRecords as $record) {
    $data = [
        'scope' => $targetScopeId,
        'scope_id' => $targetStoreId,
        'path' => $record['path'],
        'value' => $record['value']
    ];
    $installer->getConnection()->insert($installer->getTable('core_config_data'), $data);
}

Using Third-Party Extensions

Several third-party extensions are available to simplify the store view duplication process. Some popular options include:

  1. [Amasty Store Views] (https://www.amasty.com/magento-store-views.html)
  2. [AheadWorks Multi-Language Pack] (https://aheadworks.com/magento-multi-language-pack/)
  3. [MageWorx Magento Multi Currency and Multi Language] (https://mageworx.com/magento-multicurrency-and-multilanguage-extension.html)

These extensions provide user-friendly interfaces for creating new store views with pre-defined settings or by cloning existing ones.

Best Practices

When duplicating store views, consider the following best practices:

  1. Backup your data: Always backup your database before making any significant changes.
  2. Test in a staging environment: Before applying changes to your live site, test them thoroughly in a development or staging environment that mirrors your production setup.
  3. Keep your Magento version up-to-date: Newer versions often include improvements related to store view management.

Conclusion

Duplicating Magento store views is a common requirement for multilingual eCommerce sites. While the default interface doesn’t provide this functionality, you can achieve it programmatically or by using third-party extensions.

Remember, the key tables to focus on are core_config_data for system settings and the various entity_varchar tables for product and category attribute translations. With proper database management, you can efficiently create new store views that inherit all the necessary configurations from an existing one.

For more in-depth tutorials on Magento development, be sure to check out our [Magento Tutorials & How-tos] (https://laravelcompany.com/blog/magento) at LaravelCompany.

Catalog Database Extensions Configuration

Our network