We're Moving to a New Support Platform – Starting June 1st!

We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.

You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.

While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.

We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.

Thanks for your continued support and trust – we’re excited to bring you an even better support experience!

Okay
  Public Ticket #4000655
Problem with multiple persons booking for services (1+1 free)
Open

Comments

  • Jakub started the conversation
    2 days ago on Friday at 1:24pm

    Dear Amelia Development Team,

    I'm configuring Amelia Pro (currently v8.2.1) for a normobaric chamber booking system and have encountered a significant limitation regarding capacity management when services/tickets represent a varying number of actual participants.

    Our Use Case:

    • A single normobaric chamber with a strict maximum capacity of 9 persons per session.
    • Sessions are at fixed times (e.g., 11:30-13:30, 14:00-16:00).
    • We offer multiple types of "entry" services (tickets):
      • STANDARD (represents 1 person)
      • SENIOR (represents 1 person)
      • CHILD (represents 2 persons - child + guardian)
      • DISABLED PERSON (represents 2 persons - disabled person + guardian)
    • Different customers should be able to book any mix of these ticket types for the same session until the 9-person capacity is reached.
    • Preferred booking flow: Customer selects ticket type (Service) first, then the desired time slot.

    Current Problem & Limitations:

    I have attempted to use the "Services" module with the "Resources" feature (e.g., a "Chamber" resource with quantity 9, shared across all services and assigned to 9 "dummy" employees to allow concurrent bookings of different service types).

    However, the core issue is that Amelia's "Resource" quantity (and similarly, "Event" total spots) counts each booking/ticket as consuming one unit of capacity, regardless of whether that ticket actually brings 1 or 2 (or more) people.

    • Example: If the "Chamber" resource has a quantity of 9:
      • A "STANDARD" booking (1 person) uses 1 unit of the resource.
      • A "CHILD" booking (2 persons) also uses only 1 unit of the resource.
    • This allows a scenario where, for instance, 9 "CHILD" tickets could be booked, resulting in 18 people, far exceeding the chamber's 9-person limit. The system does not prevent this.
    • This forces us into manual, error-prone monitoring and intervention to prevent overbooking.

    I managed to overwrite the functionality with a simple snippet, however it works only for single bookings. After adding more than 1 booking to cart, clients have to manually include additional persons using "Bringing anyone with you" option (the system ignores my custom code).

    If you need more detailed explanation, I'm looking forward to describe it thoroughly.
     
    Thank you for your excellent plugin and ongoing support.

    Sincerely, Jakub Potocki