Replenishment Email Examples for Consumables and Repeat Purchases

Replenishment works when the message arrives near a real need. A fixed “30 days after purchase” rule can be useful for a uniform consumable, but it is wrong for products used at different rates or bought as gifts.

Build the timing model

Input	Use
Product category	Determines whether replenishment is plausible
Quantity	Changes expected lifetime
Previous purchase interval	Personalizes the estimate
Subscription state	Prevents duplicate reminders
Return or cancellation	Removes false eligibility
Customer snooze	Respects the customer’s timing

Use a confidence window rather than claiming “you are out.”

Example: predictable consumable

Subject: Ready to restock {{product_name}}?

You ordered {{product_name}} on {{last_purchase_date}}. Based on your usual timing, you may be ready for another order.

[Reorder {{product_name}}]

Need more time? Snooze this reminder until {{snooze_options}}.

Example: variable usage

Subject: Need more {{product_name}}?

It has been {{days_since_purchase}} days since your last {{product_name}} order. If you’re running low, you can reorder here; if not, choose a later reminder.

[View reorder options] [Remind me later]

Stop and change rules

Suppress when:

• the customer buys the product or an active subscription covers it;
• the order is returned, canceled, or refunded;
• the product is unavailable and no equivalent fallback is approved;
• the customer opts out or snoozes;
• a support case indicates a problem with the previous order.

If the customer purchases a different size or quantity, recalculate the next window rather than continuing the old schedule.

Copy choices

Avoid “you must be running out.” Say “you may be ready” unless consumption is directly measured. Include the previous order or product context, a single primary action, and a preference control.

QA checklist

• Timing uses the correct product and quantity.
• Subscription customers are suppressed.
• Returns and refunds remove eligibility.
• Reorder link contains the right variant and quantity.
• Snooze is stored and honored.
• The message is not sent after a support issue.

For product-specific recommendations, see the product recommendation examples.

Estimate a window, not an exact depletion date

If a customer bought two units and previously reordered every 45–60 days, use that history to choose a window. Do not state that the product is empty unless the customer has supplied a direct usage signal. A confidence range is more honest and gives the customer control.

Product behavior	Useful approach	Fallback
Uniform consumable	Quantity and known expected life	Standard reminder window
Variable consumption	Prior intervals and quantity	“Check if you need more”
Gift or occasional item	Avoid automatic replenishment	Product education or no send
Subscription overlap	Read subscription state first	Suppress reminder
Multiple variants	Preserve size, flavor, or configuration	Ask the customer to choose

Keep the reorder path faithful

The CTA should preserve the last eligible variant and quantity but still let the customer edit them. Re-check stock, price, subscription status, delivery region, and any product safety or age rule. If the item changed packaging or formulation, explain the change or route to a comparison page.

Support signals should be first-class suppression events. A customer who reported a defect should receive resolution, not a reminder to buy the same item again. A return or refund should reset the timing model rather than merely pause it.

Measure reorder conversion by timing window, snooze use, repeat purchase interval, returns, support contacts, and opt-outs. A reminder that earns fewer clicks but arrives when the customer actually needs the product is the healthier program.