Skip to content

Supply manager

The supply workspace holds the ingredients a branch buys and keeps, and everything that puts them on the shelf: suppliers, orders, deliveries and the invoices that follow.

Section What it holds
Shelf Every ingredient, how much is on hand, and what it is worth
Attention What needs a decision now
Orders Purchase orders, from draft to received
Receiving Goods arriving against an order
Suppliers Who you buy from, and at what price
Invoices What each supplier has billed

Each section carries its own badge, and the badge is counted by the server. If Attention says three, there are three.

Every ingredient the branch holds, in its own unit — kilograms, litres, pieces. Each row shows what is on hand and, if you are allowed to see cost, what that quantity is worth at the current average price.

Tapping an ingredient opens its history: every movement, with a reason, and where it came from.

Some people count ingredients and never see prices. If cost is not yours to see, those fields are blank — not zero.

That distinction matters. Zero would look like a measurement somebody made. Blank says plainly that the number exists and is not yours.

The short list of things that will cost the branch money if nobody looks: ingredients running out, orders that have been sitting in draft, deliveries booked against nothing, invoices that do not match what arrived.

Work this list first. Everything else in the workspace can wait a day.

A purchase order moves through states, and the app shows which one it is in:

State Means
Draft Being written. Nothing is committed
Awaiting approval Over the branch’s threshold — somebody else must say yes
Approved Cleared to send
Sent The supplier has it
Partially received Some of it arrived
Received All of it arrived
Cancelled Called off

Receiving is where an order becomes stock. Record what actually arrived, not what was ordered — those are different facts, and the difference is exactly what you want visible later.

A short delivery, a substitution, a damaged case: record them as they were. The gap between ordered and received is a supplier conversation, and it only exists if somebody wrote it down.

Who you buy from, what they charge, and how that has moved. Price history is what turns “this feels more expensive lately” into a number you can take to a supplier.

What a supplier says you owe, against what you actually received.

We are running low on something. Check Attention first; it is probably already there. Raise a purchase order from the ingredient itself so the unit and supplier come with it.

A delivery arrived. Receive it against its order, and record what actually came. Do it at the door, not at the end of the day — everything in between is being cooked against numbers you know are wrong.

The invoice does not match the delivery. That is what the record is for. The received quantities are what you recorded at the door; the invoice is what the supplier claims. Take the difference to them.

My order is stuck awaiting approval. It is over the branch’s threshold. Whoever holds approval at your branch has to clear it — it will not time out into approved.

I cannot see any prices. Cost is a separate permission and you do not have it. Your branch admin can grant it.

  • Adjust menu-item stock. That is the storekeeper’s ledger, not this one.
  • Approve their own order above the threshold.
  • Pay anybody. Sitora records obligations and settles none of them.
  • Edit a movement. Corrections are new entries, like everywhere else in Sitora.