As of 13 August 2026, AI can only partly send low-stock alerts.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, power-user skill, and roughly 2 hours until you can act on the result.

   How to actually do it

   1. Open your stock or warehouse system and export a sample containing SKU, product name, location, current stock, update time and any reorder threshold fields.
   2. Write down the threshold for each product or location, the people who should receive alerts, the alert channel and who is allowed to approve a purchase.
   3. Paste the sample fields and rules into the prompt, then ask the chatbot to identify whether your system can provide a live or scheduled data feed without inventing a connector.
   4. Open the automation or workflow product you have chosen and build the rule using the agreed stock and threshold fields, with missing and stale records routed to a human rather than treated as zero.
   5. Configure the alert to include the SKU, location, current stock, threshold, last update time and a link or instruction for the next purchasing step.
   6. Create test records for the ten cases in the prompt, compare every result with the expected rule, and check that the intended colleague receives each test message.
   7. Run the workflow alongside your existing stock checks, compare alerts with the current stock system for a week, and only then retire the manual check if the responsible colleague approves it.

   Prompt

   Design a low-stock alert workflow for a UK business using the information below.
   
   Stock system or data source: [name and how it can be accessed]
   Products or SKU fields available: [list]
   Current stock field: [field name]
   Reorder threshold field or rule: [details]
   Units and locations: [details]
   How often the data updates: [details]
   Alert recipients: [names or roles]
   Alert channel available: [email, Teams, Slack or other]
   Supplier or purchasing process: [details]
   
   Do not invent integrations, stock values, thresholds or delivery guarantees. First state whether the proposed setup can monitor the data source and send alerts directly. Then produce:
   1. The exact low-stock rule, including how to handle zero, missing, duplicated and stale stock records.
   2. A plain alert message containing the SKU, product name, location, current stock, threshold, timestamp and suggested next action.
   3. The implementation steps, naming the data fields and permissions needed.
   4. Ten test cases covering normal stock, stock below threshold, zero stock, missing data, duplicate records, multiple locations and a stale data feed.
   5. A short operating checklist for a colleague to check the workflow each week.
   6. The risks and the parts that still need a human decision before placing an order.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.