Define Location types and how they work in Reservation flow

Request:
Create a clear model for different types of locations in the system, because “location” can mean different things depending on the context.

The system should be able to distinguish between:

• Guest accommodation / lodging location (+ Alternate lodging or custom accommodation)

• Check-in location

• Activity meeting location (includes boat dives)

Context:
These location types are related, but they do not always mean the same thing operationally.

For example, the guest’s lodging location is mainly used as information and for reporting. It does not always have a direct operational impact. However, lodging can help determine or suggest the closest check-in location.

The check-in location is the place where the guest checks in for the first time. This can be connected to an activity, for example if they have a guided dive or course as their first activity or connected to picking up gear. In these instances when there is an activity involved, we always have guests check-in at the location of their activity. However, it can also be separate from the activity location when people do boat dives.

Example:

A guest doing a boat dive will need to check in at the Dive Friends location closest to their accommodation the day before the boat dive because they need to do a mandatory 'buoyancy check' according to local law. This is a quick 15 minute dive to check if you have enough weights and if all your gear functions properly. The boat dive itself may then depart from a different location the next day. This means the check-in location is not always the same as the place where the activity starts.

For boat dives, there can also be a pickup/meeting location. We currently have two shops where the boat docks or picks people up:

• Port Bonaire

• Sand Dollar

The boats is based at Port Bonaire. For example, we may have 5 guests boarding at Port Bonaire, then the boat drives to Sand Dollar to pick up another 7 guests. On the way back, guests are dropped off in reverse order.

Goal:
Make sure the system understands that different location fields have different meanings and different functions in the app.

Suggested location fields:

1. Guest accommodation / lodging location (Alternate lodging / custom accommodation)
   Used for where the guest is staying. This is mainly informational and useful for reporting, but it can also help suggest a check-in location.

2. Check-in location
   Used for where the guest needs to check in for the first time. This may be linked to lodging, gear pickup, or the first activity, but it is not always the same as the activity start location.

3. Activity meeting location
   Used for where the guest needs to meet for a specific activity. Activity can be a course, guided dive or boat dives (pickup location).

4. Reservation made by partner
   Used to identify whether the booking came through a partner and whether commission should be calculated.

Important distinction:
Guest accommodation and commission/referral source should be separate fields.

For example:

• Guest accommodation = Delfins

• Reservation made by partner = No
  Result: guest is staying at Delfins but booked directly with us, so Delfins does not receive commission.

Another example:

• Guest accommodation = Delfins

• Reservation made by partner = Delfins
  Result: guest is staying at Delfins and the booking came through Delfins, so Delfins should receive commission.

Suggested next step:
Review whether the reservation form should include separate fields for:

• Reservation made by partner (and which partner)

• Guest accommodation

• Check-in location

• Activity meeting location / boat pickup location where applicable

This counts for the reservations form that will be filled in by our team. When guests can make their own reservation through our website in the future, we need to revisit this logic and rules for that end of incoming reservations.

Goal:
Avoid confusion between lodging, check-in, meeting point, boat pickup, and partner commission logic.