Keep the chosen stay visible through checkout
On October 25, I worked on the transition from choosing a stay to entering contact details and reviewing payment on Petricani22.eu. The selected rooms and itinerary could disappear from view during those later steps. On a phone, the payment action could also scroll away. The person was being asked to continue a booking while losing some of the context needed to check what they had chosen.
The correction restored a compact recap beside desktop checkout and above it on mobile. It showed the selected rooms, the itinerary's actual dates, guest and visit counts, and a route back to the visit schedule. Using the actual itinerary mattered for stays with later arrivals: a summary should describe the chosen arrangement rather than suggest that every part begins on the first possible date. Contact showed the total, while Payment kept it in the existing breakdown to avoid repetition.
The mobile payment action became sticky within the booking layout, so it remained reachable as the person reviewed the content. Desktop policy and arrival-time links were also separated, and accommodation savings appeared once in the estimate. These were presentation changes around an existing decision. Consent, payment eligibility, quote amounts, discount calculation and recovery behavior were preserved. Keeping an action visible should make a decision easier to complete, not remove the conditions that make it valid.
The completed local work was checked in Romanian and English at desktop and two phone sizes using the real planner with synthetic availability and quotes. Checks covered the recap, schedule link, scrolling, consent and changed-price acceptance while retaining guest details. The implementation was committed on October 25 and merged after midnight on October 26 in Bucharest. No real booking or payment was created for the checks; physical phones, Safari and live deployment were not established by that evidence.
Reflection
A checkout is easier to review when the chosen product remains visible beside the next action. For Petricani22.eu, the useful change was to preserve that context through the later steps. A compact recap and a reachable control can improve continuity without changing the underlying transaction.