System Generated Emails

CyberStore sends programmed emails in response to account, order, return, payment, and administrative events. Use this section to identify what triggers each message, who receives it, which settings control delivery, and which replacement tags are available to its template.

Customize message headers and HTML bodies in Setup > Email Manager. Configure site-level order-email behavior under Site Manager > Site Configuration > Email, and configure the application-wide SMTP connection in Application Settings.

Messages in this section

Account and security

Orders and quotes

Returns, payments, and administration

The Email Parsing Functions reference describes the date, math, and logical expressions that can be used in supported message bodies.

How message configuration works

Each programmed email has a unique Linkname. CyberStore uses that identity to select the Email Manager record when the associated event occurs. The record controls the configured From, To, CC, and BCC addresses, subject, and HTML body; the individual email topic explains any recipients supplied dynamically by the triggering process.

Replacement tags insert contextual values when CyberStore prepares the message. Tags can be used in the subject or body when the selected email supports them. If a value is unavailable for the current event or account context, the resulting output can be blank.

Test recipient addressing, replacement output, links, and HTML rendering before enabling a message in production. System emails can contain account, address, order, and payment-related information.

Tags available across system emails

The following tags are available to system-generated emails generally. An individual topic may document additional message-specific tags.

Tag	Value
`[CustomerDefaultEmail]`	Email address stored for the Customer.
`[DefaultEmail]`	Default email address configured for the Site.
`[FromAddress]`	From address configured for the selected email.
`[Global]`	Global Message configured under Site Configuration > Email.
`[SendDate]`	Date on which CyberStore sends the email.
`[SendTime]`	Time at which CyberStore sends the email.
`[ToAddress]`	To address resolved for the email.

Customer replacement tags

Most system emails also support Customer context.

Tag	Value
`[CustomerNumber]`	Customer number.
`[CustomerClass]`	CyberStore Customer Class name.
`[CustomerName]`	Customer name.
`[CustomerPhone]`	Customer telephone number.
`[CustomerFax]`	Customer fax number.
`[CustomerContact]`	Customer contact.

For an On File (B2B) Account and Customer, all Customer tags resolve from the Customer record. For a B2C, anonymous, or other Account that is not On File, only [CustomerClass] resolves; the other Customer tags produce blank values.

The Forgot Password email does not support Customer replacement tags.

Before changing a template

Confirm the message’s Linkname so the intended programmed response is being edited.
Review the email-specific topic for its trigger, dynamic recipients, and supported tags.
Keep required operational information in the message even when redesigning the default content.
Use inline CSS and fully qualified image URLs as described in Email Manager.
Send representative B2B and B2C tests when Customer tags are used because their available values differ.