> ## Documentation Index
> Fetch the complete documentation index at: https://muveya.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Consumption report
> Read what each supply consumed, in its own unit, by day or by week, and understand what the figures do and do not cover.
The **Reports** screen shows **Consumption by supply**: how much of each supply left your inventory as consumption over a period, always in that supply's own unit. It is read-only. Nothing you do on this screen changes stock.
## Who can use it
| What | Permission | Console label |
| - | - | - |
| Open the screen and read the figures | `reports.read` | **View reports** (group **Reports and audit**) |
* No role grants `reports.read` automatically, not even owner or admin. Someone who can manage the team (`members.manage`, **Manage team access**) must grant it in **Team**. See [Team](/docs/en/account/team) and [Roles and permissions](/docs/en/account/roles-and-permissions).
* You do not need any inventory permission to read the report.
* Without `reports.read`, the **Reports** item is hidden from the navigation. If you open `console.muveya.com/reports/consumption` directly you see **You need the View reports permission** and **An owner or admin can grant it to you in Team.** If you can manage the team yourself, an **Open Team** link takes you there.
## Where it is
Main navigation: **Reports**. The screen title is **Consumption by supply** and its path is `/reports/consumption`.
## What counts as consumption
The report reads the immutable stock ledger and adds up every `consume` movement in the period. A `consume` movement is created when stock leaves a box as used or delivered, for example:
* **Consume** on a box page in the console (see [Use and moves](/docs/en/inventory/use-and-moves)).
* **Log consumption** from WhatsApp (see [WhatsApp operations](/docs/en/whatsapp/operations)).
Receipts, transfers between warehouses, dispatches, corrections and counts are not consumption and never appear here. The screen reminds you of this when it is empty: **Consumption recorded from a box appears here. Try a longer period or all supplies.**
## Filters
| Filter | Options | Default | Notes |
| - | - | - | - |
| **Period** | **Last 7 days**, **Last 30 days**, **Last 90 days** | **Last 30 days** | The window ends at the next midnight UTC, so today counts in full. Choosing **Last 90 days** switches **Group by** to **Week**; you can switch it back to **Day**. |
| **Group by** | **Day**, **Week** | **Day** | A week starts on Monday, 00:00 UTC. |
| **Supply** | **All supplies**, or one supply | **All supplies** | Every supply in your catalog is listed as `Name · SKU`, alphabetically, including retired ones, because history can still mention them. |
Under the filters the screen states two rules:
* **Days and weeks follow UTC time.** A consumption recorded late in the evening in your local time can fall on the next UTC day.
* **Observed use is stock recorded where it was used. Stock delivered to rooms that do not count their stock is an estimated consumption. The two add up to what was consumed.**
When you change a filter, the previous figures stay on screen with **Updating figures…** until the new ones arrive.
The console offers only these three periods. For another window (up to 366 days) use the public API operation `GET /v1/analytics/consumption-trend` or the MCP tool `analytics.consumption`. Both return exactly the same figures as this screen for the same window. See [Management analytics](/docs/en/reports/management-analytics).
## Reading the table
The table **Supplies consumed** has one row per supply **and unit**. Rows are ordered by number of records, most first.
| Column | What it shows |
| - | - |
| **Supply** | The supply name and SKU (`Nitrile gloves M · GLV-NIT-M`). If the catalog can no longer name the supply, **Supply no longer in the catalog**. |
| **Unit** | The supply's unit of measure, with the catalog's word for it (for example **Box**, **Milliliter**, **Pair**). |
| **Consumed** | Total quantity consumed in the period, in that unit. |
| **Observed use** | The part recorded as used where it was used (**Used directly**), plus exits recorded without a room. |
| **Delivered to rooms (estimated)** | The part handed to a room that does not count its stock (**Delivered to the room**, a room set to **Not counted**). It left inventory, but nobody observed its use, so it is an estimate of consumption. |
| **Records** | How many ledger movements the row adds up. |
| **Detail** | **By day** or **By week** opens the breakdown of that supply. |
**Observed use** plus **Delivered to rooms (estimated)** always equals **Consumed**. To learn how a room is set to **Counted stock** or **Not counted**, see [Destinations](/docs/en/locations/destinations).
### Why there is no total row
Each row is a supply in its own unit. 100 gloves and 500 mL of soap are two rows and never "600 units". The report never adds different supplies or different units together, and the screen never computes a figure of its own. If the same supply has movements recorded in two different units, it appears as two rows, one per unit.
### The breakdown
**By day** (or **By week**) lists only the days or weeks that have records, oldest first. Each line shows:
* the date, or **Week of** followed by the Monday date;
* the quantity, unit and records, for example `120 Box in 30 records`;
* the split, for example `100 observed · 20 delivered to rooms (estimated)`.
On a phone, each supply is shown as a labelled card instead of a wide row.
## The summary sentence
Above the table, a **Summary** can state the report in one sentence, for example:
```text theme={null}
Aug 19 – Sep 17, 42 records: Nitrile gloves M · 120 Box in 30 records; Chlorhexidine 0.12% · 1,500 Milliliter in 12 records.
```
* It names up to five supplies and then says how many more there are (`and 3 more supplies`). The table always lists all of them.
* It repeats every caveat that applies (partial figures, records without a verified unit, restricted warehouses).
* It appears only when the server has checked every figure in it against the table. The screen then says **Every figure in this sentence was checked against the table below.** If the check does not pass, there is no sentence and the table stands alone. The sentence is built from the figures by fixed rules; no AI writes it.
## Coverage and caveats
Before the table, the screen tells you what the figures do not cover. Read these notices before you treat a figure as a clinic total.
| Notice | When it appears | What to do |
| - | - | - |
| **Partial figures: read from `date` onward. Narrow the period or choose one supply to see all of it.** | The period holds more than 5,000 consumption records. The report reads up to the newest 5,000 and states the instant from which the figures are complete (`coveredFrom`). Older records in the period are not included. | Choose a shorter period, or pick one supply. |
| **`N` records from before units were verified are counted but not quantified: `supplies`.** | Some records were made before the supply's unit of measure was verified. They are counted, but their quantity is not added to any row, because the unit they were recorded in cannot be proven. The notice names up to five supplies and counts the rest. | Nothing to fix for past records. New records carry a verified unit. |
| **Only includes the warehouses assigned to you, not the whole clinic.** | Your membership is limited to some warehouses. You only see consumption that left those warehouses. | Ask an administrator for wider warehouse access if you need clinic totals. |
If there are no records at all in the period, you see **No consumption in this period**.
## What the system records
Nothing. Opening or filtering the report does not create movements, change stock or write audit entries.
## Download
This screen has no download button. To get figures as a file, request the management briefing export through the public API; it includes the consumption of the leading supplies, each in its own unit. See [Exports](/docs/en/api-reference/exports) and [Management analytics](/docs/en/reports/management-analytics).
## What can go wrong
| Message | Cause | What to do |
| - | - | - |
| **You need the View reports permission** | You do not hold `reports.read`. | Ask someone with **Manage team access** to grant **View reports** in **Team**. |
| **Your account does not have permission for this action.** | Your permission was removed while the screen was open. | Reload. If it persists, ask for **View reports** again. |
| **Review the entered values before trying again.** | The server refused the window (for example a window wider than 366 days). The console presets never trigger it. | Reload the page and pick a preset. |
| **The active dental clinic account changed. Reload the page before trying again.** | You switched account in another tab. | Reload the page. |
| **Could not confirm the operation. Check your connection and review the list before trying again.** | You are offline. | Check your connection, then **Try again**. |
| **Could not complete the request. Please try again.** | A temporary server problem. | Use **Try again**. If it keeps failing, write to [team@muveya.com](mailto:team@muveya.com). |
## Related pages
Every management metric and where to read it: API, MCP and exports.
How consumption is recorded from a box in the console.
Log consumption from a phone.
Grant **View reports** to a member.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.