Hello,

First of all, I want to clarify that I am highlighting an automation issue to help you understand the problem, but the unexpected behavior comes solely from Amelia.

I work extensively with coupons. I have an automation that allows me to use them as gift cards across my different payment methods (WooCommerce e-shop, in-store via the Square cash register, and Amelia).

However, I have noticed that the way coupons are managed is very surprising. Specifically, if an appointment is booked using a coupon, the amount paid equals the value of the coupon. This means that if I update my coupon, the deposit paid by my client is directly affected, even though it shouldn't be linked.

Here is an example:

• I have a coupon with a deduction of €100.
• My client books a service costing €90.
• My automation adjusts the coupon value to €10 so that my client can continue using their remaining balance.
• However, in the appointment details for my client, instead of seeing "deposit paid = €90," I see €10, as that’s the remaining value on the coupon. If the coupon balance is reduced to €0, the deposit paid doesn't even appear.

What I want to emphasize is that the amount of a deposit paid for a service should be a fixed value and not linked to any other information that could be modified.

What does the technical team think? Could an update be implemented to address this? The impacts are significant, even for someone using this feature in a more standard way. For instance, a "Welcome" code offering €10 off in 2024 that is updated to €12 off in 2025 would affect all appointments that used this discount in 2024.

Thank you.

Hello,

Here, I'm not reporting a bug, but an astonishing development choice, and a source of error that has a major impact.

In fact, the information for appointments booked using an Amelia coupon is unreliable because it depends on coupon updates.

When I make a reservation with an Amelia discount code, the total amount of the transaction is correctly recorded. However, if I update this coupon at a later date, this also modifies the deposit payment for previous bookings, creating an inconsistency.
For example, a "Welcome" promo code at 10% in January, if changed to 15% the following month, will impact all bookings made with the old code, resulting in errors on deposits.

I understand that this is not a bug, but a surprising development choice that impacts the consistency of booking figures. Payment information is normally stored in hard copy, and should never be dependent on any system update.

I understand that at your level you're not in a position to answer my question, so could you please pass on my ticket to the technical team so that they can consider a possible solution?

Thank you in advance for your help.

Best regards,