Explain the stay limit before asking for a price
On October 22, I corrected the feedback for stays longer than a rental's saved maximum on Petricani22.eu. Selecting too many nights could look like a pricing outage. The person had provided dates the property did not support, but the interface suggested that the service could not obtain a price. That difference matters because retrying a service request cannot fix dates that remain outside the allowed stay.
The rental widget and direct checkout page were changed to share a localized explanation of the maximum stay. The message tells the guest to choose an earlier departure date, and booking actions remain disabled while the dates exceed the limit. The widget avoids requesting a quote for that known invalid selection. Once the dates are valid again, normal pricing resumes instead of leaving the person stuck in a previous error state.
The calculation reused the existing date-only night counter. That kept the displayed guidance aligned with the booking model rather than adding a second interpretation of how long a stay lasts. Server-side limits, rates, discounts and booking creation were unchanged. A genuine pricing failure still had its own retry behavior. The correction therefore separated an input problem the guest could solve from a service problem that might need another attempt or later investigation.
The implementation was merged on October 22 after the recorded local verification gate. Focused checks covered both languages, dates just inside and outside the limit, recovery after changing dates, rentals without a maximum and direct checkout links. They also preserved real-outage retry behavior. Those checks support the implemented boundary and its explanation, not proof of a completed real booking or a production deployment observed in this evidence packet.
Reflection
A useful error explains the action that can resolve it. For Petricani22.eu, telling someone the maximum stay was more helpful than presenting an unsupported selection as a temporary pricing failure. Sharing that explanation across entry points also kept the booking journey consistent wherever the guest began.