Post-Purchase Email for Wine Brands: Tasting Notes, Pairings, and Next Allocations

Wine sells on anticipation, not impulse. The post-purchase moment is when a buyer is most curious about the bottle they just paid for, so this email trades the retailer discount for the winemaker's voice.

Trigger on two events, not one. Fire the shipping email at fulfillment with serving temperature, decant time, and the cellar window. Fire the delivered email 48 hours after the carrier marks it delivered, with tasting notes, a pairing, and the next allocation. In the wine programs we run, two touches roughly double allocation revenue versus a single message.

Skip the discount. Coupons on alcohol trip compliance rules in control states like Pennsylvania and Utah, and they cheapen a vintage the buyer already paid full price for. Offer early access to the next allocation, a complimentary estate tasting, or wine-club priority instead. Scarcity outperforms a percentage off here.

Lead with the vintage and varietal, not the brand. Subject lines like 'Your 2021 Estate Cabernet is on its way' open around 48% on wine lists, against roughly 30% for generic retail post-purchase. The body reads like a sommelier wrote it: serving temp in degrees, a specific pairing (dry-aged ribeye, not 'red meat'), and a drink window with real years attached.

Use one CTA per message. The shipping touch points to the winemaker's notes. The delivered touch points to 'Reserve your fall allocation.' Splitting attention across three buttons cuts clicks on wine emails by about 40% in the audits we have done.

Example copy, shipping touch: Subject: Your 2021 Hollis Hollow Cabernet is on its way Preheader: Decant 30 minutes, serve at 62F, drink now through 2032. Body: 'The 2021 saw a long, cool hangtime. Expect blackcurrant, dried sage, and a graphite edge that softens in the decanter. Pour it beside a dry-aged ribeye. Your tracking number is below.'

Numbers we see on live wine programs: shipping-plus-delivered post-purchase flows open between 45% and 55%, allocation pre-orders from the delivered email convert at 18% to 25% on club lists, and the second touch alone drives about a third of repeat-bottle revenue inside 90 days. Built clean, the email reads like the estate wrote it, not like a promo blast.

The layout uses nested HTML tables, not divs or flex. Outlook and older Gmail render tables, not CSS layout, so every band (header, hero, bottle art, tasting-notes card, CTA, footer) is a table row with explicit width and align attributes. Nothing floats.

Every style sits inline on the element. Gmail strips style blocks for non-Gmail accounts and Android Gmail clips them, so the wine-red hero, the cream body, and the ink text all live as inline CSS. The email looks identical whether the client parses styles or ignores them.

The CTA is a bulletproof VML button for Outlook's Word engine. Outlook 2007 through 365 use Word to render, which drops border-radius and background on a normal anchor. We wrap the button in MSO conditional comments with v:roundrect and v:textbox, so the allocation button stays a filled, rounded wine-red rectangle with a working link in every Outlook build.

Tasting notes, pairing, vintage, ABV, cellar window, and the allocation line are live text, not images. Live text scales on mobile, loads the instant the inbox opens, and stays legible in dark mode. The bottle shot is the only image in the message.

A dark-mode color-scheme meta keeps the label art from inverting. We set meta name='color-scheme' content='light dark' and supported-color-schemes in the head, then pin a light background on the outer table. Apple Mail dark mode and Outlook black themes honor it, so the estate label keeps its real color.

One mobile media query handles the small screen. A single style block scoped to max-width:600px bumps headline and body font sizes, pads the CTA to a 44px tap target, and gives the tasting-notes card breathing room. No framework, no breakpoint soup. Web-font fallbacks load 'Playfair Display' for the headline with Georgia, 'Times New Roman', serif behind it, so even if the custom font fails the email still reads like a wine list.

Copy the rendered HTML. Open your ESP and paste.

In Klaviyo, build the email inside a flow triggered by Placed Order or Fulfilled Order (wine should fire on Fulfilled, once the carrier accepts the package). Drop a single HTML block into a blank template and paste the full file. Then wire the merge tags for your wine data: - First name: {{ person.first_name|default:'wine lover' }} - Bottle just bought: {{ event.extra.line_items.0.name }} - Vintage and varietal: {{ event.extra.line_items.0.variant_name }} (e.g. '2021 Estate Cabernet') - Allocation link: a custom profile property, {{ person|lookup:'Fall Allocation URL' }} - 'Drink responsibly' footer: pull from a universal Klaviyo snippet so every wine template stays compliant.

In Mailchimp, start a campaign and choose Code Your Own, then Paste in code. Mailchimp merge tags use the asterisk-pipe format: *|FNAME|* for first name, *|PRODUCT_TITLE|* and *|PRODUCT_VARIANT|* for the bottle and vintage on ecommerce-connected stores, and *|IF:MC_ALLOCATION|* blocks for conditional allocation copy.

Swap brand, colors, and links before you send. The palette lives in three hexes: primary wine red #6B1F2E, cream #F6F1E7, ink #2A1A1F. Replace the estate logo URL and the bottle image, then point the allocation button and the winemaker-notes link at your real pages.

Test before it goes live. Send to Gmail on web and Android, Apple Mail on iPhone with dark mode on, and Outlook 365 on Windows. Confirm the CTA renders as a real rounded button in Outlook, the bottle image loads, dark mode does not invert the label, and every merge tag resolves to the right buyer, vintage, and allocation URL.