Dear WPBay Review Team,

Thank you for reviewing Ordrivo Booking Super Pro. Version 7.0.15 addresses the rescheduling concurrency finding.

- After acquiring the per-booking lock, customer rescheduling now reads the post and appointment metadata directly from the database. It validates the current publication state, ownership, status and original date/time from this fresh state, bypassing metadata cached during customer ID resolution.
- The appointment is read and validated again after acquiring the requested date lock. Availability checks and reschedule writes use the fresh state while both locks are held.
- Administrator status changes use the same booking lock. If rejection, cancellation or treatment start commits first, rescheduling returns HTTP 409 and preserves the administrator's status and original schedule. If rescheduling gets the lock first, the administrator action runs against the new pending appointment state.

The updated complete package, changelog and requested staging scenarios are included. PHP lint and live WordPress/database concurrency checks were not available in this packaging environment; the test report lists them as staging checks rather than completed tests.

Best regards,
Baris Beydogan
