# Glossary

Terms used across the whole console. Dispatcher-specific vocabulary — driver states, Last-Option, TTB — is in the [Dispatcher glossary](/books/console-yF7/page/dispatcher-glossary).

| Term | Meaning |
|---|---|
| **Brand** | A commercial identity within your company. Most screens work within one brand at a time, and data is separated by brand |
| **Store** | A physical location. Called a branch in some screens |
| **Hub** | An operational grouping of stores. Employees belong to a hub, and it determines which operation their work counts towards |
| **Source** | Where an order came from: web, app, kiosk, or an aggregator. Content and some reports are separated by source |
| **Scope** | What data an employee may see — brands, stores, sources. Set once per person and applied everywhere |
| **Role** | What an employee may do. A person can hold several; permissions combine |
| **Permission** | One specific ability, such as assigning a driver or exporting metrics. Roles are built from these |
| **Exception** | A grant or deny of one permission for one person, overriding their roles. A deny always wins |
| **Business date** | The trading day an order belongs to. Late-night orders belong to the previous business date, not the calendar date |
| **Promised time** | The delivery time the customer was given, and what lateness is measured against |
| **Own fleet** | Your own drivers, whether employed or contracted |
| **Third-party carrier** | An external delivery company you hand orders to. They choose the courier, not you |
| **Redeemed** | A promotion, voucher or credit the customer has already used. Bulk operations never touch redeemed records |
| **Bulk change** | Changing many records at once, via check → apply → track |
| **Import** | Loading records from a CSV. Never transactional: a partial failure leaves earlier rows applied |
| **Backup** | A retained snapshot of an export, which can be downloaded or restored |
| **Alarm** | Raised automatically when a store crosses a threshold. Lives in the Hub, and is archived once handled |
| **Alert** | Raised automatically about a driver, or returned by a threshold report in Reports |
| **Incident** | A record *a person* writes against one order, explaining what went wrong |
| **Request ID** | Identifies one dispatcher run. The single most useful thing to include when reporting a dispatcher problem |

## Three that are easy to confuse

**Alarm, alert, incident.** The first two are raised by the system and you respond to them; the third you write yourself and it stays on the order. See [Branch alarms](/books/console-yF7/page/branch-alarms), [Stores and driver alerts](/books/console-yF7/page/stores-and-driver-alerts) and [Logging an incident](/books/console-yF7/page/logging-an-incident).

**Contracted driver versus third-party carrier.** A contracted driver is part of your fleet and is assigned by name. A carrier is a company — you hand it the order and it picks the courier. See [External employees](/books/console-yF7/page/external-employees).

**Role versus scope.** Roles decide actions, scope decides data. See [Roles and scope: the two ideas](/books/console-yF7/page/roles-and-scope-the-two-ideas).