See which emails the store sends on its own, send broadcasts to your customers through the assistant, and understand bounces and unsubscribes.
Litestore sends order and account emails on its own, sends a few follow-ups automatically, and sends broadcasts to groups of customers when you approve one. Every email goes out through Resend.
The admin has no email page and no template editor. Each email has a fixed design that's part of the store's code, so whoever runs the store changes the wording there. You send broadcasts by asking the assistant, and the address that receives staff alerts is under Settings → Notifications.
Emails the store sends
| Group | Emails |
|---|---|
| Orders | Order confirmation, cancellation |
| Shipping | Shipped with tracking, delivered, ready for pickup, pickup reminder |
| Returns and refunds | Return requested, refund processed |
| Account | Sign-in link, welcome, customer invitation |
| Cart recovery | The abandoned-cart follow-up, and a coupon email if the store has a recovery code |
| Post-purchase | The review request and one reminder |
| Marketing | Win-back emails to lapsed customers, if the store turns them on |
| Collabs and team | Collab approved or rejected, team invitation |
| Gift cards | Gift card issued |
| Staff alerts | New sales, refund requests and other store events, sent to the admin notification email |
Automatic follow-ups
Some emails wait before they go out:
| Follow-up | When it's sent |
|---|---|
| Abandoned cart | 24 hours after the cart goes quiet, for carts of signed-in customers |
| Recovery coupon | Later, only if the store has a recovery coupon code |
| Review request | 3 days after the order is delivered, with one reminder later if no review arrives |
| Signup nudge | 3 days after a customer signs up |
These timings and the coupon codes are fixed defaults in the store's code rather than admin settings, so whoever runs the store changes them. Before Litestore emails a coupon, it checks that the code still works, so a customer never receives a code that has expired or run out.
Broadcasts
A broadcast has a subject and a plain-text body. You ask the assistant to write it, it counts the recipients and shows you the draft, and nothing is sent until you approve it. This needs the autonomy ceiling at Read + Propose + Execute. A broadcast goes to every customer you're allowed to email, or to the lifecycle segments you choose:
new
invited
registered
purchased
repeatRestricted and banned accounts can't be selected. Litestore excludes unsubscribed customers from both the recipient count in the preview and the actual send, so the preview always matches the send.
Delivery log
Litestore writes one row for each email once it reaches its final state, which is either sent or failed. The row records the recipient, the subject and the type, along with the provider's message id, any error, and the order or customer the email belongs to. Litestore keeps these rows for 180 days and then deletes them.
The admin doesn't have a screen for this delivery log. It's meant for checking a specific complaint, such as "was the pickup-ready email for this order sent?", rather than for browsing.
Bounces and complaints
Once you connect the Resend webhook, Litestore responds to delivery problems as follows.
| Event | What Litestore does |
|---|---|
| Spam complaint | Unsubscribes that customer from marketing email. |
| Permanent bounce | Unsubscribes that customer from marketing email. |
| Temporary bounce, such as a full mailbox or a greylisted server | Records it but never removes consent. |
Before sending any marketing email, Litestore checks for unsubscribes, spam complaints and permanent bounces. Temporary bounces don't remove consent because a full mailbox is usually a short-term problem and doesn't mean the customer asked to stop receiving email.
Newsletter providers
The newsletter signup form on the storefront can send signups to one of 7 destinations:
Beehiiv
Klaviyo
Mailchimp
ConvertKit
Buttondown
Loops
your own webhookYou configure them with environment variables, and Litestore uses the first one it finds configured. None of them affect the emails the store sends for orders and accounts.