> ## Documentation Index
> Fetch the complete documentation index at: https://docs.maska.co.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Log wastage

> Write off spoiled, expired, over-prepped, or damaged stock with a reason.

**Wastage** is stock you have to throw away — milk that spoiled, croissants
that expired, a tray that was dropped, a batch you over-prepped. Logging it
writes that loss off your on-hand balance and records *why*, so the value lost
shows up in your numbers instead of quietly disappearing as a stock-take
variance later.

<Note>
  New to the terms here (adjustment, variance, WMA, average cost)? See the
  [Glossary](/procurement/glossary).
</Note>

## Who logs wastage

Anyone with stock to write off can log it — outlet **staff**, **warehouse**
managers, and **owners/managers**. Where you log it depends on your role:

<CardGroup cols={2}>
  <Card title="Outlet staff">
    Log wastage against **your own outlet** — your home location is fixed, so
    you don't pick where. Your log shows **today's** entries only.
  </Card>

  <Card title="Owners & managers">
    Not tied to a single location, so you **choose where** you're logging —
    warehouse, an outlet, or the kitchen — defaulting to the warehouse. This is
    how warehouse-level wastage gets recorded.
  </Card>
</CardGroup>

## The reasons

Every line you write off needs a reason. The Log wastage screen offers:

* **Expired** — past its use-by / holding time.
* **Spoiled** — gone off, unfit to use.
* **Spillage** — physically lost (knocked over, leaked).
* **Over-prep** — prepped more than was needed.
* **Damaged** — broken or otherwise unusable.
* **Burnt / error** — a prep mistake ruined it.
* **Customer return** — sent back and unusable.
* **Quality fail** — didn't pass quality, can't be served.

<Note>
  These are the labels you see while logging. Under the hood they roll up into a
  smaller set of stored [wastage](/procurement/glossary) reasons (`spoilage`,
  `expiry`, `damage`, `wastage`, `count_variance`, `other`), which is what the
  manager tracking view groups and reports by.
</Note>

## Log a write-off

<Steps>
  <Step title="Open Log wastage">
    From your wastage log, tap **Log wastage**. (Managers/owners reach the same
    screen from the console's Wastage page.)
  </Step>

  <Step title="Pick the location (managers/owners only)">
    Choose where the wastage happened. Staff skip this — it's always their own
    outlet. Switching location starts the list fresh, since stock is per
    location.
  </Step>

  <Step title="Find the items">
    Search, or filter by type (Raw / Semi / Finished) and category, then tap an
    item to add it. Each row shows what's **on hand** and the item's average
    cost, so you can see the value as you go. You can add several items in one go.
  </Step>

  <Step title="Set quantity and reason">
    For each item, set how much was wasted and pick a reason. The screen values
    the loss at the item's current [average cost](/procurement/glossary) and
    keeps a running total.
  </Step>

  <Step title="Take the required photo">
    Each line needs a **live photo** as proof of waste — taken with the in-app
    camera, not chosen from your gallery. You can't submit a line until its
    photo is captured.
  </Step>

  <Step title="Add a note (optional)">
    Leave a short note for your manager if the reason needs context — e.g. "left
    out past holding time".
  </Step>

  <Step title="Log it">
    Submit writes off every line. On-hand drops at that location and the loss is
    posted to the stock ledger.
  </Step>
</Steps>

<Note>
  Submit stays blocked until **every** line has a quantity, a reason, **and** a
  captured photo. The action bar tells you what's still missing — how many lines
  need a reason or a photo — before it lets you write off.
</Note>

## How it hits your stock

Logging wastage doesn't go through a separate approval queue. Each write-off is
recorded as a posted stock **adjustment** (of the
[variance](/procurement/glossary) type): a negative line for the wasted
quantity, valued at the item's current average cost, that posts **immediately**.

That means:

* **On-hand goes down** at the chosen location the moment you submit.
* **The stock ledger** gets a row for the loss, so it's auditable later.
* The item's **average cost is unaffected** — wastage removes quantity at the
  current average; it doesn't re-blend the cost the way a receipt does.

<Warning>
  Logging wastage posts to live stock right away — there's no draft to sit on or
  silent undo. Check the quantity and reason before you submit. If you log
  **more than is on hand**, the screen warns you and the entry is recorded as an
  inventory **variance** rather than a clean write-off.
</Warning>

## Tracking what gets wasted

Your wastage log is where everyone sees what's been written off:

<CardGroup cols={2}>
  <Card title="Staff log (per outlet, today)">
    Staff see a running tally of **today's** wastage at their outlet — total
    value up top, split across Raw / Semi / Finished, then each entry with its
    reason, quantity, cost, and who logged it. Earlier days roll off.
  </Card>

  <Card title="Manager console (tenant-wide)">
    Owners and managers get a **whole-business** view — every write-off across
    every outlet, with the **total wastage value**, the number of entries, and
    the **top reason** and **top category** by value. Filter by reason and
    search by item or category to dig in.
  </Card>
</CardGroup>

<Note>
  Which items and categories staff can log against are configured by their
  manager — staff only see the trackable stock at their own location.
</Note>