🌟 Required Items before Checkout (Order Restriction)

[Nicistarful]

ℹ️ Please check if the feature you're requesting already exists in the project's roadmap or issues.
I looked through the issues / suggestions and haven't found a request like this yet.

Is your feature request related to a problem? Please describe.
We are currently using hi.events for an upcoming event and we give attendees the option to also reserve a hotel room for the event duration. However, some people have gotten around the requirement to at least get an Attendance Ticket by just putting the Hotel Room in their cart. This means we have to manually ask those who didn't get an Attendance ticket to purchase one, because it would be unfair to those who purchased both (Attendance + Hotel).

In short: We are missing the functionality to make products required before being able to continue with checkout.

Describe the solution you'd like
Under event settings, in the checkout section, it'd be great to choose products where, if any of them have a quantity of more than 0 in a customer's selection, you can continue with checkout and get a restriction otherwise.

Additional context
I have made some changes locally and tested them already and they work:

If this aligns with hi.event's interests and seems like a good addition, I'm more than happy to create a pull request an contribute. Would love feedback on this.

[anthonyrom]

A workaround could be creating two products: "Attendance" or "Attendance w/ Hotel" rather than separating them like this. Seems like a bad pattern to make checkout available only when purchasing a certain item.

[Nicistarful]

This may be specific to our case but I’m not sure if others might run into something similar. We separated them because some rooms were blocked for 2 days mid-event, so we created the whole duration hotel ticket/product and also the single nights (which draw from the same per night capacity). We could have combined it with the hotel but we wanted separate check-ins, one for attendants in total and then those who stay at the hotel.

But you’re right, we could’ve structured it so that the Hotel variants contain the ticket price. We just thought dynamically, not having to change each price because we adjust the attendance ticket.

However, I see that my suggestion is a bit of an „anti-pattern“, so I don’t mind if the suggestion gets closed :)