Projects
Keep one list of the projects shipments are filed under, so operators pick a project instead of typing a name and reports can group by it.
Projects (/settings/projects) is the catalog of projects a shipment can be filed under — a
customer programme, a season, a contract. Operators pick one on the shipment; reports group by it.
Before this catalog the project on a shipment was free text, so "Acme Q3" and "ACME Q3" were two projects no report could bring together. The project is now a reference to this list, and this page is the only place the list is authored.
The list
| Column | What it means |
|---|---|
| Name | What operators see in the picker. |
| Code | A short identifier, stored upper-case and unique within your company. Optional. |
| Shipments | How many shipments are filed under this project. |
| Active | Off hides the project from the picker. Shipments already filed under it keep it. |
A row that any shipment still points at is marked In use.
Adding and editing
Add project asks for a Name (required) and a Code (optional). Lower-case codes are uppercased for you, so two spellings cannot become two projects.
Edit changes the name or the code; every shipment already filed under the project follows the change.
Retiring a project
Two ways, for two situations:
- Active off — the project stops appearing in the picker but every shipment that carries it keeps resolving to it. This is the normal way to retire a finished project: history stays whole.
- Delete — removes the project outright. Only offered for a project no shipment references; a project marked In use cannot be deleted (the server enforces this too — switch it off instead, or move its shipments first).
Related
- Divisions — the operating unit that owns a record; a different axis from the project it is filed under.
- Edit a shipment — where the project is picked.