home / use cases / back-office operations / inventory-reorder

Reorders drafted the moment stock runs low

Every evening your Aivell reads stock levels and open orders from your own database, spots what has fallen below its reorder point, groups the needs into one order per supplier, drafts the email in the supplier's language, and pauses. You approve from your phone; the order goes out; tomorrow's run remembers it.

Watch the demo

starts when: Every evening at 18:00, on schedule

The problem

Most stockouts are not surprises — they are missed glances. The quantity sat in the database for days, sinking past the reorder point, while the person who usually notices was busy, on holiday, or trusting that someone else had ordered. The customer discovers the gap before you do, and the emergency order arrives with express freight charges and a worse price.

The opposite failure is quieter: reordering by gut feel fills the shelf with capital. The reorder points, the pack sizes, the seasonal doubling before summer — the knowledge exists, but it lives in one buyer’s head and gets applied only when that head has a free evening.

How your Aivell does it

  1. The database is read every evening. At 18:00 the chore checks each item’s stock against its reorder point — and against open orders, so what is already on its way is never ordered twice.
  2. Needs become sensible orders. Items are grouped into one order per supplier, quantities filled up to the maximum level and rounded to pack sizes. Seasonal items get their pre-season boost, visibly marked as such.
  3. Drafts, not dispatches. Each order is written in the supplier’s language and then the chore stops. This is the pause built into the product: the AI prepares, a human decides.
  4. You approve from wherever you are. The drafts arrive on your phone with the reasoning attached. Tap to send, hold to think — the guardrail guarantees no order email can leave without that tap.
  5. The system learns out loud. An item that keeps dipping below its point three weeks in a row is not silently re-ordered harder — Sara gets a note that the reorder point itself needs a look.

The rules in the chore are your buying policy, spelled out once in plain language instead of living in someone’s memory. The guardrails hold the hard lines underneath: database writes confined to the order log, supplier mail confined to the approved list. Between the two, the shelf stays stocked and the decisions stay yours.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · watch stock and reorder ● active

every evening, read stock levels and open orders from the database

anything below its reorder point and not already on order goes on the list

group the list by supplier — one order per supplier, not ten emails

order up to the maximum level, rounded to the supplier's pack size

seasonal items in the two months before their season — double the quantity, but say so

draft each order in the supplier's language and hold it for approval

once approved, send it and record the order so tomorrow doesn't repeat it

the same item low three weeks running — tell Sara the reorder point is wrong

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Schedule runs the stock check every evening
Database reads stock levels and open orders
Email drafts and sends orders to suppliers

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Database Reads the stock and order tables; may write only to the order log. Stock quantities themselves are untouchable.
Email Order mail goes only to suppliers on the approved list. A new supplier address is a human decision, always.

Questions, answered.

Could it flood a supplier with orders by mistake? +

No, for two independent reasons. Every draft pauses for your approval before sending — nothing leaves the building on the AI's own initiative. And each sent order is recorded, so the next evening's run sees it as already on order and moves on.

Our stock lives in an old management system. Will this work? +

If the system has a database the box can reach on your network, yes — the Aivell reads it where it is. No migration, no sync to a cloud inventory tool, no export ritual.

Do suppliers or anyone else see our stock levels and purchase volumes? +

Only what you send them. The analysis happens onboard the box, inside your network — quantities, reorder points and buying patterns are never processed by an outside service. Suppliers see their order and nothing more.

What does approving an order look like in practice? +

The evening run leaves you the drafts — supplier, lines, quantities, why. You look them over on your phone at the kitchen table, tap yes on four, hold the fifth to check with Sara tomorrow. Held drafts wait; they don't expire or auto-send.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee