Overview
What I shipped
Full-stack
Implemented end-to-end Ticket Protection (formerly Booking Protect) across cart, checkout, order history, and email confirmations in the Cultural District Rails app.
Context
Checkout needed optional ticket insurance with consistent cart, confirmation, and order-history visibility.
Problem
Add Ticket Protection to the purchase flow, ensuring eligibility gating, pricing, line items, and user messaging are accurate end-to-end.
Approach
Feature-flagged rollout covering cart selection, TMS order line integration, and downstream confirmations with CMS-managed copy.
Key decisions
Renamed Booking Protect to Ticket Protection for clarity; gated availability via booking_protect_allowed/ticket_protection_allowed flags; ensured removal controls and line-item display in cart and summaries.
Implementation
Added flag-driven eligibility and cart option; created/remapped line items through TMS; surfaced copy in cart, confirmations, and order history; allowed user removal of protection; synchronized performance data and CMS titles.