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

# What's in the Blend Metrics report?

> Six sections — Turnaround, Patients, Stuck, Invoicing, Replacements, and Utilization — over any date range, scoped to one business or rolled up across a whole brand, with comparison against the prior period.

The Metrics report in the Blend Dashboard is the operational view of your account: how fast orders move, how many patients are new versus returning, what's getting stuck, what you're spending, how often replacements happen, and which products and prescribers drive volume. Choose a date range, scope it to a single business or roll it up across an entire brand, and each section compares against the prior period.

Find it under **Metrics** in the Blend Dashboard.

## The six sections

<CardGroup cols={2}>
  <Card title="Turnaround" icon="stopwatch">
    Average time from order received to shipped, with time spent blocked in exception excluded — so a stuck order doesn't distort your fulfillment speed.
  </Card>

  <Card title="Patients" icon="user-group">
    New versus returning patients in the period. The clearest read on whether growth is acquisition or retention.
  </Card>

  <Card title="Stuck" icon="triangle-exclamation">
    Orders and prescriptions created in the period that hit an exception, broken out by reason — so you can see which blockers are systemic.
  </Card>

  <Card title="Invoicing" icon="file-invoice-dollar">
    Product, fill, and shipping spend, windowed on ship date.
  </Card>

  <Card title="Replacements" icon="rotate">
    Replacement order rate against orders created in the window — your quality signal.
  </Card>

  <Card title="Utilization" icon="chart-column">
    Product volume, optionally broken down by prescriber.
  </Card>
</CardGroup>

## Turnaround, measured two ways

Turnaround is reported both as **wall-clock** time and against **pharmacy operating hours**.

The distinction matters more than it sounds. An order received at 9pm and shipped at noon the next day is fifteen hours on the clock, but only a few operating hours — and the second number is the one that reflects how the pharmacy actually performed. Judge fulfillment speed on business hours; set patient expectations on wall clock.

<Note>
  Time an order spends in `exception` is excluded from turnaround. A stuck order waiting on a missing prescription isn't a fulfillment delay, and counting it as one would hide real performance changes.
</Note>

## Scoping and comparison

* **One business, or a whole brand.** Scope to a single customer, or roll up across every business under a brand. See [multi-brand and multi-location support](/guides/multitenancy).
* **Filter to a location.** Where a business operates several locations, narrow to one.
* **Compare against the prior period.** Each section reports change against the preceding comparable window, so a number is always in context.
* **Deep-link a section.** The active tab is reflected in the URL, so you can send a colleague straight to the view you're looking at.

<Tip>
  Sections export to CSV, so a monthly board pack or a finance reconciliation doesn't mean retyping figures. The report is also laid out to print cleanly.
</Tip>

## Metrics versus the API reports

|          | Metrics report                               | [API reports](/guides/reports)              |
| -------- | -------------------------------------------- | ------------------------------------------- |
| Where    | Blend Dashboard                              | `GET /reports/daily`, `GET /reports/orders` |
| Best for | Reviewing performance, spotting trends       | Feeding your own systems                    |
| Depth    | Turnaround, spend, utilization, replacements | Counts by day and by status                 |
| Scope    | Customer, brand, or location                 | Your account                                |

Use Metrics when a person needs to understand what happened. Use the API reports when a system needs the numbers.

<CardGroup cols={2}>
  <Card title="API reports" icon="chart-simple" href="/guides/reports">
    Pull counts programmatically
  </Card>

  <Card title="Multi-brand support" icon="sitemap" href="/guides/multitenancy">
    How brand roll-ups work
  </Card>

  <Card title="Stuck orders" icon="triangle-exclamation" href="/guides/stuck-orders">
    What the Stuck section is counting
  </Card>

  <Card title="Replacement orders" icon="rotate" href="/guides/replacement-orders">
    What drives the replacement rate
  </Card>
</CardGroup>
