Development Update – Reservation Archive & PMS Integration
Date: July 2, 2026
Team,
Today’s work produced several important improvements to the Reservation integration between Hostipable, Zapier, and WordPress.
Completed
1. Reservation Archive Redesign
The Reservation Archive page has been significantly improved.
Instead of showing minimal information, each reservation card now displays:
- Reservation Code
- Reservation Status
- Guest Name
- Number of Paid Guests
- Booking Platform
- Check-in Date
- Room Category
- Room Name
- Property Address
- Total Paid
This makes the reservation archive much more useful as an operational dashboard.
2. Property Category Mapping
Hostipable now sends the room category (examples: P2007S4, P2014R1, etc.).
Using this information we can determine:
- Property
- Address
- Building
- Other metadata
This is a major improvement because the UI can now identify the property regardless of which room was booked.
Example:
Room Category
P2007S4
↓
Property
2007 West 100th Street
↓
Display correct address automatically
This opens the door to much richer reservation displays.
3. Reservation Information Display
Reservation cards now contain enough information for staff to quickly identify:
- where the guest is staying
- what platform booked it
- guest count
- payment amount
- exact room
- exact property
without opening the reservation.
Important Next Feature
Guest Reservation Claim
One major missing feature became obvious.
Currently reservations exist independently of users.
Instead, reservations should eventually become attached to the guest’s account.
Desired workflow:
Reservation Created
↓
Guest receives invitation
↓
Guest creates/logs into account
↓
Guest claims reservation
↓
Reservation permanently linked to user account
Benefits:
- Guest Dashboard
- Messaging
- Digital Guidebooks
- Checklists
- Future Reservations
- Loyalty tracking
- Better CRM
- Personalized experience
This is probably one of the highest-value improvements for the platform.
Issue Discovered
The Reservation Archive currently shows duplicate reservation cards after updates.
Example:
Reservation HMP9NNQPXE
Changed
Reservation HMP9NNQPXE
Changed, Edgewater Residence VII
and
Changed
Changed, P2014 Edgewater Residence XIV
This indicates that updates are being inserted as new records rather than updating the existing reservation.
The synchronization process should instead:
Find reservation by Reservation ID
↓
Update existing reservation
↓
Do NOT create a duplicate post
Possible Enhancement
Once the property mapping is stable, we can expose additional information automatically:
- Property photos
- House Manual
- Parking Instructions
- Wi-Fi
- Smart Lock Instructions
- Emergency Contacts
- Maintenance Contacts
- Local recommendations
without requiring additional reservation-specific data.
Overall Progress
Today’s work substantially advances the architecture toward a true PMS-backed reservation system in WordPress.
The reservation archive is now evolving from a simple list into an operational dashboard, while the new property mapping creates the foundation for guest portals, property intelligence, and future automation.
The next major milestone should be implementing Reservation Claiming, which will connect reservations to registered users and unlock personalized guest experiences.
