Picture of Copy Storefront Functionality - What can it copy? What can't it copy?

Copy Storefront Functionality - What can it copy? What can't it copy?

Who can clone, and from where

  • Only Arone-themed storefronts are supported as clone sources. Storefronts on any other theme cannot be cloned and are not listed.
  • Only users with the Clone Storefront permission can clone (Super Admin and Platform Admin by default).
  • The source storefront must also be on the same portal and have status Normal or Test.
  • Cloning happens only when a new storefront is created via Add New Storefront in admin.
  • You cannot clone into an existing storefront.
  • Applying bundles to an existing storefront never clones.
  • The feature can be switched off per environment. When off, the storefront is created normally, without the clone.

What is cloned

  • Selectable options:
    • CSS Override
    • Editable Content
    • Layouts
    • Content Pages (Topics)
    • Message Templates
    • Settings (including MIS settings)
    • Product Attributes
    • Predefined Values
    • Specification Attributes
  • Content Pages, Product Attributes, Predefined Values and Specification Attributes are unticked by default.
  • At least one option must be ticked.
  • Ticking Predefined Values also ticks Product Attributes; a value cannot exist without its attribute.
  • The source's Arone theme settings (colours, fonts, feature images) are always copied, regardless of the options ticked.

What is NOT cloned

  • Products
  • Categories
  • Orders
  • Customers / users
  • Customer roles
  • Custom Content Templates not used by any cloned content. A template is copied only when a cloned Editable Content, Content Page or Message Template uses it.
  • The images behind the storefront avatar and PDF logo settings. The clone keeps pointing at the source's images (follow-up planned).
  • Print locations of predefined values.
  • Tier price adjustments restricted to a customer role the new storefront does not have. These are skipped, because customer roles are not cloned.

Settings copied as-is: check after cloning

With Settings ticked, every setting is copied unchanged. Only the store URL is updated to the new storefront.

  • Credentials and API keys are shared with the source:

    • payment gateways (PayPal, Square, CyberSource, Authorize.Net, etc.)
    • SMTP
    • shipping carriers (FedEx, UPS, USPS)
    • reCAPTCHA
    • social login
    • all MIS logins

    Change them if the new storefront needs its own accounts.

  • Store name and SEO default page title stay the source's until changed.

  • PayPal Standard IPN URL still points to the source storefront.

  • Default email account is the same as the source's.

  • MIS integrations act as the source until reconfigured (customer's responsibility):

    • Webhook registrations (Tharstern, LabelTraxx, Google Merchant) are inherited. Unsubscribing or disconnecting on the clone can remove the source's subscription.
    • PunchOut identity and shared secrets, EDI certificates and Generic MIS webhook secrets are identical to the source's and should be regenerated.
    • The EasyPost carrier mapping still contains the source's storefront reference.

Behaviour to be aware of

  • If CSS Override is not ticked, images in cloned content still load from the source's CSS Override folder. Deleting those files on the source breaks them on the clone.
  • The Appearance, Storefront Type, B2B/B2C and Industry Type choices on Add New Storefront are still applied first. The cloned data is then applied on top.
  • A product attribute that has the same name as one already on the new storefront (e.g. from sample products) is added beside it, not merged.
  • Specification attributes are merged by name.
  • Re-initialising a cloned storefront runs the clone again:
    • anything that came from the source and was edited on the clone is overwritten with the source's values
    • content that exists only on the clone is kept
    • nothing is deleted

Operational

  • A large source can take several minutes to clone.
  • Run clones one at a time; several running at once can time out.
  • A failed clone marks the storefront Initialization Failed. Re-initialise it once the cause is fixed.
Incomplete
Alternate Search Terms
WYSIWYG stands for "What You See Is What You Get" which means that the styling choices made in this editor will be reflected on the front end.