Use Cases

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.

Restore Staging with Production - shared backend

16481648

Workflow #1: Restore Staging with Production

  1. Reach out to your Shogun Frontend point of contact to set up your staging store and enable the Store Copy feature.
  2. Use Store Copy to push updates from your Shogun Frontend Production store to your Shogun Frontend Staging store. Your entire Shogun Frontend Staging store will be overwritten with contents from your Shogun Frontend Production store.

❗️

Warning

THIS ACTION CANNOT BE CANCELLED, UNDONE, OR REVERTED!

  1. Manually update the content in your Staging store as needed.
  2. Fully test your Shogun Frontend store before publishing. We offer three tools for this:
    • eXperience Manager Live Preview
    • Preview URL
    • Build errors

🚧

Due to the highly interconnected nature of Shogun Frontend data, a missing or changed piece of data between stores will likely lead to a build error or production bug after you conduct a Store Copy. This scenario is most likely when you have distinct ecommerce backends and will require manual reconfiguration of multiple parts of your Shogun Frontend store.


International Stores

  • Brands investing in a global online presence.
  • Brands selling a similar product catalog in multiple languages and currencies.
  • Technical team members seeking to reuse an existing Shogun Frontend store as the foundation for regional stores.
  • Store Copy should only be used as the mechanism to run the initial copy of your flagship international store to create your regional stores. Beyond that point, Store Copy should not be used as it will overwrite the entire store.
  • Developers can connect separate branches, via the GitHub Integration, to regional stores to manage code differences between the stores

Copy from Flagship to Regional Stores - shared backend

16001600

Workflow #3: Copy from Flagship to Regional Stores

  1. Reach out to your Shogun Frontend point of contact to set up your regional stores and enable the Store Copy feature.
  2. Use Store Copy to push updates from your Shogun Frontend flagship store to your Shogun Frontend regional store. Your entire Shogun Frontend regional store will be overwritten with contents from your Shogun Frontend flagship store.

❗️

Warning

THIS ACTION CANNOT BE CANCELLED, UNDONE, OR REVERTED!

  1. Fully test your Shogun Frontend store before publishing. We offer three tools for this:
    • eXperience Manager Live Preview
    • Preview URL
    • Build errors
  2. Use the GitHub Integration to push code only from one regional store’s local environment to that same region’s Shogun Frontend site. Code pushed to other regional sites will be overwritten if followed by a Store Copy.
  3. Manually update the contents in your Production store as needed.
  4. Complete the build, test, and launch your regional store.

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.

Copy from Umbrella to Sub-Brand Stores - shared backend

16001600

Workflow #4 Copy from Umbrella Store to Sub-Brand Stores

  1. Reach out to your Shogun Frontend point of contact to set up your sub-brand stores and enable the Store Copy feature.
  2. Use Store Copy to push updates from your Shogun Frontend umbrella store to your Shogun Frontend sub-brand store. Your entire Shogun Frontend regional store will be overwritten with contents from your Shogun Frontend flagship store.

❗️

Warning

THIS ACTION CANNOT BE CANCELLED, UNDONE OR REVERTED!

  1. Fully test your Shogun Frontend store before publishing. We offer three tools for this:
    • eXperience Manager Live Preview
    • Preview URL
    • Build errors
  2. Use the the GitHub Integration to push code only from one sub-brand store’s local environment to that same sub-brand’s Shogun Frontend site. Code pushed to other regional sites will be overwritten if followed by a Store Copy.
  3. Manually update the contents in your Staging store as needed.
  4. Complete the build, test, and launch your sub-brand store.