Arrangements vs objects

Frequently asked question: is it useful to make use of arrangements? As a guide in making this decision, this article highlights several aspects that may influence it.

Relevant characteristics

This list is not intended to be exhaustive:

1. Price calculation of the arrangement.
   Is the price of a combination of objects different from the sum of those objects?
   If so, a combined arrangement will be needed (shopping cart = no).
2. Is the price the sum of the parts?
   Then the decision is more difficult. If you choose an arrangement, it will at least be a "shopping cart".
3. Are usernames used, or are reservations accepted without usernames?
4. Is it possible to modify and/or cancel reservations?
   Is this per sub-reservation or the entire reservation at once?
5. Is a payment option offered?
   What happens if part of the reservation is canceled or changed?
6. Is the workflow already determined for the objects?

Workflow

Items 3 to 6 are related to the workflow.
User wishes and/or requirements for the workflow play a crucial role. Note that workflow steps can be implemented at both the arrangement level and the object level. These workflows may overlap.

In short: a workflow can quickly become very complex.

Impact

It is important to consider the impact of a shopping cart in advance.
Functionality and complexity, as well as user-friendliness and management (e.g. of workflow/templates), must be weighed against each other.
Keep in mind that every step of the workflow must be tested. Do you receive the right email/SMS at the right moment?

For many users, testing is a major hurdle. This argues in favor of a simple setup, and sometimes for the decision not to use a shopping cart.
Still want to use a shopping cart? Then take the time to write down and execute all test cases.

Timing of implementation

Implementing a shopping cart before the system is put into use is relatively easiest. After all, a test round has already been planned.

Are you implementing a shopping cart while the application is already in production (actively in use)?
That is possible, but requires even more planning. You have to consider the start and end situation, but also all steps in between. Transitioning from one workflow to another also impacts existing reservations. That makes the puzzle considerably more complex…