Availability search combines selected dates, guest capacity, physical inventory and blocking records. An empty result, an invalid request and a missing catalogue Page are different problems and need different checks.
Reproduce a controlled search
- Use one published/active room type with known quantity, capacity and base price. A featured image is optional.
- Select future check-in/check-out dates with check-out after check-in, and valid adult/child counts.
- Submit from the configured Booking Page or supported theme form. Keep the actual language context and route.
- Record whether the result is an input error, a valid zero-result state or a routing/rendering failure.
Check-out is exclusive, so overlapping occupied nights determine inventory. Capacity per room and the number of physical rooms are separate inputs. Increasing a photo, bed label or room area does not increase guest capacity or stock.
Inspect inventory and routes
Review overlapping bookings and their blocking lifecycle states, manual inventory blocks and any externally synchronized blocks. Pro iCal/API sources can consume inventory without a full website guest record. Do not delete their blocks to force a result; inspect and repair the owning source.
Check the assigned Rooms and Booking Pages, publication/access status and actual permalinks. A renamed Page should use its current assigned permalink. Deliberate unassignment or deletion is not an instruction to recreate Pages silently. Do not use Save Permalinks as the default fix for an application-level availability or assignment error.
Search is not a reservation
A displayed available room and price do not lock stock while the guest browses. Book Now previews and final creation recheck inventory and price. If stock changes, the customer must review the current result instead of bypassing a server rejection.
For multilingual forms, verify the submitted destination retains the selected language and dates. For missing styles or photos, compare the native Core output and active theme without changing availability logic.
Verify and recover
Retest the same synthetic stay after the targeted correction, then test a genuine no-availability case and a date validation error. Preserve operational reservations and source-managed blocks. If a cache is involved, clear only the relevant safe cache after fixing the underlying route/data issue. See managed Pages.
