
Onboarding Journeys
Part of Post-purchase customer education journeys
Coordinating education around a likely replenishment date
Education and replenishment answer different questions.
Why Education Should Track the Replenishment Window
Replenishment reminders run on a shipment date, not a campaign calendar. Omnisend triggers its Replenishment Reminder on the Order Fulfilled event, which tracks when an item has shipped, giving a more accurate start for estimating product usage. Education on the same clock reaches the customer while they are still working through the product.
The payoff is commercial and practical. Omnisend lists higher retention—the store stays top of mind when refills fall due—repeat revenue from reorders placed before the product runs out, and a better customer experience because reordering is fast and convenient.
Fixed calendars struggle because timing and message must match the individual. TaxJar notes that the closer messaging and timing fit each customer, the stronger the results, and that one-size-fits-all email marketing is over. Lifecycle nurture programs, from welcome emails to re-engagement campaigns, maintain contact instead of relying on one dated send.
Not every recipient is ready to reorder on cue. Shopify's lead-nurturing guide states that 80% of potential customers who are not ready now will make a purchase within the next 24 months. The refill window is simply when timely content is most useful.
Estimating the Likely Replenishment Date
Start from fulfilment, not the order date. The Order Fulfilled trigger follows shipment, so the usage clock begins when goods are on their way. From that anchor, the estimated replenishment date is the ship date plus the expected days of use.
Order detail shows the size of the job. Omnisend's trigger filters include product quantity, order total and shipping location, alongside product and collection filters. Quantity sets how much the customer has; shipping location affects delivery time.
Past purchase intervals refine the estimate. Omnisend offers a purchase date filter that targets orders fulfilled within a set range. The average gap between a customer's previous orders gives a workable estimate of when the next is due.
Usage rates differ by product, so build the estimate per SKU. CartonCloud configures replenishment at product level, letting each SKU carry its own trigger point, order quantity and unit of measure. Collection or category filters such as moisturisers or coffee beans can group items with similar consumption patterns.
Recent and new orders both need coverage. Omnisend enables retrospective triggering by default, so customers who purchased in the past three weeks receive the reminder; disabling it targets new orders only. Running both catches recent buyers up when a workflow goes live.
Top Factors Influencing Replenishment Date Accuracy
- Shipment Date (Order Fulfilled Event)Primary anchor for usage clock; most accurate starting point
- Past Purchase IntervalsAverage time between previous orders improves estimate reliability
- Product-Specific Usage RatesSKU-level configuration allows tailored replenishment triggers
- Shipping LocationAffects delivery speed and usage start timeline
Structuring Education Before, On and After the Date
Shopify's lead-nurturing stages—awareness, interest, consideration and action—map onto the replenishment timeline. Awareness is the education stage: understand the customer's problem and position the product as a helpful solution through relevant content. Before the estimated date, that means usage guidance rather than a reorder prompt.
Just before the date, focus on recognition. Content that helps a customer tell when a product is running low or nearly used up supports the decision without pressure, and it arrives while the product is still in use. General usage, storage and dosage guidance belongs in this window too.
On the date, make the action easy. Omnisend cites improved customer experience from fast, convenient reordering; its preset reminder includes a dynamic layout with product images, names and buttons linking to product pages. The first product in the customer's order appears in the subject line for personalisation.
After the date, switch to support and feedback. A post-purchase program asks for feedback on the shopping experience, from website usability through to checkout. Order and delivery confirmations suit email: TaxJar cites that 98% of consumers agree email is the best channel for order updates.
Keep the sequence educational, not pushy. Shopify notes that 80% of potential customers who are not ready now will buy within 24 months. Recipients who do not reorder on cue stay in the nurture program and keep receiving useful content until they do.
Automating the Sequence Around the Date
Build the workflow around one anchor event. In Omnisend, create a workflow under Automation, locate Replenishment Reminder and open it to customise the sequence; the trigger is Order Fulfilled. Everything downstream inherits the shipment date as its timing reference.
Filters decide who enters. Omnisend supports targeting by product title, collection title, purchase date range, order total, product quantity and shipping location. It notes that filter labels differ by ecommerce platform, so a WooCommerce store may see product name instead of product title.
Set an exit condition. The default is a placed order, so a customer who buys after entering leaves automatically, preventing irrelevant reminder emails. Other exits suit particular cases: a paused subscription, a return, or a product that cannot currently be replenished.
Personalise the product block dynamically. Omnisend's preset message carries product images, names and buttons linking to product pages; a text item can pull in the product description automatically when description is selected as the data source. TaxJar highlights personalisation and lifecycle nurture as core features of email automation for ecommerce.
Reconciling the Date with Actual Stock and Replenishment Rules
Education should not create demand you cannot fill. CartonCloud's replenishment feature keeps fast-moving pick face locations topped up before they run low, using minimum and maximum stock thresholds, a choice between on-hand and free stock, and automated replenishment based on sale order demand. Check those positions before a reminder wave goes out.
Settings are product specific. CartonCloud lets you tune each SKU's reorder level, order size and unit, and generates a replenishment report identifying locations that need topping up. Pick faces are the locations the team picks from most often, so keeping them stocked protects order flow.
Know what each replenishment order costs. Omniful lists order cost components as procurement administration, documentation and approvals, shipping and freight, and inspection, sorting and goods receipt notes. Carrying cost covers warehouse rental and labour, insurance and depreciation, loss from expiry or obsolescence, and the opportunity cost of cash locked in stock.
The two costs pull against each other. Omniful notes that more frequent orders can cut carrying costs but raise order costs, while fewer orders reduce admin but increase the risk of holding stock. The estimated date should sit where that balance suits the product.
Use dynamic triggers rather than a fixed schedule. Omniful points to real-time demand, sales patterns and expiry dates as triggers that automate restocking intelligently and help avoid both stockouts and overstocking. For a dated or perishable line, expiry can pull the replenishment date earlier than usage alone would.
When stock is short, hold the reorder prompt and keep sending usage and care education, then resume the ask once supply is confirmed. Omniful notes that syncing data across locations, channels and suppliers helps avoid both stockouts and overstocking, freeing up capital while reducing wastage and markdowns.
Reviewing and Adjusting the Cycle
Track outcomes against the estimated date. Omnisend frames replenishment reminders around increased retention, repeat purchases and reduced churn, so measure reorders against the predicted date for each product. A consistent lead or lag tells you whether the interval is wrong or the message timing is wrong.
Adjust at the level where the error sits. If the date is out, change the interval; if the date is right but reorders are flat, change the timing or content. Because reorder levels, order sizes and units are set per SKU, product-level corrections do not disturb the rest of the catalogue.
Seasonality moves usage rates. Omniful notes that demand can spike or slow with the season, so replenishment frequency must stay agile. Shorten or extend the cycle for seasonal lines rather than keeping one interval all year.
Expiry dates work as a dynamic trigger, so dated stock may need a different rhythm from consumables that do not expire. Review product and collection filters, order value and quantity bands, and exit conditions as ranges change.
Filter and trigger settings are not permanent. Omnisend advises disabling retrospective triggering to target new orders only, and platform filter labels can vary, so confirm the filters still match the products and segments you intend. Recheck the workflow after each catalogue or range change.
Key Performance Indicators for Replenishment Campaigns
- Repeat Purchase Rate
- Increased by replenishment reminders (Omnisend)
- Customer Retention
- Higher when refills are anticipated before depletion (Omnisend)
- Email Open Rate for Order Updates
- 98% of consumers prefer email for order confirmations (TaxJar)
- Potential Customers Ready to Buy
- 80% of non-ready customers will purchase within 24 months (Shopify)
Further reading: Replenishment Reminder Automation (support.omnisend.com).



