How it works, step by step

For the branch manager: what happens from the first order at the till to the review at the end of the night.

The six steps

The same steps repeat all day. What the system learns at the end carries into the next shift.

  1. 1. Sales come inFrom your POS or a file
  2. 2. A forecast every 15 minutesFor each prepared item
  3. 3. When it runs out, and what to cookStart, wait or stop
  4. 4. The kitchen gets the taskOn a phone or tablet
  5. 5. It checks what happenedAfter each action's window
  6. 6. It proposes adjustmentsA manager approves
  7. Next shift
  1. Step 1 of 6 · From your POS or a file

    Sales come in

    Every order rung up on your POS reaches 1 Gram, from Foodics or Odoo, or from a sales file you upload. The system knows which prepared items go into each dish, so it knows how much biryani or grilled chicken has been used so far.

    • A file of past sales gives the forecast a starting point from day one
    • Menu items it does not recognise wait in a list until you map them
  2. Step 2 of 6 · For each prepared item

    A forecast every 15 minutes

    For every prepared item, the system forecasts demand for each 15 minutes of the day, with an expected figure and a higher one to be safe. The same weekday in recent weeks carries the most weight.

    • During the shift the forecast is corrected by how fast you are actually selling
    • Each day's forecast is saved as it was, so decisions are later judged on what the system knew at the time
  3. Step 3 of 6 · Start, wait or stop

    When it runs out, and what to cook

    The system rolls ready stock forward minute by minute: what is cooked, what is on the stove, what the forecast will sell and what will expire. From that it finds when an item drops below its safety level and when it runs out, then picks the action: start a batch of a set size by a set time, wait, stop, count first, bring ingredients, or escalate.

    • Batch sizes follow your rules: minimum, maximum and step
    • Food is not cooked so early that it expires before it sells
    • Safety stock shrinks towards closing, so no batch is started that cannot sell
    • During a rush, keeping an item available can come before saving waste

    Example: one item, one evening

    Made-up numbers that show how the decision is reached.

    Chicken biryani

    Example
    • Ready stock with the batch
    • Without a new batch
    • Safety level
    • Forecast demand
    0246810START5:005:306:006:307:007:308:00kg

    Example

    Start · 8 kg · Do before 6:15 PM

    Without it, stock drops below the safety level at 6:40 PM. The batch takes 25 minutes.

    Ready now
    6 kg
    Batch ready
    6:40
    All seven actions on the product page
  4. Step 4 of 6 · On a phone or tablet

    The kitchen gets the task

    Once a manager approves the action, it becomes a task: what, how much and by when. The cook sees it on a phone or tablet, marks it started and completes it with the quantity actually made.

    • Late tasks are flagged
    • An escalation nobody answers within 15 minutes goes to the owner
  5. Step 5 of 6 · After each action's window

    It checks what happened

    When the action's time window has passed, the system compares it with what was really sold, thrown away and left over, and gives it a verdict.

    • Verdicts: correct, neutral, incorrect, ignored or unverifiable
    • Losses from wrong recommendations count straight away
    • Savings count as verified only after a manager confirms them
  6. Step 6 of 6 · A manager approves

    It proposes adjustments

    Patterns that repeat become proposals for tomorrow: correct an item's forecast, raise its safety stock, or shorten how far ahead a batch covers. Each one shows its evidence, and a manager approves or rejects it.

    • Changes apply from the next day and can be reverted
    • Each change has limits, so one bad day cannot swing the numbers

What stays with the manager

Recommendations only until you go live
While you set up, nothing is assigned automatically. You decide when to switch the system live.
The reason is always visible
Each action opens to show its reasons, the numbers the system saw, and why its confidence is high or low.
It asks when it is unsure
When the data is old or does not add up, it asks for a count or says its confidence is too low.
Rejections are recorded
Reject any recommendation and give the reason. The reason is kept and the decision still goes into the review.
You approve the changes
Learning proposals wait for a manager, and every approval and override is in the audit log.

Follow these steps on a demo restaurant

Open the live demo and watch a shift that is already running, or start a free trial with your own menu.

The live demo opens your own copy of a demo restaurant with two branches and four weeks of sales. No account needed.

Start free trial

Live demo without an account · Arabic and English