Origins
The places goods are collected from, with the pickup detail a driver needs on arrival.
An origin is a place goods come from — a kitchen, a warehouse, a hub, a supplier’s yard. It holds the same address and contact detail as a destination, plus the two things that only matter when someone is collecting: how to get the goods, and how long they take to be ready.
Who can do this
- Role
- Administrators
- Permission
origins:readorigins:writeorigins:delete
Origins are an admin surface. The list, the create form and the import all sit behind the origins scopes.
Terminology
Your organisation can rename these. If your screens say something else, this is what they mean here.
- Origin
- A place goods are picked up from. Some tenants rename these pickups, sources, kitchens, depots or suppliers.Rename it in Customization → Terminology
- Destination
- A place goods are delivered to. A separate record type, covered on the Destinations page.Rename it in Customization → Terminology
An origin is not a destination
These are two record types, not two labels on one. They have their own lists, their own permissions, their own type vocabularies and their own fields, and nothing converts one into the other — a place you both collect from and deliver to needs a record on each side. If you are describing somewhere goods are dropped off, you want Destinations.
| Origin | Destination | |
|---|---|---|
| Direction | Goods leave here | Goods arrive here |
| Pickup instructions | Yes, free text | No |
| Average prep time | Yes, in minutes | No |
| Delivery window | No | Window open and window close |
| Opening a record | Opens the edit form | Opens a detail page with tabs |
| Driver assignments | No | Yes |
| Created automatically | Yes, from a driver GPS fix | Never |
Create an origin
Name, Address Line 1, City and Country are required. Type is required but pre-selected.
- 1
Open the form
Origins → Add OriginThe sidebar shows your own word for these if you have renamed them.
- 2
Name it and pick a type
The type list is your organisation’s, and the field opens on the first entry in it, so leaving it untouched is a valid answer.
- 3
Place it on the map
Search, click the map, or type coordinates by hand. A chosen search result also fills the city, state, postal code and country fields.
- 4
Add the pickup detail
Pickup instructions and average prep time are the fields that make this an origin rather than a generic address — see below.
- 5
Add contacts and custom fields
Contact name, phone and email; then any custom fields your organisation has defined for origins.
Pickup instructions and prep time
Pickup instructions is free text and belongs to the driver standing outside: which entrance, which bell, which dock, who to ask for. Average prep time is a whole number of minutes describing how long this place typically takes to have an order ready — the honest number, not the aspiration, because it is what makes a collection time realistic.
Origins you did not create
When a driver starts a trip from wherever they happen to be rather than from a planned pickup, the system records where that was as an origin, so the trip has a real starting point instead of a blank. These are stamped with a source of driver_location and named Driver location. Their address comes from reverse-geocoding the GPS fix, falling back to the raw coordinates when that fails, and their city and country are placeholders — a driver’s position has no structured address to record.
Types are configured, not fixed
Origins ship with Restaurant, Dark Kitchen, Cloud Kitchen, Commissary, Warehouse, Hub and Other, and that list is entirely yours to replace under Customization → Entity Types. Origin types are configured separately from destination types, so the two lists need not resemble each other. A value no longer in the list still displays on the records that hold it.
Working the list
Search matches name, city and address; the toolbar adds status, type and your own custom-field conditions. A few things behave differently from destinations:
- There is no detail page. The row’s edit action opens the same form you created it with, and global search deep-links straight into that form.
- There is no map view for origins. Coordinates still matter — they are what a trip routes from — but there is no clustered map to browse them on.
- Import takes CSV, XLSX or JSON up to 500 rows, matching on name to update rather than duplicate. It never matches a driver-location origin, so an import cannot accidentally overwrite one.