Store Copy

🚧

In order to access the Store Copy feature, you need to contact your Shogun Frontend point of contact.

Overview

The Store Copy feature allows you to copy or clone your existing store to a new empty store.

The Store Copy feature is ideal for:

  • Staging Stores

    • Merchants with multiple technical and non-technical team members collaborating on Shogun Frontend.
    • Technical and non-technical team members creating, testing, previewing and sharing store changes in a safe, production-like environment.
  • International Stores

    • Brands investing in a global online presence.
    • Brands selling a similar product catalog in multiple languages and currencies.
    • Technical and non-technical team members seeking to reuse an existing Shogun Frontend store as the foundation for regional stores.
  • Sub-Brand Stores

    • Brands investing in subsidiary brands under an umbrella brand.
    • Technical and non-technical team members tailoring their online brand presence to different segments of their customer base.
    • Technical and non-technical team members seeking to reuse an existing Shogun Frontend store as the foundation for subsidiary brand stores.

πŸ“˜

See Use Cases for more details.

What is not included in the store copy

It's important to note that not everything will be included in the copy process. Below is a list of what will be excluded from a Store Copy:

  • Ecommerce platform data
    • Platform data is not included in the store copy. Rather, when the additional store is set up it will be connected to your ecommerce platform and the data will be synced into the Shogun Frontend CMS via data sync jobs and webhooks.
  • Site Manifest under Store Settings as this is configured per store.
  • GitHub Integration connection. Sections and components will be included in the store copy but you will need to manually connect to your repository if you wish to automatically pull changes from your local development environment.
  • Slack Integration connection.
  • PageMeta Section. Developers generally add site-specific configuration in the PageMeta section so this is not included in the store copy to enable you to retain those site-specific settings.
  • App Component. Developers generally add site-specific configuration in the App component so this is not included in the store copy to enable you to retain those site-specific settings.

Limitations

Store Copy is a broadly executed and destructive action resulting in the content (minus exclusions) of your destination store being entirely overwritten by the content (minus exclusions) of your source store.

Currently, customers can do the following:

  • Copy into a non-live store. A non-live store could be a staging, sandbox, or a newly created regional or sub-brand store.
  • Copy between stores with a shared ecommerce backend.

Currently, customers cannot do the following:

  • Copy into a live store.
  • Copy between stores with a distinct ecommerce backend.
  • Cancel a Store Copy after the action has been initiated.
  • Revert the changes made to any store by the Store Copy.
  • Resolve conflicts between content that is different. If content exists in the destination store it will be overwritten.
  • Maintain Sections or Components with the same name. A Store Copy will overwrite any Section or Component with the same name.

Usage

🚧

Heads up

The destination store will be overwritten by the source store and this process is irreversible.

To get started with Store Copy:

  1. Navigate to frontend.getshogun.com and log in.
  2. Click on the STORE COPY button.
  3. Select the source store from the SOURCE dropdown.
  4. Select the destination store from the DESTINATION dropdown.
  5. Review the content that will be copied. You can cancel this process by clicking on the X button in the top right corner.
  6. Click COPY ITEMS to start the copy process.
  7. Double-check you are copying to the correct store and click on START COPY, or CANCEL to close the confirmation modal and start over.
  8. The Copy process will start and will take a few minutes to be complete depending on the size of your store.

Please reference this checklist of tasks to run through, as it suits your needs, after you conduct a Store Copy:

  1. Manually update your PageMeta Section and App Component if desired, such as if you'd like to use a different Google Analytics tracking ID specific to your new Frontend store.
  2. Manually update your Site Manifest details under Store Settings
  3. Configure your GitHub integration if desired.
  4. Configure your Slack integration if desired.

πŸ“˜

Check our suggested workflows here.

Feature usage

  • Any change made to the source store while a copy is in progress will not be included in the copy.
  • The Store Copy will overwrite anything in the destination store that exists in the source store and leave anything in the destination store that does not exist in the source store.
  • Usage with third-party integrations and tracking IDs
    • As the Store Copy doesn't include the PageMeta Section and App Component, the PageMeta Section or App Component should store environment-specific IDs. For example, rather than storing your GTM ID in a separate component, you should store that ID in the PageMeta Section so that it is not overwritten during a Store Copy. This way you can specify one tracking ID for Staging and another for Production to avoid muddying your production analytics or data. It is important that you QA your store thoroughly after a copy to identify any unintended outcomes.
  • While we are in private beta, you may encounter unanticipated issues requiring manual repair. It is important that you QA your store thoroughly after a copy to identify any unintended outcomes.

What’s Next