Resend in Practice: Registration, Orders & Notifications

👁 119 reads

Resend is useful for any application that sends emails in response to user actions: registration, purchases, password changes, new comments. We’ve collected the use cases where it works best, and what to watch out for to ensure emails reach inboxes instead of spam folders.

We covered how to send your first email and verify your domain in our Resend tutorial.

Where to Start with Resend

The best first email to move to Resend is the one that most often fails to arrive or generates the most customer complaints. In many applications, that’s password reset or registration confirmation. After migrating one email and verifying it works, you can move others following the same pattern, and you’ll already have common template elements like headers and footers ready.

Before you start, take care of domain configuration: SPF, DKIM, and it’s worth adding DMARC. These are what primarily determine whether emails reach recipients’ inboxes.

Registration and Password Reset Emails

A basic use case for any application with accounts. Emails with activation links and password resets must arrive quickly and reliably, because without them users can’t access the application. Resend sends them with a single API call, and the dashboard shows whether the email was delivered, which saves a lot of searching when someone reports “I didn’t get the email.”

Order Confirmations for E-commerce

An online store sends order confirmations, shipping notifications, and invoices. Emails come from the store’s domain, not from a provider’s address, which builds customer trust. A template built with React Email lets you insert a product list, total amount, and order number into the email.

Application Notifications

New messages in an app, approaching deadlines, ticket status changes. Email notifications bring users back to the application, if they’re specific and don’t arrive too frequently.

Apps Built in Lovable and Similar Tools

Lovable has an official Resend configuration guide on their channel. An application built from a description gets real email sending, not just a form that doesn’t notify anyone. We wrote about building in Lovable in our Lovable tutorial.

Emails That Match Your Brand

You write templates in React Email like page components, with the same logo, colors, and font. Common elements, like the footer, you write once and use in all emails. Changing the company address in the footer is one edit instead of ten.

Diagnosing Delivery Problems

When a customer says an email didn’t arrive, the dashboard shows the status: delivered, rejected, marked as spam. Instead of guessing, you see what happened, and with rejections you know whether the problem is with the recipient’s address or your domain configuration.

Separate Subdomain for Reputation Protection

Resend recommends sending from a separate subdomain. If something goes wrong with your application email reputation, your corporate email won’t suffer when sent from the main domain. It’s a simple decision at the start that saves problems later.

Example: Store with Custom Sending Domain

A small ceramics shop switches from emails sent from a platform address to its own. They add a sending subdomain in Resend, configure SPF, DKIM and DMARC records, and write order confirmation and shipping templates in React Email with the logo and product photo. Customers receive emails from the store’s address, and the owner sees in the dashboard that one customer didn’t receive confirmation because she provided an address with a typo.

In this example, the dashboard with sending history proved most valuable. Instead of replying to the customer “everything works on our end,” the owner saw the typo in the address and could immediately send confirmation to the correct one. Such situations happen in every store, and the ability to check what happened with a specific email turns a frustrating message exchange into one quick response.

What to Watch Out For

• The Transactional plan applies to emails sent in response to user actions, and marketing newsletters are a separate matter that always requires recipient consent.
• Keep your API key on the server, never in page code.
• Deliverability depends on configuration, so DNS records are fundamental.

How to Check If It’s Worth It

The primary measure is the number of customer reports like “I didn’t get the email” before and after moving the sending. Each such report means customer service time, and with password reset emails also a customer who might have given up. The second measure is developer time: a ready-made library and templates as components save work with each new email.

It’s also worth checking the percentage of rejected messages in the dashboard weekly. If it’s growing, you need to look at the quality of addresses in your database.

In all these use cases, one principle works well: transactional email should be short and do one thing. Order confirmation confirms the order, password reset resets the password. Adding promotions and newsletter content to them increases the risk that filters will treat them as advertising and move them outside the inbox.

// read moreResend Setup Guide: API Key, Domain Verification & First EmailGuidesResend Pricing: Free Tier and Pro Plan for Transactional EmailAI ToolsReplit in Practice: Learning to Code, Prototypes & Business ToolsGuides