Booking Manager Service
Background service that automatically cancels un-ticketed bookings, saving ~$23K-$27K total across 6 OTA clients
Developed a critical background service using ASP.NET Core & Hangfire that automatically cancels un-ticketed bookings before the last ticketing time. This solution reduced ADM penalties by $4,500-$6,400 per month per OTA, achieving total savings of ~$23,000-$27,000 across 6 clients.
What it does
A background service that watches bookings approaching their last ticketing time and automatically cancels the ones still un-ticketed — before the airline can charge an Agency Debit Memo penalty for holding them.
Scale
Running across 6 OTA client platforms, it reduced ADM penalties by $4,500-$6,400 per month per OTA, for a total saving of roughly $23,000-$27,000.
My role
Built it end to end.
Why this stack
Hangfire on ASP.NET Core for recurring job scheduling with retry semantics, backed by SQLite for persistence — deliberately lightweight, since the service only needs to survive restarts with its own job state intact, not share a database with the platform it protects. Keeping it isolated means a problem here can't take the booking flow down with it.