Articles on: Notifications

Duplicate Email Workflows and Templates to Use Them in Multiple Organizations

Relevant to: Pro, Premium, and Enterprise customers

Creating email workflows and templates one by one from scratch gets repetitive and time-consuming, especially for the merchants with multiple organizations. As these flows generally have the same logo, layout, and similar content, AfterShip allows merchants to duplicate these workflows and templates to be able to use them in other organizations.

Below are a few things to keep in mind before duplicating an email workflow.


You must be a member of the destination organization. If not, you won’t be able to find the organization on the selection list.
To be able to use this feature, your user role should fall into one of these categories: Owner, Admin, Manager, and Member.
If you are copying an order fulfilled/unfulfilled email, please ensure the destination organization is supported with order-level notifications. (Using order API or connecting it with a store).

Steps to duplicate an email workflow

Log in to your AfterShip admin account
Navigate to the Email & SMS tab under Notifications
Choose the email workflow you want to duplicate and click Edit > Duplicate

Rename your duplicate workflow (Optional)
Add the destination organization (i.e., the account where the new flow will be copied to)

You can change the flow’s main trigger based on the shipment status

✍️ Key information

Changes made to the original flow will not be reflected in the duplicate flow once created.
The duplicate flow will be disabled by default, and you need to enable it manually.
The trigger filters associated with the flow will be copied as it is. You can change them later by editing the duplicated flow.
The language settings of the template will also be copied, including the languages created and the default language.
If the original email template includes product recommendations, you must add that section to the duplicate email separately. The setting can't be copied across organizations as it requires store-level customizations.

If you have any questions, feel free to contact our support team.

Updated on: 26/12/2022

Was this article helpful?

Share your feedback


Thank you!