Recipes / E-commerce & shops

Low-stock and reorder report

A daily report of the SKUs that will run out before your supplier can restock, with draft reorder emails.

Copy-paste prompt

Every day at 7am, load stock and the last 28 days of sales for each SKU from [source], and lead times from [supplier sheet]. Work out the daily sales rate, the days of stock left, and the reorder point (rate × (lead time + [7] safety days)). List every SKU under its reorder point with a suggested quantity that covers [45] days, rounded to the case pack. Draft one email per supplier. Don't send them.

Fill in everything in [square brackets]. Put your approval rules (see the free operator's charter) above it.

What you need

How the agent does it

  1. Load current stock and the last 28 days of unit sales per SKU.
  2. Compute daily sales rate and days of cover = stock / rate.
  3. Reorder point = rate x (lead time + safety days); flag SKUs below it.
  4. Suggest an order quantity to cover [45] days after arrival, rounded to case pack.
  5. Draft one reorder email per supplier, grouping that supplier's SKUs.

What you get

A table of SKUs to reorder (stock, rate, days of cover, lead time, suggested quantity) and draft supplier emails.

ScheduleDaily at 7am.
Needs your approvalPlacing orders, emailing suppliers and changing inventory all need approval. Read-only store access only.
How to check it workedRates use at least 14 days of data; SKUs with fewer days are flagged as 'low data', not guessed.

Common mistakes

Want new jobs like this tested for you? The Agent Operator Club sends members a monthly drop of tested skills (with scripts and sample data), Grok Bot templates and recipes. From $19/month for the first 50 founding members. Join the waitlist.

Setting it up in each agent

In Grok Bot

Ask the Bot to run the prompt once and review the result. Then say "Save the process we just used as a skill called 'Low-stock and reorder report'" and "Create a routine that runs the Low-stock and reorder report skill daily at 7am". Grok Bot's docs say a Bot can own up to 50 routines, schedules must be at least five minutes apart, and you should use Test run before you enable one.

In Meta Muse

Paste the prompt into Muse and ask it to remember the job and run it on the schedule. Muse asks for approval before outbound actions and purchases, so keep the 'don't send' line in the prompt. Before you rely on it, check that Muse can reach the apps this recipe needs.

In ChatGPT Dots

Give your dot the prompt as an ongoing goal and set the schedule. Dots can work between chats and ask for approval before sensitive actions. OpenAI says background work counts toward your plan's allowance, so match the frequency to what you actually need.

Run it by hand once with harmless inputs before you schedule it. A test run does real work.