Custom fields, tags, seasons & territories
Four small settings that make the app fit your business instead of the other way round. None of them is required. Each is worth ten minutes if it matches something you’re currently tracking on paper or in your head.
Custom fields
Extra fields on a record, for the thing your business tracks that nobody else does — gate code, dog’s name, which side the meter is on.
Settings → Company → Customization → Custom Fields. Requires admin.
Pick what it’s attached to
Customer, Property, or Job. Those three, and a field belongs to exactly one of them.
Pick a type
Text, Number, Date, Select, or Checkbox. Select takes a list of options you define.
Name it, and decide if it’s required
Attach it to the right record. “Gate code” on the customer is wrong the moment they have two properties — it belongs on the property, because that’s what has the gate.
Tags
Free-form labels for grouping customers: commercial, snow contract, slow payer, referred by Dave. Each gets a color, and they show as chips on the customer list where you can filter by them.
Settings → Company → Customization → Tags.
Tags apply to customers only — not properties, jobs or invoices. If you want to label a property, that’s a custom field.
Custom field or tag? A tag answers which group is this in and you’ll add and drop them freely. A custom field answers what is this value and every record has one. Gate code is a field. “Commercial” is a tag.
Seasons
Named date ranges — Spring, Summer, Fall, Winter, plus any you invent. They drive contract grouping, contract rollover, and route scheduling.
Settings → Catalog → Seasons.
Each season takes a name, a date range, a color and an icon. The calendar overview shows how they map onto the year, which is the fastest way to spot a gap or an overlap you didn’t intend.
Seasons may cross the year boundary — a November → March snow season is normal and the form tells you when you’ve made one.
The slug cannot be changed after you create a season, because contracts and API references point at it. The display name can change whenever you like.
Deleting a season leaves existing contracts alone; they keep the season they were written with.
Service territories
The areas you cover, defined by ZIP code. They colour the chips on Locations, drive the facet rail and heatmap, and let you filter jobs, routes and reports by area.
Settings → Operations → Service Territories. Owner only.
Name the area, pick a chip color, and paste the ZIPs — one per line or comma-separated. Properties auto-assign on save, so you don’t back-fill by hand.
A ZIP belongs to exactly one territory. The form tells you which territory already claims one rather than silently moving it.
Territories archive rather than delete, and the confirmation tells you how many properties will move to Unassigned first.
Tips
- Don’t create a custom field for something already in the app. A second “phone” field means half your customers have a number in the wrong place.
- Name territories after how your crews talk. “Cedar District” beats “Territory 3” on a radio.
- Set seasons before writing seasonal contracts, not after. Rollover uses them.