Why this exists
A shop has orders. A trade business has jobs. A consultancy has enquiries and projects. The underlying record is the same thing, but calling a plumber's callout an "order" makes the whole app read as though it was built for someone else.
Setting it up
- Go to Customers, then Settings, then Record types.
- Tick what this business actually tracks.
- If you tick more than one, set what to call them collectively, up to 24 characters. Something like Jobs, Work or Records.
Only the types you tick are offered when classifying a record, which keeps the picker short and stops half your data being filed under a word nobody uses.
What changes
Your words are used throughout the app: list headings, buttons, the activity timeline, and the labels on a contact. It is a naming layer, not a data change, so switching it never moves or rewrites anything.
Leaving it blank
If you tick nothing, labels follow whatever your data says, which is the behaviour before you touch this page. That is fine for a business with only one kind of record.
A note on the API
The REST API resource stays orders whatever you call it in the interface, and each record carries a kind telling a purchase apart from an enquiry. Renaming the API resource would break every integration already built against it, so the naming stops at the interface.
Who can change it
Owners and admins only. It affects what every member sees.