Glossary

The read-only record of every action in your company: who, what, when and whether it worked. See Page guide: Activity log.

A secret that lets a customer's own system (an ERP, a web shop) read orders, place them or get quotes without signing in. It acts as one customer contact. See API keys and webhooks for customers.

An order is Assigned when a driver has it, and Driver accepted once the driver confirms in the app.

One try at a pickup or delivery. A failed attempt records a reason and can be followed by a new attempt, a return to sender or a hold. See Handle failed deliveries.

The dispatch rule Auto-assign new orders: portal, API and import orders go straight to the best-fitting driver and become Assigned. When nobody fits, the order stays Pending.

The status of an order a customer placed (portal, API, import or recurring) when their account doesn't approve orders automatically. Your team approves or declines it. See Customer settings and field modes.

The starting price of an order before modifiers: the lane's price in the price set's zone table. A distance-only price set has no zone table and builds its price from modifiers such as Per km. See How pricing works, end to end.

A delivered or completed order that can go on an invoice. It waits as an Unbilled order until it is invoiced. See Orders not yet invoiced.

Your operating days and holidays. Delivery promises, holiday surcharges, recurring orders and pay days read it. See Business calendar.

A qualification a driver holds, such as dangerous goods training, with a number and an expiry date. Handling types can require it. See Handling and certifications.

The list of every handover of a package (pickup, depot receiving, transfer, delivery, return), shown on an order's Packages tab.

Extra amounts added to an order after pickup or delivery, such as waiting time, a failed attempt or a redelivery. They are billed with the order.

Money a driver collects from the receiver. COD orders come from the staff order form, the customer portal, an import or the API. The cash stays with the driver until finance receives it in COD cash. See COD cash.

A customer's own price for some lanes or modifiers, used instead of the price set's while it is in effect. See Contract rates.

A numbered document that gives a customer money back as credit against open or later invoices. See Credit notes.

A field you add to customers or orders, such as a PO number. Internal or customer-visible. See Add custom fields.

A business you deliver for. It has contacts, addresses, prices, invoices and, if you allow it, portal access. See Add customers and give them portal access.

A person at a customer. Contacts can be invited to the portal, each with their own sign-in and rights.

A problem or help request a customer sends from the portal, for example with Report a problem on an order. See Customer issues.

One of the six roles every company starts with: Admin, Operations Manager, Dispatcher, Warehouse Manager, Finance, Viewer. See Roles and permissions explained.

When an order is due, worked out from its service type's promise and your business calendar. See Availability and delivery promise.

A hub you pick up from, sort at or send routes out of. Its page address is /warehouses, and the Warehouse Manager role runs depots. See Run the depot day and scan station.

Which depots' order alerts a team member gets: all of them, or up to four selected ones. It does not hide records.

An order with No depot — direct job: one driver collects at the pickup address and drives straight to the delivery. It is never put on a route. See Routing with or without a depot.

Sending a planned route to its driver, so the stops appear in the driver app. See Dispatch and run a route.

Free text a dispatcher adds to a route; the driver sees it as Notes from dispatch on the route's orders.

An order or invoice that is saved but not yet live. A draft order may leave required fields empty.

The NemiRoute phone app drivers use to clock in, run stops, capture proof and see earnings. See Install and sign in.

Approved independent drivers, vetted and paid by the platform, who can take your unassigned orders. They never join your own driver list. See Use the driver network.

What one person can do right now: their role plus their overrides.

An item in the Exceptions queue that needs a dispatcher: a failed or late order, an order without a driver, a delayed vehicle, lost signal or a driver issue. See Exceptions queue.

A delivery attempt that did not hand over the package. It records a reason and counts as an Attempt. See Failed deliveries.

How a field appears on the portal order form: Hidden, Optional, Required or Locked.

Dated fuel price values (for example the weekly NRCan average) that a fuel surcharge reads to pick its percentage. See Fuel surcharge from a fuel index.

What a package needs (Standard, Fragile, Temp. controlled, Dangerous goods, Keep upright or your own), and therefore what the vehicle, driver and proof must meet. See Handling and certifications.

The depot a driver or vehicle belongs to. Optional: a courier with no warehouse leaves it empty.

