Picture of Copy Products Between Storefronts

Copy Products Between Storefronts

Copy Products lets admins quickly duplicate one or more products from a source storefront into another storefront (or within the same storefront) directly from Product Management. The action runs as a queued task and creates new items on the target storefront, so you can keep working while it processes. You’ll choose the destination storefront, set a new name or a prefix for batches, and decide whether the copies are Published or Unpublished. Typical uses include seeding new storefronts, rolling out multi-brand catalogues, creating variant families, and promoting from staging to production. Most product data and assets are copied; however, pricing scripts/Global Additional Data CSVs, some 3D products, and MegaEdit products with preview plugins may require extra setup. Always open and validate the copied products on the recipient storefront before publishing.

Tutorial Video Transcript

A transcript of our tutorial video, ensuring you can find exactly what you need, when you need it.

You can search this page to find the relevant time-stamp in the video. Also, this text can be used as part of the tutorial search feature.

0:01 Copy products lets you duplicate one or more products from a source storefront into another storefront in just a few clicks.
0:10 Additionally, as we always could do, we can also duplicate products into the same storefront that you currently working on. Now this updated version of copy products was introduced in the middle of August 2025, And it's designed to speed up new storefront launches and reduce repetitive setup work this
0:32 capability is enabled by default for all administrative users So what's happening behind the scenes is that the copy runs as a cute task when it's completed the duplicated products appear on the chosen recipient storefront as brand new items they are completely separate from the original storefront Now
0:54 there's quite a few different use cases for this. As I've mentioned, it allows you to launch your storefronts much, much faster.
1:00 It will allow you to create fast variant families on if you're copying on the same storefront while you can also create a multi brand catalog if you're copying between storefronts.
1:12 So you can copy and duplicate a product and just make minor tweaks on a different storefront to update the branding, for example.
1:19 Another option is you could first do pilot products on a staging or test storefront. And then once you're happy with those, you can then scale them to your production So let's take a look at a quick step-by-step implementation guide.
1:35 This is really easy to do. So we start off in our product And what we want to do is to select one or more products that we want to copy either onto this storefront or to a different storefront.
1:51 So I'm just going to select a couple of my products. I'm then going to go to the top right of my screen underneath the action list and I'm going to say copy, products selected.
2:08 So that will just copy these selected products from the list. This will bring up this new interface which allows you to copy between storefronts.
2:22 So the first thing you have to note here, let's go down to settings, is that we've got a product name and So if you just selected a single product, the field becomes the new product name.
2:36 So you can just put whatever you like in there, but will be the entire product name. If you have multiple products selected, then this field is used as a prefix, which is applied to each copied product name.
2:48 So for example, if I go copied, product, test, that will now be added as a prefix to each of those products that is copied onto our new storefront.
3:06 And then selecting the target storefront I want to copy them to, as you can see, one of those options is the current storefront that we have available, so we can keep them within in the same storefront.
3:20 We then have two more options. One is to specify whether these are published by default. My recommendation would be to turn them off, so because we, we should probably do four round of checks to make sure that everything's copied over correctly.
3:35 And then we can copy over the product images as well if you wish to do so. Now as an important little note here, And what this clarifies and identifies is that a lot of the dependencies and resources that are associated with that product will also be copied over to the recipient's storefront if they 
4:00 don't already exist in that storefront. So this includes things like attributes, it includes things like categories that have been created, products that have associated with it, that kind of thing.
4:11 and you must note as well that if that target or recipient storefront has a different configuration, you will need to very carefully check that the copy products have been adjusted accordingly to match that different configuration.
4:30 So I'm just going to go ahead and click We'll give us a running update as to how that is doing but that will also work in the background so we can continue to work.
4:42 So only two products and they're quite simple products here. Now it's worth bearing in mind that in order to be able to do this because we are working between storefronts, you will need to be logged in as a platform administrator.
4:57 Storefronts administrator will not have the ability to access multiple storefronts on your platform. If you are logged in as the platform administrator, when you get into, oh, it will up to this point, you have the ability to switch between storefronts.
5:11 So I'm going to select the recipient storefront, go to my product list, and then search for those particular products. Now we can see the two products have been copied.
5:37 We have our prefix on the names. We can see that our images have been brought over as well. What I'm going to do is just go on edit and just see what kind of information has been brought over.
5:48 So we can see all of the product landing page information has been brought over. This is a multi-part product so I'll just have a little look at the configuration.
6:00 I can see I can see a well that are so as well and I can see as well that associated resources have been copied over as well.
6:09 So for example if I go to the category mappings we can see that category mapping still exists as it did in the original storefront.
6:20 And that's due to the fact that the actual category structure that was required by that Now, as of the first release of this functionality, which is in the middle of August 2025, there are a couple of limitations which need to be aware of, and you need to know when you have to double check what has been
6:44 copied. So most of the product data and related assets, as we've seen, they copy over and are created as brand new records in the recipient storefront.
6:54 However, there are some important limitations. So for example, at the moment pricing scripts and global additional data CSVs, there are limitations with these two elements.
7:05 So you must root carefully review pricing behavior after the copy is completed and reconfigure the storefront where necessary or reconfigure that particular product where necessary.
7:16 Another limitation is 3D products so these may require additional configuration on the recipient storefront after copying and then we also have mega edit products with preview plugins so products that rely on preview plugins can require extra post copy setup.
7:35 Apart from that everything should copy over absolutely fine, however it is still recommended to do careful checks to make Now a few final tips and best practices for this functionality.
7:51 So first of all, batch thoughtfully. So you can copy these in logical sets. So for example by category or by product type, and then validate after each batch.
8:02 So you don't get confused too many products once on the recipient's storefront. That being said, you can copy them all over in large batches if you prefer to do so.
8:14 It's also recommended to name them strategically. So use meaningful prefixes when copying multiple products. So, for example, campaign language or client code, if applicable.
8:27 It's important that if you do notice any exceptions in your particular workflow or your particular copied products, then it is recommended to keep a short internal checklist, so future copies are faster and more reliable.
8:42 And then, finally, I would say that you want to publish intentionally. So whenever you do create one of these copies, I recommend that you start off with an unpublished draft so you don't just copy it as published straight away.
8:55 Make sure you validate it first and then publish it you know it's been finalized.

