Operations & Daily Work / Solution -15

Reorder stock before it runs out, not after the customer notices.

Bestsellers run out while slow items fill the shelves. Reordering happens from gut feel on a busy afternoon, and supplier lead times are always longer than remembered.

Your point-of-sale or order systemYour inventory systemYour AI agentYour purchasing or accounting systemIllustrative walkthrough
How to solve

What each tool does

Use the tools for your chosen path. Optional advanced tools are identified below.

Your point-of-sale or order system

Responsibility
Hold sales history by item.
What it accomplishes
Real demand, not remembered demand.
What it does
Exposes item-level sales through reports or an API.

Your inventory system

Responsibility
Hold stock on hand and on order.
What it accomplishes
The starting point for every forecast.
What it does
Returns current quantities and open purchase orders.

Your AI agent

Responsibility
Read the connected records and propose an action.
What it accomplishes
A drafted decision with its evidence attached.
What it does
Calls the model you already use through its API, with read access first and write access only to staging fields.

Your purchasing or accounting system

Responsibility
Hold draft purchase orders.
What it accomplishes
Orders ready for a buyer to approve.
What it does
Creates draft purchase orders against existing suppliers.

This walkthrough is for shop owners and buyers who reorder stock by hand.

AI inventory management for small business: forecast, explain, then ask

Most searches for AI inventory management for small business come after a stockout. The bestseller ran out on a Saturday, a customer went elsewhere, and the reorder that should have gone in two weeks ago is now urgent. Meanwhile slow lines sit on shelves because they were reordered on habit.

You do not need a new inventory platform to fix this. Your sales system knows what sold. Your inventory system knows what is on hand and on order. What is missing is someone who looks at both every day, remembers each supplier’s real lead time and notices when demand changes. This workflow gives that job to an AI agent and leaves the buying decision with a person.

1. Connect the agent to sales, stock and purchasing

Your point-of-sale or order system holds item-level sales by day. Your inventory system holds on-hand and on-order quantities. Your purchasing or accounting system holds suppliers and purchase orders. Connect your AI agent to each through an API key or MCP connection under a service user.

Read access is enough for sales and stock. For purchasing, the agent needs permission to create draft purchase orders and nothing more: no approving, sending or editing supplier records. If your system cannot draft without sending, have the agent write proposed orders to a holding file the buyer imports.

Then give the agent the facts it cannot infer:

Supplier: Coastal Goods (synthetic)
quoted lead time: 7 days | actual average from receipts: 11 days
minimum order: 12 units per line | order day: Tuesdays
Item rules:
- Seasonal lines: forecast from same weeks last year, not last month
- Never auto-propose discontinued items
- Safety stock: two weeks of typical sales for top sellers

Actual lead times should come from your own receipt dates. The gap between quoted and actual is often where stockouts come from.

2. What the agent reads, decides and writes back

Every morning, the agent calculates days of cover for each active item: stock on hand plus stock on order, divided by expected daily sales. Expected sales come from recent history, adjusted for seasonality and for any days the item was out of stock, because a stocked-out item shows zero sales that are not zero demand.

It then flags items whose cover is shorter than lead time plus safety stock and drafts an order line with an explanation:

Item: ceramic mug, sage (synthetic)
on hand: 9 | on order: 0 | recent sales: about 4 a day, rising
cover: about 2 days | supplier actual lead time: 11 days
proposed: 48 units (meets minimum, covers lead time + safety stock)
why rising: sales doubled after the item was featured in the window
confidence: medium (short history since the change)

The agent groups lines by supplier, creates one draft purchase order per supplier on that supplier’s order day, and attaches the explanations. It also lists items with far more cover than needed, so the buyer can pause reorders or plan a promotion.

3. The buyer approves every order

The buyer reviews draft orders before they go to suppliers. They can change quantities, remove lines, combine orders or reject the draft entirely. Only the buyer sends the order. Cash, storage space and supplier relationships are judgement calls the agent does not see.

Make the review quick. A good draft shows the explanation next to each line, so the buyer can trust the routine lines and spend their time on the unusual ones, such as a sudden spike or a new item with little history.

Record changes. When the buyer reduces a quantity because “storage is full until the sale ends,” that context helps the next forecast. A note field on the draft order is enough.

4. Advanced path: catch demand shifts and supplier drift

Once routine reorders are working, add two weekly checks. First, demand shifts: items whose sales this week are well outside their normal range, up or down, with a possible reason drawn from what the agent can see, such as a price change or a stockout at the time. A person decides whether the shift is real.

Second, supplier drift: compare promised and actual delivery dates for each supplier over the last few months. If a supplier’s lead times are lengthening, the agent proposes updating the lead time it uses and lists items that would need earlier orders. The buyer approves any change to supplier settings.

You can feed both into your weekly operations report so the owner sees stock risk alongside the rest of the business.

5. Test what should stop it, and measure it

Test with synthetic data: an item that sold nothing for a week because it was out of stock, a seasonal item in its off season, a discontinued item with low stock, a supplier with no receipt history, a single bulk order that spikes sales once, and a supplier note that says “always order double.”

Stop the workflow if it proposes discontinued items, treats stockout periods as zero demand, sends or approves an order, or follows instructions found in supplier notes.

Measure stockout days on top sellers, slow-moving stock value and how long the buyer spends on reordering each week. The aim is fewer empty shelves without more cash tied up in boxes.

Give it a full season before judging. Forecasts built on a few weeks of history will be rough, and the explanations make that roughness visible. If the buyer keeps overriding the same kind of line, such as new items or promotional weeks, write that pattern into the item rules rather than expecting the forecast to guess it.

The workflow at a glance:

  • Reads: item sales history, stock on hand, open orders and real lead times.
  • Decides: days of cover and a proposed order quantity with an explanation.
  • Writes back: draft purchase orders grouped by supplier.
  • Human approval: the buyer edits and sends every order.
  • Never allowed to: approve or send orders, or reorder discontinued items.
  • Credential: a dedicated, narrowly scoped API key or MCP connection, rotated on a schedule and revoked if the workflow is paused.

Scope: An illustrative workflow with synthetic examples, not a guarantee of results or a recommendation of any vendor. The Lean AI Business does not provide implementation services. Start with test records, and keep the manual process available. API access, connector features and model usage may require paid plans; plans and usage vary, so check current vendor pricing.

AI connection: Use the AI model or agent platform you already trust. Connect it to your sales, inventory and purchasing systems through a supported API key or MCP connection with the narrowest scope that works, store the credential in a secrets manager rather than in a prompt, and keep the approval step outside the model.

Better together

How did it go?

Share a useful tweak, a question, or what you learned. Sign in with Google to post; your Google name and profile picture appear with your comment.

Loading comments…