Skip to main content

Setup order: how hunts, seasons, and areas fit together

The order to set things up — how hunt types, seasons, areas, and bookings depend on each other.

These pieces build on each other, so setting them up in the right order saves rework. Here's how they relate.

The dependency chain

  • Hunt Area (optional) — a location you can attach to hunt types.
  • Hunt Type (required first) — species, duration, pricing. Optionally linked to an area.
  • Season (requires a hunt type) — a dated, year-specific window with capacity.
  • Hunt (optional) — discrete bookable weeks inside a season.
  • Booking (requires a season) — a hunter booked into a season, optionally a specific hunt.

Recommended order

  1. (Optional) Add your hunt areas first if you want to tag hunts by location.
  2. Add your hunt types — at least one before anything else, since seasons need one.
  3. Add a season for each hunt type and year you'll run.
  4. (Optional) Add hunts inside a season if you sell it by the week.
  5. Now you can take bookings against those seasons.

You can't create a season without a hunt type, and you can't create a booking without a season. Pricing is set once on the hunt type and flows down to seasons and bookings.