Incomplete
Guide

Copy Products lets you duplicate one or more products from a source storefront into another storefront (or duplicate within the same storefront) in a few clicks. It’s designed to speed up new-storefront launches and reduce repetitive setup work. This capability is enabled by default for all admin users.

Behind the scenes, the copy runs as a queued task. When it completes, the duplicated product(s) appear on the chosen storefront as new items (separate from the originals).


Use Cases

  • Launch a new storefront fast: Seed a new storefront with a ready-made set of products from an existing site.

  • Multi-brand catalogues: Copy shared products to brand/storefront variants, then adjust branding or pricing as needed.

  • Variant families: Duplicate within the same storefront to create size/finish/language variants quickly.

  • Pilot then scale: Finalise a product on a staging/storefront, then copy to production or other client storefronts.


Current Limitations & What to Double-Check

Most product data and related assets copy over and are created as new records on the recipient storefront. However, there are some important limitations:

  • Pricing scripts & Global Additional Data CSVs: There are limitations with pricing scripts and with CSV files from Global Additional Data. Review pricing behaviour after the copy and reconfigure where necessary.

  • 3D products: These may require additional configuration on the recipient storefront after copying.

  • MegaEdit products with preview plugins: Products that rely on preview plugins can require extra post-copy setup.

Action required: After every copy, check the resulting product(s) on the recipient storefront for accuracy.


