Every notification Digital Florists sends — whether it succeeds or fails — is logged. You can view these logs to check if a customer received their message, investigate failures, and resend notifications when needed.Documentation Index
Fetch the complete documentation index at: https://docs.florists.digital/llms.txt
Use this file to discover all available pages before exploring further.
This page covers features gated by Admin-tier permissions — typically Settings access. Admins have these by default; your administrator can adjust who has them in Settings > Team.
Viewing notification logs
Go to Settings > Notifications > Logs to see a history of all sent notifications. Each log entry shows:| Column | What it shows |
|---|---|
| Type | Email or SMS |
| Status | Sent, Failed, or Blocked |
| Recipient | The email address or phone number |
| Event | Which notification was triggered (e.g., Order Confirmed, Proposal Sent) |
| Timestamp | When the notification was sent |
| Reason | If it failed, a plain-English explanation of what went wrong |
Resending a notification
If a customer didn’t receive a notification, you can resend it:- From the order — open the order, find the notification section, and use the resend option. You can resend the original order confirmation, delivery notification, or any other status notification.
- Send a new message — if you’d rather write something custom, use the Send button to compose a freehand email or SMS linked to the order.
Troubleshooting failed notifications
If a notification shows as Failed, here’s what to check:Email failures
| Problem | What to check |
|---|---|
| Customer email is invalid or missing | Open the customer’s profile and check their email address is correct. Common issues: typos, missing @ symbol, or no email on file. |
| Email sending settings not set up | Your email sending settings may not be set up. Check Settings > Advanced > Email to make sure they’re filled in correctly. |
| Email couldn’t be delivered | The email address may not exist, or the customer’s inbox might be full. Check the address is correct. |
| Email went to spam | Automated emails can end up in spam folders. Ask the customer to check their junk/spam folder and mark your emails as safe. |
SMS failures
| Problem | What to check |
|---|---|
| Phone number is invalid | The number may be incorrectly formatted or not a mobile number. Landlines can’t receive SMS. |
| Phone number is a landline | SMS can only be sent to mobile numbers. Digital Florists validates this before sending. |
| SMS quota exceeded | Your monthly SMS credits may be used up. Check your SMS plan and usage in billing settings. |
| SMS disabled for account | SMS requires an active SMS plan. If you haven’t set one up, SMS notifications won’t send. |
| Text message settings not set up | Your text message service may not be connected. Check your SMS settings or contact support for help. |
Notifications not sending at all
If notifications aren’t firing even though they’re enabled:- Check the event is enabled — go to Settings > Notifications and make sure the event toggle is on for the right channel (email and/or SMS)
- Check customer preferences — the customer may have opted out of notifications on their profile
- Check order preferences — the order may have Disable notifications ticked
- Check order type rules — the notification may be excluded for that order type (e.g., funerals excluded). Check the Advanced settings on the event.
- Check the funeral switch — if it’s a funeral order, the global funeral notification switch in Settings > General > Way of Working may be on
Business notifications (invoices, statements, receipts) bypass most of these checks — they’re mandatory and will always attempt to send.
Understanding notification statuses
| Status | What it means |
|---|---|
| Sent | The notification was The message was sent successfully from your shop. Note that emails can still end up in the customer’s spam folder. |
| Failed | Something went wrong. Check the reason column for details. |
| Blocked | The notification was prevented from sending by a rule — for example, the customer opted out or the order type was excluded. |
Email sending details
For failed email notifications, the log records which email sending settings were used — including the technical details of your email setup. This is useful for diagnosing configuration issues or confirming which email provider sent the message.Common questions
A customer says they didn't receive a notification
A customer says they didn't receive a notification
First, check the notification logs to see if it was sent. If it shows as Sent, the message left Digital Florists successfully — ask the customer to check their spam/junk folder. If it shows as Failed, check the reason and fix the underlying issue. If there’s no log entry at all, the notification event may be disabled or the customer/order preferences may be blocking it.
Can I see exactly what was sent to the customer?
Can I see exactly what was sent to the customer?
Yes. Click any log entry to view the full rendered content — the exact email or text message that was delivered.
How long are logs kept?
How long are logs kept?
Notification logs are kept indefinitely. The logs page defaults to showing the last 3 months, but you can search further back.
Can I export notification logs?
Can I export notification logs?
Notification logs are viewable in your dashboard but not currently exportable as a spreadsheet. If you need a record of a specific notification, click into the log entry and copy the content.
Why did a notification send twice?
Why did a notification send twice?
To avoid sending the same message twice, Digital Florists suppresses immediate duplicates of the same notification. If enough time has passed, or if someone used the resend function, it may send again.
Related
Notifications Overview
How the notification system works and how to enable or disable events.
Events Reference
Every notification event and what triggers it.
Templates & Branding
Edit what your notifications say and how they look.
Automations Logs
View logs for your automated actions.