Price Drop Email Examples for Carted, Viewed, and Favorite Products

A price-drop message is a triggered notification about a product the recipient has shown interest in. It should never be a generic sale announcement disguised as personal alert.

Eligibility by intent

Signal	Example	Copy angle
Carted	Product remained in a cart	“The item in your cart changed price”
Viewed	Repeated product views	“The product you viewed is now lower”
Favorited	Wishlist or saved item	“A saved item changed price”
Purchased	Previous customer	Usually a cross-sell or price-protection policy, not a default alert

Require consent, a valid product relationship, and a freshness window.

Carted example

Subject: The price changed for {{product_name}}

The {{product_name}} in your cart is now {{current_price}}, down from {{previous_price}}.

[Review your cart]

Prices and availability can change again before checkout. Remove the item or update your preferences here: {{preference_url}}.

Viewed or favorited example

Subject: A saved item is now {{current_price}}

{{product_name}} is now {{current_price}}, down from {{previous_price}}. You received this because you viewed or saved it.

[View product]

The message should identify the relationship accurately. Do not say “your cart” for a wishlist event.

Pricing rules

• Use the same currency and tax basis for previous and current price.
• Exclude a temporary display error from the trigger.
• Explain whether shipping, duties, or subscription terms are excluded.
• Do not imply a personal discount when the price changed for everyone.
• Recheck price and availability at send time.

Suppression

Stop after purchase, cart removal when the product is no longer eligible, unsubscribe, product sellout, or a later price correction. Cap repeated alerts for a product so frequent small changes do not become spam.

QA checklist

• Previous and current prices are accurate.
• Product variant is the one the customer viewed or saved.
• The destination page shows the same current price.
• Cart and purchase states suppress the right path.
• Scarcity and urgency are not invented.
• The email explains why it was sent.

For restock-specific alerts, see back-in-stock examples.

Record the price event precisely

A “drop” needs a defensible comparison. Store the previous price, current price, currency, tax basis, variant, effective timestamps, and reason for the change. Exclude a short-lived catalog error or an automatic repricing blip if the business would not honor it at checkout.

For subscriptions, bundles, and member pricing, say what changed: recurring price, one-time price, or an authenticated customer price. Do not compare a member price with a public price unless the recipient is eligible for the member price.

Choose timing by intent

Intent	Timing	Additional check
Carted item	After the price event and cart refresh	Cart still contains the same variant
Favorite item	Soon after the saved-item event	Wishlist is still active
Repeated browse	After the price has remained valid	Browse event is within its lookback window
Broad price change	Campaign or catalog announcement	Do not imply a personal alert

Suppress small repeated changes with a product-level cooldown. If the price rises again before send, render the current state or cancel the alert; never promise a discount that no longer exists.

Make the CTA and record agree

The landing page should show the same variant, currency, price basis, and availability as the message. A cart link should open the affected cart when possible; a product link should preserve the size or color the customer saved. If the item is sold out, route to a waitlist or remove the price claim.

Use a holdout and report purchases, margin, returns, complaints, and price-alert suppression. Price-drop performance is not only a click problem: a high click rate with stale prices damages trust.