Branding, Notifications, and Email
Company branding, notification profiles, email templates, order email settings, and holidays
Company Branding
Company Branding Settings feed shared branded email and PDF presentation. Keep brand values current before editing individual templates. Operational emails should use the shared branded shell rather than one-off HTML layouts.
Notification Profiles
Notification Profiles define recipients, CC/BCC routing, and operational notification behavior. Use them for alerts that need configurable recipients instead of hard-coding addresses in Apex or LWC.
Examples of notification-driven surfaces:
| Area | Behavior |
|---|---|
| 3PL fulfillment failures | Runtime alert recipients and cooldowns. |
| Order emails | Invoice, payment, and tracking communication routes. |
| Item notifications | Item setup and inventory notification routing. |
| Shared operations alerts | Email shell and recipient consistency. |
Email Templates
The shared template service owns branded template registration and merge fields. Admins can customize template content while preserving the shared layout and merge-field contract.
Use this rule: if an email is operational and should match all other Exodus emails, register or edit it through the shared template path instead of creating a bespoke layout.
Order Email Settings
Order Email Settings control customer-facing communication around invoices, payment links, order notices, and tracking. After changes, send a QA email from a non-production customer record or sandbox-only test record and confirm:
- Subject and branding are correct.
- Recipients and CC/BCC are correct.
- Merge fields render with expected customer/order values.
- Email history is written to the source record.
Holidays
Org Holidays define business-day behavior for workflows that depend on operating calendars. Update holidays before SLA or schedule-sensitive reporting starts using the new period.
Last updated on