Occasion Reminders
Help customers remember the next occasion.
Uses dates and preferences customers have given you to invite a repeat order a set time before each occasion. Every invitation is built from current products and delivery cutoffs, and only customers who opted in receive one.
A real customer situation
A customer opted in to an anniversary reminder two weeks before the date and ordered a garden rose bouquet last year. This year the owner wants to remind her in time, suggest what is actually in stock within her stated budget, and not send a reminder if she has already ordered.
Where the owner wants to be
Opted-in customers get one timely, accurate invitation per occasion, can reorder in a few taps, and the next reminder date is set automatically. Changed dates, existing orders and opt-outs are respected without anyone checking a spreadsheet.
What it handles
- Calculates reminder dates from customer-provided occasions and lead times, and reschedules when a date changes
- Suppresses the invitation when an order for that occasion already exists
- Suggests in-stock products within the stated budget, with alternatives when last year’s item is unavailable
- Rechecks stock and delivery cutoff at checkout and offers collection when delivery is closed
- Records the order, the delivery or collection request and the next reminder date
What it deliberately does not do
- Never reminds anyone without an explicit opt-in; opt-out removes future eligibility
- Reuses stated preferences and order history only — no inferred personal details
- Sends one invitation per occasion and does not chase
Interactive demo
Try it with sample data
No sign-up needed. Pick a scenario, change the inputs, then play the customer and the owner. The right-hand panel only shows what the workflow actually recorded.
Interactive simulation using a sample customer, catalogue and delivery calendar. No reminder is sent, no order is placed and no payment is taken.
Choose a scenario
Opted in, reminder two weeks before, previous bouquet in stock.
Today is Mon 5 Oct 2026 in the simulation.
Off = the Garden rose bouquet is unavailable.
Reply arrives after 2pm the day before the occasion.
0 = unchanged. Otherwise the customer updates the date at the reminder.
Customer side · Reminder email and replies
Press “Run scenario” to start. Every message and record here comes from sample data.
Workflow and harness
How Occasion Reminders runs
Reference schematic for the proposed workflow. Blue steps do the work, purple paths handle exceptions and returns, and amber checks are the harness controls that a step cannot pass without.
Overview — business stages
Read the full flow as text
- Saved occasion approaches (business step)
Reminder date = occasion − stated lead time. Output: Scheduled reminder. Leads to: Check preference and existing order. - Check preference and existing order (business step)
Opt-in active; no order for this occasion. Output: Eligible reminder. Leads to: Select available products; Already ordered. - Select available products (business step)
In stock and in band; previous item first if available. Output: Invitation with up to 3 products. Leads to: Customer chooses or updates date. - Customer chooses or updates date (business step)
Choice must be an offered product. Output: Selected product or changed preference. Leads to: Validate delivery and checkout; Occasion date changed; Opted out. - Validate delivery and checkout (business step)
Recheck stock and cutoff; sample checkout. Output: Payment reference. Leads to: Record order and next reminder; Cutoff missed. - Record order and next reminder (business step)
One order per occasion; next reminder next year. Output: Order, fulfilment request, next reminder date. - Already ordered (exception or return path)
Suppress invitation. Output: Stop; next reminder next year. - Occasion date changed (exception or return path)
Save date; recalculate reminder. Output: Rescheduled reminder. Leads to: Saved occasion approaches (reschedule). - Opted out (exception or return path)
Delete future eligibility. Output: No further reminders. - Cutoff missed (exception or return path)
Offer collection or no order. Output: Alternative fulfilment. Leads to: Select available products (alternative fulfilment). - Permission and duplicate check (harness check)
Explicit opt-in; one order per occasion. Output: Allow / suppress. Leads to: Check preference and existing order (required check). - Current stock (harness check)
Only in-stock items offered or sold. Output: Available product list. Leads to: Select available products (required check). - Delivery cutoff (harness check)
Delivery orders by 2pm the day before. Output: Delivery allowed / blocked. Leads to: Validate delivery and checkout (required check).
Harness controls
- Explicit reminder permission checked before scheduling and before sending
- Date accuracy: only customer-provided dates; changes reschedule the reminder
- Current availability checked when suggesting and again at checkout
- Delivery cutoff enforced; collection offered as the alternative
- Duplicate-order suppression per occasion
Systems and data
Production uses customer preferences, occasion dates, the catalogue, a delivery calendar and checkout. The demo uses a sample customer and catalogue, an outbox that holds the reminder and a sandbox checkout event.
Demo boundary
External calls, customer messages, payments and business writes use synthetic fixtures and an on-screen outbox. The demo shows only verified demo state. Custom production connections are a paid implementation deliverable.
What gets delivered
The records your business receives
Reorder receipt
Product, price, delivery or collection date, sample payment reference and order number.
Delivery or collection request
A request on the delivery calendar or collection list for the occasion date, linked to the order.
Saved occasion record
Customer-provided date, lead time, stated budget band, permission status and the next reminder date.
Custom deployment
Configured for your business during a paid implementation. Integrations are confirmed during discovery, never assumed.
Your business rules
- Which occasions you remind for and the lead times offered
- Budget bands and which products may be suggested
- Delivery cutoffs, delivery areas and collection hours
- Opt-in wording and how opt-outs are recorded
Systems we connect
Measurement
We measure completed business against a baseline, not messages sent. No results are promised before discovery.
Business results
- Completed repeat occasion orders
- Contribution after discounts
- Share of reminders that convert to an order
Operational reliability
- Reminders sent without an opt-in (target: zero)
- Invitations sent when an occasion order already exists (target: zero)
- Orders accepted after the delivery cutoff for delivery (target: zero)
Want this reminding your own customers before their occasions?
Book a call about Occasion Reminders. We start with discovery: your current process, volumes, systems and who handles exceptions. The proposal then defines the integrations, approvals and acceptance tests before anything goes live.