Notification Settings
Quark Commerce supports multiple notification providers for sending emails and SMS messages to customers.
Managing Providers
Navigate to Settings → Notifications.
Provider Types
| Type | Protocol | Use Cases |
|---|---|---|
| SMTP | Order confirmations, password resets, marketing | |
| Twilio | SMS + Email | Phone verification, order SMS, two-factor auth |
SMTP Provider Fields
| Field | Description |
|---|---|
| Name | Provider display name |
| SMTP Host | Mail server hostname |
| SMTP Port | Mail server port (587, 465, 25) |
| Username | SMTP authentication username |
| Password | SMTP authentication password |
| From Address | Sender email address |
| From Name | Sender display name |
| Use SSL | Enable TLS/SSL |
Twilio Provider Fields
| Field | Description |
|---|---|
| Name | Provider display name |
| Account SID | Twilio account SID |
| Auth Token | Twilio auth token |
| Verify Service SID | Twilio Verify service (for phone verification) |
| From Number | Twilio phone number (for direct SMS) |
Testing
Each provider has a Test button:
- Auth Check — verifies credentials are valid
- Send Test — sends a test message to confirm delivery
Per-Store Assignment
Each store can be assigned specific providers:
- Go to Settings → Stores → Edit Store
- Select SMS Provider and Email Provider from dropdowns
- Save
When sending notifications, the system:
- Checks the store's assigned provider first
- Falls back to priority-based selection if not set
Phone Verification
When Twilio's Verify Service SID is configured:
- Phone verification uses Twilio Verify API (recommended — Twilio manages code generation and delivery)
- Without it, the system generates codes locally and sends them via SMS
Notification Events
Notifications are triggered by various events:
- Password reset emails
- Order confirmation (when implemented via event consumers)
- Phone verification codes
- Custom notifications via the API