Sarbacane wird Positive User

Product replenishment reminders: automated reorder alerts

Automatically remind customers to reorder products before they run out, using replenishment cycles and personalized recommendations.

Goal
Encourage repeat sales
Improve conversion and sales
Improve personalization and the customer experience
Industries
B2C
E-commerce
Channels
Automation
E-Mail

Description

Some products have a natural rhythm. A bottle of shampoo lasts about 30 days. A tub of protein powder lasts 90. When a customer buys one of these, you already know roughly when they will need another. This use case turns that knowledge into action. Every day, the system checks which customers are approaching the end of their product usage cycle and sends them a timely, personal reminder to reorder. The email shows the exact product they bought, links straight to the product page, and can include a discount code. No guessing, no generic campaigns. Just the right message at the right moment, based on real purchase data.

Implementation Effort
Impact on a goal

Outcome

Increase recurring revenue and repeat purchases
Deliver proactive, helpful communication at the right moment
Automate reminder timing based on real product usage cycles

How it works in practice

A customer ordered a 30-day product three weeks ago. Today, the system runs its daily check. It looks for completed orders containing products from the Replenishment 30 segment that were delivered 20 days ago, which means the 10-day reminder window has opened. An aggregator calculates how many of these deals the customer has. If the number is greater than zero and the customer has email consent, a personalized email goes out. It shows the product they bought, links to the product page, and optionally offers a discount to make the reorder easy. The same logic runs independently for 90-day products, for 60-day products, for any cycle defined in the product catalog. Each cycle has its own timing, its own segment, its own reminder. The whole thing runs every day without anyone having to touch it.

1

Daily check of product replenishment cycles: Every day at a scheduled time, the system reviews completed deals that match replenishment-defined segments. For example, for Replenishment 30, it looks for deals where the product was delivered 20 days ago, opening a 10-day window before depletion.

2

Aggregator evaluation per contact: An aggregator calculates how many deals a contact has within each replenishment cycle segment, for example Number of products with Replenishment 30. If the value is greater than zero, the contact is approaching the end of that product's usage period and qualifies for a reminder.

3

Consent check: The automation checks that Consent email is TRUE. Only contacts with valid email consent receive the replenishment reminder.

4

Personalized reminder email: If the aggregator value is greater than zero and email consent is confirmed, the system sends a reminder email containing the product name, image, direct product URL, and an optional discount code. The message highlights that the customer is nearing the end of their product cycle and includes a clear CTA to reorder.

5

Separate flows for each replenishment cycle: Each replenishment cycle, such as Replenishment 30 or Replenishment 90, runs as a dedicated automation. This ensures accurate timing and product-specific recommendations for each cycle, reducing errors and keeping every reminder relevant to what the customer actually bought.

How to set it up

Implementing use case automation involves several key steps and tools. Here's a comprehensive ressources to get you started:

Used modules

Automations

Marketing on a new level with a beautiful visual, drag & drop creator.

On date & time
Send Email Campaign

Email Marketing

Send personalized emails that resonate with your users at the perfect moment.

Prerequisities

Set up your own sending domain for email delivery.
Define the Replenishment days attribute for each relevant product in the catalog.
Create product segments for each replenishment cycle, for example Replenishment 30 and Replenishment 90.
Create deal segments that filter only completed orders, excluding cancelled and refunded deals, with the correct Date delivered condition for each cycle.
Configure aggregators that calculate daily how many deals per contact belong to each replenishment segment and save the result as a contact attribute.

Recommended data structure

Contact Attributes

A contact attribute is a data field stored on the contact's profile, used for segmentation, personalization, reporting, and automation.

Attribute name
Attribute type
email
(standard) string
Consent email
(custom) boolean
Replenishment 30
(custom) integer
Replenishment 90
(custom) integer

Product Attributes

A product attribute is a data field describing a property of a product stored on the product profile.

Attribute name
Attribute type
Name
(standard) string
Product URL
(standard) string
Image URL
(standard) string
Replenishment days
(custom) integer

Deal Attributes

A deal represents a specific sales transaction tracked through your CRM pipeline.

Attribute name
Attribute type
stage
(standard) integer
Date delivered
(custom) datetime

Segments

Segments are dynamic groups that update in real time based on contact behavior, product attributes, or deal data.

Segment name
Segment description
Replenishment 30
(product segment) Based on the product attribute Replenishment days = 30
Replenishment 90
(product segment) Based on the product attribute Replenishment days = 90
Replenishment 30 – deals
Deal-Segment: abgeschlossene Deals mit Produkten aus Replenishment 30, Date delivered vor 20 Tagen
Replenishment 90 – deals
Deal-Segment: abgeschlossene Deals mit Produkten aus Replenishment 90, Date delivered vor 80 Tagen

Aggregators

An aggregator collects numerical data from deals or events and saves the result as a contact attribute, updated on a daily schedule.

Aggregators name
Aggregators definition
Number of products with Replenishment 30
The aggregator sums up the deals from a Replenishment 30 segment and saves this number in the contact attribute Replenishment 30. If the value is greater than 0, it means that the contact has a deal from this segment
Number of products with Replenishment 90
The aggregator sums up the deals from a Replenishment 90 segment and saves this number in the contact attribute Replenishment 90. If the value is greater than 0, it means that the contact has a deal from this segment

Warning

Things to take into consideration when leveraging this use-case

Before you go live

Make sure the Date delivered attribute is populated for all completed orders. Without it, the cycle timing calculations cannot run correctly.

The email snippet tag references stage 2 as the completed order stage. Adjust this tag if your pipeline uses a different stage number for completed orders.

Customer review

Trusted by fast-growing teams

„Dank Positive User haben wir nicht nur unsere Kundenbasis erheblich erweitert, sondern auch die Kommunikation optimiert und viele zeitintensive Aufgaben automatisiert. Dieses Tool unterstützt wirklich unsere Vertriebs- und Digitalstrategie.“

Somfy, E-Commerce-Team, Somfy
Read the full customer story

Turn this use case into action

Start from a proven use case designed to help you engage faster, with relevance and impact.

More ways to engage your audience

Double-Opt-in mit Rabatt belohnen

Konforme Zwei-Schritt-Opt-ins, die einen sofortigen Rabatt liefern und die Bestätigungsraten steigern.

Neue Features in-app ankündigen

In-App-Nachrichten, die neue Features präsentieren, sobald Mobile-Nutzer die App öffnen.

Vertriebsaktionen nach Abo-Ende auslösen

Automatische Deal- und Task-Erstellung, die innerhalb weniger Tage Sales auf jedes abgelaufene Abo ansetzt.