We’ve encountered an issue with WPAmelia’s group booking calculations, particularly when applying coupons.

• We have a service that allows group bookings (1–18 participants).
• The price per person is 999 kr, so for two people, the total should be 1,998 kr.
• However, Amelia calculates the total as 1,598.40 kr instead of 1,998 kr before applying any discounts.
• When a 999 kr coupon is applied, the final payment is incorrect.
• Stripe metadata correctly shows 999 kr, but only 749,25 kr was actually charged.

• An earlier booking in the same group had a 20% discount coupon applied, and it affected all participants in the group—even bookings made afterward.
• We later removed that 20% discount coupon, but this new issue appeared immediately after.
• Now, when a 999 kr gift card is used, the final charge is incorrect.
• The issue only happens when a coupon is applied—if no coupon is used, the total price and payment processing work correctly.
• This issue only affects group bookings—individual bookings with a coupon work fine.

It seems like WPAmelia is still applying a hidden discount from the earlier 20% coupon or miscalculating the total amount when multiple participants are booked, leading to incorrect payments being processed.

Can you investigate and provide guidance on how to resolve this?

Best regards,
Martin

Dear Stefan,

Thank you for your response. I want to clarify the exact issue I’m experiencing, as I believe the core problem lies in how WPAmelia handles group bookings with coupons—specifically when a discount is applied after an initial group booking has been made.

1. A customer books a group of 2 for service ID 199, and the correct total price is calculated.
2. Later, another customer books service ID 199 and applies a 20% discount coupon.
3. This unexpectedly applies the discount retroactively to the first group booking, reducing the price for the previous customer as well.
4. After removing the 20% discount coupon, a new booking is made for 2 people using a 999 kr fixed discount (gift card) for service ID 199.
5. The finance system in WPAmelia correctly shows 1,998 kr as the total payment due after the discount.
6. However, only 749,25 kr is actually paid, even though the metadata transfer to Stripe correctly lists 999 kr.
7. The issue only happens when a voucher is applied—group bookings work fine without a discount.

• In Denmark, all prices shown to private customers must include VAT at all times.
• Customers must always see the full amount they are expected to pay, and the discount should be applied accordingly.

1. Why is a discount applied to previous group bookings for service ID 199 when a coupon is used later?
2. Why does WPAmelia’s finance section show the correct amount (1,998 kr) but only 749,25 kr is processed by Stripe, despite the metadata transfer correctly showing 999 kr  (after the coupon is calculated)?
3. Is there a issue or bug in how WPAmelia processes group booking discounts across multiple bookings for the same service ID?

I would appreciate your insights on this issue, as it is causing significant discrepancies in payments.

Best regards,
Martin

Thank you for your response and for attempting to reproduce the issue. However, the test you performed does not fully reflect the scenario we described.

You tested a straightforward booking where:

1. A service is booked for two people at full price.
2. A second booking applies a 20% discount, correctly reducing only that booking’s total.

This is not the issue we are experiencing. Our issue occurs when a discount is applied to a later booking but retroactively affects earlier bookings.

1. Book a group of two for service ID 199. Ensure the total is correctly calculated.
2. Make a new booking for the same service ID 199 but apply a 20% discount.
3. Check if the first booking is unexpectedly affected by the discount as well.
4. Now remove the 20% discount and try booking another group of two with a 999 kr discount.
5. Check if the WPAmelia finance system correctly shows 1,998 kr due but only 749,25 kr is actually processed in Stripe—even though the metadata sent to Stripe correctly states 999 kr.

For security reasons, we cannot provide direct admin access. However, if you need to troubleshoot on our live system, we can:

• Provide detailed logs/screenshots.
• Run tests with debugging enabled and share relevant data with you.
  
  

We have also now moved away from services to events, but the issue remains.

Please let us know how you’d like to proceed securely without compromising site integrity.

Best regards,
Martin

Dear Stefan,

Thank you for your private response. We have disabled the coupons in WPAmelia because the system’s behavior with group bookings and discount handling is not only unreliable but has also become more problematic after transitioning from services to events.

It is clear that my previous messages were not fully read, as the testing scenarios you described did not match the specific issues I outlined. I am not particularly impressed with the support style so far, as there has been a lack of clear communication and concrete action steps.

1. Retroactive Discounts: Applying a new discount coupon still affects previous bookings for the same event, leading to incorrect payment amounts.
2. Services, Discrepancy in Stripe Payments: The Stripe metadata shows 999 kr, but only 749,25 kr is processed, causing serious financial inconsistencies.
3. New Issue After Switching to Events:
   • When applying a 100kr discount coupon to an event priced at 999 kr Incl. VAT, the subtotal changes incorrectly to 974 kr before the discount is even applied.
   • The final amount displayed is 874 kr Incl. VAT, which does not match a 100 kr reduction from 999 kr(which should be 899 kr).

• In Denmark, all prices shown to private customers must include VAT at all times.
• The incorrect subtotal and final amount displayed are not only confusing but also risk non-compliance with Danish tax laws.

I must reiterate that providing admin access to our live site is not an option, as it would be unprofessional and insecure. I had previously offered alternative ways to assist in troubleshooting, including:

• Providing detailed logs and screenshots.
• Enabling debugging and sharing relevant data.