Search the documentation

Find a page by title or section.

Go to dashboard
Administration

Terminology

Rename the eight core nouns to the words your business already uses, and know exactly how far the rename reaches.

Updated

Cooriroo ships with a default vocabulary — trip, stop, driver, destination — and most fleets already have their own. Terminology lets you replace eight nouns with the words your team says out loud, so nobody has to translate between the screen and the depot. It is a display change: nothing in your data moves, and nothing in the API is renamed.

Who can do this

Role
Administrators

Terminology is org-wide, so it is an admin setting rather than a personal preference. It is also the one part of configuration an API key cannot reach — the settings endpoints accept a signed-in admin only.

The eight terms

DefaultWhat it namesRenamed to, typically
TripOne journey with an ordered list of stopsRoute, run, job, tour
StopOne ordered call within a tripCall, visit, leg
TaskA unit of work, on a stop or standing aloneJob, action, step
DriverThe person carrying out the workCourier, operator, rider, crew
VehicleThe asset the work is carried out withVan, truck, bike, unit
ShiftA scheduled block of a driver’s timeDuty, roster slot, tour
OriginWhere goods are collected fromDepot, hub, kitchen, warehouse
DestinationWhere goods are delivered toSite, client, customer, drop
Each row is one editable term. Enter the singular; the product forms the plural for you.

Renaming takes about a minute, and the preview shows the result before you save.

  1. 1

    Open Terminology

    Customization → Terminology

    Customization is reached from the launcher in the header, and Terminology sits under Data and language. Your personal account settings are somewhere else entirely.

  2. 2

    Type the singular form

    Each row shows the current term on the left and an input on the right. Enter the singular — Route, not Routes. The preview beside the rows updates as you type, showing the navigation and a sample sentence in your words.

  3. 3

    Leave a row blank to keep the default

    An empty field is not an empty label. Blank means "use the platform default", so you can rename two nouns and leave the other six alone. Whitespace on its own is rejected rather than saved.

  4. 4

    Save

    The whole organisation moves at once. Reset to defaults in the page header restores all eight rows, and still needs a save to take effect.

Where a renamed term shows up

The rename is resolved on the server as well as in the browser, which is why it reaches further than the screens you are looking at:

  • Navigation, page titles, buttons, filters and empty states across the dashboard.
  • The driver app and the driver portal, which read the same terms from their own configuration rather than falling back to English defaults.
  • Notification text. "Trip #1042 started" becomes "Route #1042 started" in the admin feed and in the push a driver receives.
  • Bulk-import templates: the title of the template and the name of the file you download.
  • The AI assistant, which is told your vocabulary and also recognises it in questions — asking where your couriers are still finds your drivers.

What renaming does not change

Terminology is a label layer over a fixed model. These stay on the platform vocabulary no matter what you rename, and that is deliberate — an integration written last year must not break because someone renamed a noun this morning.

  • API paths and JSON field names. A trip is still trip on the wire.
  • Permission and scope keys, which stay as trips:read and friends.
  • Dashboard URLs — /admin/trips does not become /admin/routes.
  • Column headers in import templates and exports, which are the field keys the importer matches on.
  • Custom field keys, and the selectable type taxonomies for trips, stops, destinations and origins — those are edited under Entity Types.

How quickly it propagates

The dashboard picks the change up on the next load. Server-side text — notification titles, import template names, the assistant’s vocabulary — reads from a cache that is refreshed at least every five minutes, so a rename can take that long to reach every surface. Signed-in drivers pick it up when their app next fetches its configuration.

When a rename does not look right

The dashboard uses my word but the driver app still says the old one
Cause

The app caches its configuration and refreshes it on its own schedule.

Have the driver close and reopen the app, or sign out and back in. The driver app and portal read terminology from a driver-readable configuration endpoint, not from the admin settings a driver has no rights to.

One label went back to English on its own
Cause

That row was saved blank, so it falls back to the platform default.

Blank means "default", not "no label". Retype the word and save. The same applies to a value that is only spaces — it is rejected rather than stored.

The plural of my term is wrong
Cause

Plurals are derived by rule, and the rule only covers regular English.

There is no separate plural field. If the generated form is unusable, choose a near-synonym that pluralises regularly — this is the most common reason a rename gets reverted.

My integration broke after we renamed things
Cause

Almost certainly not the rename.

Terminology never touches API paths, field names, scope keys or import column headers. If a client started failing, look for a change on its own side rather than in this setting.

I want to change the list of trip or destination types, not the noun
Cause

Those are a different setting.

The selectable type taxonomies live under Entity Types in the same Customization group. Terminology renames the noun; Entity Types edits the values you can pick for it.