Birthday Email for Coffee Brands

Coffee is a reorder business. Your customer buys a bag every two to four weeks, so a birthday gift lands inside a habit they already have. That is the whole reason this email outperforms a generic birthday blast. It does not interrupt anything. It feeds the cycle.

Trigger. Fire on the birthday date field, once a year, one per profile. The customer enters the date at signup, or Shopify syncs it into the profile. Klaviyo stores it as a custom property. Mailchimp reads the birthday merge field.

Timing. Send seven days before the date, not on the morning of. A bag has to roast, pack, and ship. If the email lands on the birthday itself, the gift shows up four days late, which reads as a miss. Seven days clears roast time and transit, and still lets the customer brew the free bag on the actual morning.

The offer. A free 12oz bag of a featured single-origin beats a 20 percent discount every time in this vertical. A percentage off reads like a sale. A named bag, picked by a named roaster, reads like a gift. Your cost is roughly $4 to $6 in green coffee and packaging against an $18 to $24 subscription. It earns back if the customer renews even once more. Ship one single-use code per profile with a 10-day expiry. For a tea brand, swap the bag for a tin of a featured flush or a three-tea sample flight.

The copy angle. Personal, warm, signed by a real person at the roastery. Pair the offer with a one-line origin note: the farm name and two tasting notes. That detail is what a discount can never do. Avoid "happy birthday from the team." This is the most-forwarded email of the year for a coffee list when it reads like a note from a friend who happens to roast.

CTA. One button, one job. "Claim your birthday bag" to a pre-filled cart or the subscription product page with the code already in the URL. Do not split attention with a second link.

Example subject and preheader. Subject: A birthday bag from Maya Preheader: Your free single-origin is waiting. It expires in 10 days.

Example body line. "Hey {{ first_name|default:'friend' }}, your birthday's in a week. We set aside a 12oz bag of this month's featured single-origin for you. Use BIRTHDAY-XXXX at checkout. It expires in 10 days, because the beans are best fresh."

Compliance. One code per profile prevents sharing and bounds your COGS. Exclude EU profiles if your store has not accounted for VAT on a zero-value gift, or price the item at a nominal cent. Keep email and SMS consent separate. Suppress anyone who unsubscribed before the send.

This template compiles to the HTML Klaviyo and Mailchimp actually send. Nothing in it depends on a client that strips things.

Nested tables, not divs or flex. Every section is a table inside the 600px container table. Flexbox and CSS grid do not exist in Outlook and half of Gmail. Tables work everywhere.

Inline CSS on every element. The compiled output puts its styles inline on each tag. Gmail drops head style blocks for some accounts, and Yahoo has done the same. Inline styles survive both.

Bulletproof VML button. Outlook desktop runs the Word rendering engine, which flattens a normal button into underlined text. The CTA ships as a real v:roundrect wrapped in an mso conditional, with an anchorlock, so Outlook 2016, 2019, and 365 draw an actual colored, clickable rectangle. We verified the VML in the compiled output.

Live text, not image text. The headline, the offer, the code, and the CTA are real characters. Gmail blocks images by default until the recipient allows them. If your headline were an image, half your list would see a blank box. Live text also reads correctly in dark mode and in screen readers.

Dark-mode color-scheme meta. The head carries the color-scheme and supported-color-schemes meta tags, so Apple Mail and Outlook invert backgrounds predictably instead of guess-flipping your cream to a muddy gray. The dashed code box keeps its border in both modes.

One mobile media query. A single max-width:480px block shrinks the headline and the lead font size. More than one media query starts fighting itself in Yahoo and AOL. One is enough.

Web-font fallbacks. The family stack walks down through system fonts: Apple, Segoe UI, Roboto, Helvetica, Arial. Google Fonts load where supported. The layout never depends on a web font arriving.

1. Copy the HTML. Use the compiled HTML when you paste, not the MJML source. Edit the MJML only if you want to change the layout itself.

2. Paste into your ESP. Klaviyo: open the campaign or flow email, switch to Source, or drag in an HTML block, and paste. For a reusable template, go to Email Templates, Create Template, Import HTML. Mailchimp: Create, Email, Code your own, Paste in code. Drop the full document in.

3. Swap brand, palette, links. Replace the logo text or image URL, the three hex values in the head defaults (espresso #2A1D14, cream #F7F1E8, clay #B5532A), and the button link. Point the CTA at the featured single-origin product page or a pre-filled cart.

4. Wire the merge tags. Klaviyo: {{ first_name|default:'friend' }} for the name. For the code, create a unique coupon in Klaviyo Coupons and reference {{ coupon_code }}, or hard-code a single code if your list is small. Link to the subscription product. Pass the code into the checkout URL so the cart opens discounted. Mailchimp: *|FNAME|* for the name. Generate a single-use promo code through your Shopify integration so each recipient gets a unique code. Link to the product URL. For both: hard-code the expiry date in the body text so it reads as a real deadline, not a variable that might render blank.

5. Test before you send. Send a preview to Gmail web, Gmail app, Apple Mail, and Outlook 2019 or 365. Then toggle dark mode on the phone and re-check the code box, the roaster note, and the button. Fix anything that broke, then schedule the send for seven days before each recipient's birthday.