Resend email
Resend is already partially present in the product for billing and couple invite email paths. The next step is to turn email into a proper lifecycle system, not scattered sends.
Email classes
| Class | Examples |
|---|---|
| Transactional | login, invite, billing, export ready, report ready |
| Lifecycle | onboarding, first cabinet, first wear, wishlist reminder |
| Commercial | API key created, quota warning, invoice, plan upgrade |
| Creator | referral conversion, payout estimate, campaign brief |
| Retailer | widget install, catalogue import complete, feed ready |
| Corpus | contribution accepted, correction reviewed |
Build requirements
- Central email event table.
- Template registry.
- Suppression and unsubscribe state.
- User communication preferences.
- Admin preview and test send.
- Delivery/error webhook handling.
- Domain authentication and deliverability checks before serious volume.
Official reference
Guardrail
No marketing broadcast should ship until preferences, unsubscribe behaviour, and suppression are implemented.