A pickup zone → delivery zone pair, such as Toronto Core → Mississauga. Each lane has a base price in a zone table.

A block that stops a person's data from being erased during a dispute or claim. See Privacy requests, retention and legal holds.

The map of every active vehicle, its route and next stop, refreshed every few seconds. See Live map.

One charge or discount on top of the base price: a fee, a rate per km, a fuel percentage, a weekend fee. Each has a type that decides the maths. See Modifiers.

A bundle of modifiers that charges their sum, only the highest or only the lowest. See Combine modifiers in a group.

One order with extra stops (up to 25) and an optional return leg. It has one price and goes to one driver as a whole; it is never put on a route.

An order paused on purpose, for example after a failed attempt while you wait for the customer.

One job: a pickup and a delivery for a customer, with its packages, price and status. Its number starts with your order prefix (for example OR-2149). See Create an order.

Where an order came from: Manual (your team), Portal, CSV (import) or API.

A personal exception to a team member's role for one area, optionally until a date.

A parcel size and weight customers can pick, such as an envelope or a pallet, with its price effect. See Conditional charges.

The dates whose driver and staff earnings are paid together. It moves through Open, Closed, Statements ready, Approved and Paid. See Pay periods.

How a driver or staff member earns: per hour, per delivery, per km, salary and more. Plans are versioned. See Driver pay plans.

An area plus an action (Read, Write, Create, Delete), such as "Invoices: Create". See Roles and permissions explained.

What the driver captures to complete a stop: signature, photo, recipient name, ID and age check, PIN or safe drop, plus a GPS check. See Proof and delivery rules.

Your customers' own website, at your portal address, where their contacts place and track orders, pay invoices and report issues. See Track your orders.

A service customers order, such as Same Day or Standard. It sets its zone table (if any), modifiers, availability and delivery promise. See Price sets.

A page to quote any price set against made-up inputs and see every step of the calculation. See Test price sets and quotes.

A window when non-urgent texts (to customers) or alerts (to you) wait. See Page guide: SMS.

An order whose lane is outside the zone table. It is put On hold until someone sets its price with Adjust price.

The person or business that gets the delivery. Receivers don't need an account: they follow the order with a tracking link.

A series that repeats an existing order on a schedule; each order is created a set number of days ahead (7 by default) and priced then. See Recurring orders.

After a failed delivery, the package goes back to the pickup address; it ends as Returned.

A named set of permissions. Every team member has exactly one.

One vehicle's run from a depot through a list of stops, planned in the Route planner. Statuses: Draft, Planned, Ready, In progress, Completed, Cancelled. See Plan a route.

The depot screen where packages are scanned in, so you know they arrived and where they go next.

The unit text messages are counted in; a long message uses more than one.

The schedule is the week ahead; the time clock is what drivers actually worked, from clock-in to clock-out. See Driver schedule and time clock.

Everyday word for an order on its way, as in the Shipment delays alert. There is no separate shipment record.

A list of everything invoiced to and paid by one customer over a period. See Statements and aging.

One pickup or delivery on a route. Stop statuses: Pending, Completed, Failed, Skipped.

What your company pays for NemiRoute: your plan, usage and limits. See Your plan, usage and limits.

A person at your company who signs in to the app (not a driver or customer contact). See Invite your team and manage roles.

Your company's own workspace on NemiRoute: your data, settings, team, customers and portal, kept apart from every other company.

The public page anyone with the link can open to follow one delivery. What it shows is set in Customer experience.

An order with no driver yet. The Needs attention row of the Operations overview lists them first.

A delivered order not yet on an invoice. See Unbilled orders.

Your company's weight, distance, dimension and volume units (kg or lb, km or mi, cm or in, m³ or ft³). Values are stored in metric and shown in your units. See Page guide: General settings.

A signed call NemiRoute sends to another system's URL when an order or invoice event happens. See Page guide: Company webhooks.

A named area made of postal prefixes, such as M5V for downtown Toronto. A postal code belongs to the zone with the longest matching prefix. See Zones and postal prefixes.

The matrix of base prices for every lane between your zones. A price set uses at most one zone table for its base price. See Zone tables and lane prices.