Camp enrollment form

There are many ways to approach this, but with such vague requirements, it's not possible to suggest a specific approach. For example, how many guardians? Do the guardians live at the same address as the children, or each other? How many children? Can the children be enrolled for different times, or are all enrollments for the same weeks? Do add-ons apply across all enrollees or can add-ons be different for them?

Truthfully, you may be better off getting help from a developer that can help at least with the form(s) and view(s) design. Trying to explain how to approach this with any specificity is beyond the scope of the help I'm willing to provide as a community volunteer. Maybe someone else seeing this could help you.

Ideally, we would have a form where people could select multiple options that get added to a cart. Then, they could checkout.

Instead, it looks like formidable has a per product form option. If one parent is enrolling a kid in two weeks, we would not need them to fill out the same form twice though. Also, if they had two kids for two weeks, we would not want to request that they fill out the same form four times.

Any solutions for that?

Anything is possible if you think through the architecture and have the right developer. I would imagine you would need something that allows you to carry and relate persistent data, such as an ID, email, or some unique piece of data. Your user would then refer to that persistent data and it would load the data associated with that particular entry. Ideally you would be requiring a user account to access your application so that you can have the form set to logged in users only for security purposes. If you choose to not require users to register, then you have higher data security risks.