Originally written by Will Miller, last updated Mar 17, 2026, on the Swan Retail knowledge base (SRS).
This program is used to set up and maintain email actions used within customer ordering / sales order processing, customer service and statements.
To configure the email system, visit the Email tab within Company Maintenance.
Standard Menu Location: System Administration > System Maintenance > Email Action Maintenance
Searching
Clicking the Lookup button allows you to search for a specific email action.
Creation and Editing
Double clicking the email action or clicking the New or Edit buttons, opens the screen email action window:
|
Field |
Details |
|---|---|
|
Action code |
Action Code Cannot edit for existing email actions |
|
Action type |
Choose from the list in the table below. |
|
Action description |
Describe the primary use of the action such as ‘Goods in Notification’ or ‘Request for payment’ |
|
Email from address |
Email from address, e.g. noreply@company.com. It is possible to include a name in the email from address, e.g.” RetailersRus” orders@swanretail.co.uk Basic validity checks will be done on the format and the user notified if it’s invalid. This is not using an external validation service. |
|
Email copy (bcc) address |
Email address(es) to bcc the outgoing emails to. May be blank for no copy. BCC is a blind copy to address and is not visible to the recipient. Multiple email addresses may be specified – email addresses should be separated with a semi colon (;). |
|
Email subject |
Email subject line shown to recipients. It is possible to include Message Merge Fields depending on the action type chosen. |
|
Email body text |
Free format body text that can include HTML for a rich-formatted email. It is possible to include Message Merge Fields depending on the action type chosen. |
|
Email body URL |
No longer used, please embed html in the body text. |
|
Email attachment URL |
Where applicable, use the Browse button to look-up the folder containing the attachment to include in the email. This will be sent to the customer as an additional attachment to the email. |
|
Action type default |
Check if this is the default for the action type. Only one action can be the default for a type. If the sending program allows the user to select which email action to use they will be presented with the default first, therefore this should be ticked for the most commonly used email action. |
|
Email message override |
Check if the message text may be overridden by the user when sending the message. Sometimes this is necessary if the information is not stored in SRS and cannot be merged or if you want staff to provide a custom message. |
Action Types
|
· General |
Available within Customer Emails |
|
· Marketing |
Future Use |
|
· Option statement |
Available within Statement Print |
|
· Sundry statement |
Used in Statement Print |
|
· Purchase order |
This process uses a tiered approach to establish the sending email account. Please refer to the Purchase Order Emailing how to guide. |
|
· Supplier returns |
|
|
· Remittance advice |
Future Use |
|
· Non specific |
Applies to all. Use for Web email. |
|
· Sales order |
Available within Sales Order Enquiry and Sales Order Control Centre |
|
· Sales order line |
Used in Sales Order Control Centre |
|
· Deliverable orders |
Available within Deliverable Sales Orders |
|
· Sales order delivery schedule |
Used in Sales Order Delivery Schedule and Quick Delivery Confirmation |
|
· Sales order delivery confirmation |
Future Use |
|
· Customer service incident |
Available within Customer Service and Sales Prospects programs. |
|
· Customer service action |
Available within Customer Service |
|
· Sales order email |
|
|
· Customer service supplier |
Available within Customer Service |
The Statement Print only uses the CustomerAccountNumber, Title, CustomerInitials, CustomerSurname, CustomerName and AccountType merge fields
Only one Option Statements, Sundry Statements, Purchase Order and Remittance Advice action type is permitted.
Message Merge Fields
Within the message it is possible to set merge fields to merge in data when emails are sent.
All merge fields must be within double square brackets as in the example below
Dear [[Title]] [[CustomerSurname]] your order number [[SalesOrderNumber]] is ready for collection.
When sending this would be merged as:
Dear Mr Smith, your order number 456 is ready for collection.
A list of merge fields is available here Email Merge Fields
Deletion
To delete a row, select the row to be deleted first, then press the Delete button. The system will require confirmation before the selected email action will be deleted.
This is one of the few areas in the system where used messages can be deleted as any sent messages are stored separately. This also means you can update existing without having an effect on records of historical sent emails.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article