Build routines and local reminders

Use App builder > Routines for guided sequences of products, such as a morning skincare routine. Routines are available across the five app characters. They are separate from subscriptions, automatic purchasing and loyalty rewards.

Author a routine

1. Turn on Enable routines, then Add routine. Set Routine title, Time of day and whether to Show this routine.
2. Add steps in the intended order. Give each a Step name and choose its Eligible products using a tag, collection or selected products.
3. Mark genuinely necessary steps as required. Use Keep this step last only for a final step that must remain last.
4. Add an explanation in Why this order? and optional profile matching. Matching needs the corresponding Shopper profile questions and catalogue data.
5. Resolve validation messages, save and reload. If another editor saved a newer revision, reload rather than overwriting an unseen change.
6. Place a Routine teaser section or a supported routine destination so shoppers can reach it. An enabled routine without an entry point is difficult to discover.

Set refill estimates carefully

Under refill settings, enable Show refill estimates only when you can supply meaningful usage assumptions. Configure Uses per day, Amount per use and Amount unit consistently with the product size. Typical days if size is unavailable is a fallback. Without usable size or fallback data, there is no reliable estimate to show.

These are estimates, not medical advice or guarantees. Shoppers can adjust their usage. Reordering uses current product prices and availability; it does not schedule an automatic payment or shipment.

Verify reminders on a phone

The optional Running-low reminder is scheduled locally and requires the shopper's consent and notification permission. Check scheduling, changing the routine and cancelling the reminder on an installed app. Delivery timing is best effort and depends on the operating system.

Account-synced reminders and Live Activities/Live Updates are excluded from the initial offering. Browser previews cannot prove a notification will arrive. Keep ordinary shopping usable when permission is declined, and verify a routine with unavailable products before publishing it.