Step-by-Step Implementation Guide

  1. Open Product Management
    Go to the storefront that contains the product(s) you want to copy and open Product Management.

  2. Select product(s)
    Tick one or more products in the grid.

    • Tip: Use filters/search to prepare batches. (If you manage very large catalogues, run multiple batches.)

  3. Click “Copy Product (Selected)”
    This opens the Copy Products modal.




  4. Choose the target storefront
    Pick the storefront to receive the product(s).

    • To duplicate within the same storefront, select the current storefront.

  5. Set the name or prefix

    • Single product: the field becomes the new product name.

    • Multiple products: the field is used as a prefix applied to each copied product name (e.g., Spring_OriginalName).

  6. Set Published status
    Decide whether the copies should be created as Published or Unpublished/Draft.




  7. Start the copy
    Click Copy Product. The action is queued; you can continue working while it processes.

  8. Verify on the recipient storefront (critical)
    When the queue finishes, navigate to the target storefront → Product Management and open each copied product to validate configuration.






  9. Repeat for additional storefronts (if needed)
    Each operation copies from one source to one target. Repeat the process for any additional destinations.


Tips & Best Practices

  • Batch thoughtfully: Copy in logical sets (e.g., by category or product type) and validate after each batch.

  • Name strategically: Use meaningful prefixes when copying multiple products (e.g., campaign, language, or client code).

  • Document exceptions: If a specific product type needs extra steps (e.g., 3D/MegaEdit), keep a short internal checklist so future copies are faster and more reliable.

  • Publish intentionally: Consider creating copies as Unpublished/Draft, validate them, then publish when ready.

Video Chapters

Guide to Using the Copy Products Feature

 

1. Introduction to Copy Products 0:01

generated-image-at-00:00:01

  • The Copy Products feature allows duplication of products from one storefront to another or within the same storefront.

  • Introduced in August 2025 to speed up storefront launches and reduce repetitive setup work.

  • Enabled by default for all administrative users.

 

2. Use Cases for Copy Products 0:54

generated-image-at-00:00:54

  • Launch storefronts faster.

  • Create fast variant families within the same storefront.

  • Develop a multi-brand catalog by copying products between storefronts.

  • Pilot products on a staging storefront before scaling to production.

 

3. Step-by-Step Implementation Guide 1:35

generated-image-at-00:01:35

  • Start in the product list and select one or more products to copy.

  • Click on 'Copy Products Selected' in the action list.

 

4. Configuring the Copy Settings 2:08

generated-image-at-00:02:08

  • A new interface will appear for copying products.

  • Set the product name or prefix for multiple products.

  • Choose the target storefront for the copied products.

 

5. Additional Copy Options 3:20

generated-image-at-00:03:20

  • Decide whether to publish the products by default (recommended to keep them unpublished initially).

  • Option to copy product images.

 

6. Understanding Dependencies and Resources 4:00

generated-image-at-00:04:00

  • Dependencies like attributes and categories will also be copied if they don't exist in the target storefront.

  • Check for configuration differences in the target storefront.

 

7. Completing the Copy Process 4:42

generated-image-at-00:04:42

  • The copy process runs in the background, allowing you to continue working.

  • Ensure you are logged in as a platform administrator to access multiple storefronts.

 

8. Verifying Copied Products 5:37

generated-image-at-00:05:37

  • After copying, check the recipient storefront for the new products.

  • Verify that product information and associated resources have been copied correctly.

 

9. Limitations to Be Aware Of 6:44

generated-image-at-00:06:44

  • Some elements like pricing scripts and global additional data CSVs may not copy over correctly.

  • 3D products and mega edit products with preview plugins may require additional configuration.

 

10. Best Practices for Using Copy Products 7:51

generated-image-at-00:07:51

  • Batch products logically (by category or type) and validate after each batch.

  • Use meaningful prefixes for product names.

  • Keep a checklist for exceptions to improve future copying processes.

  • Start with unpublished drafts to validate before publishing.

Link to Loom

https://loom.com/share/fac192bf77ce41e69ba648d0aa9508fb

Alternate Search Terms

how to copy a product to another storefront, duplicate products between storefronts, clone a product in the same storefront, bulk copy catalogue items, copy products from staging to production, replicate products for multi-brand stores, move a product to a different site, copy MegaEdit or 3D product setup, add name prefix when copying products, create unpublished copies to review first