Found some stuff form the quinta suite.. Lets get that one int here
Date: July 2, 2026
Team,
Today’s work produced several important improvements to the Reservation integration between Hostipable, Zapier, and WordPress.
The Reservation Archive page has been significantly improved.
Instead of showing minimal information, each reservation card now displays:
This makes the reservation archive much more useful as an operational dashboard.
Hostipable now sends the room category (examples: P2007S4, P2014R1, etc.).
Using this information we can determine:
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.
Reservation cards now contain enough information for staff to quickly identify:
without opening the reservation.
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:
This is probably one of the highest-value improvements for the platform.
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
Once the property mapping is stable, we can expose additional information automatically:
without requiring additional reservation-specific data.
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.
hope the fact I added “hospitable” as a category does not impact the visibility. This post as it is should only show to administrator level users.
We are able to capture or cancel payments on stripe, even the payments done through hospitable. today I had to do that with a paymment from Jeniffer Lee, that was in limbo I simply went to strtipe
/transactions and uip top it has the two options to capture or cancel the payment that has already been authorized, and that is why Jeniffer had the ability to send us the screen shot the previous day showing the payment already there.
And above the two screen shots from the guest informing us that the payment was not yet “captured” – althou8gh the guest said: payment was already taken from my account but not completed yet.
Not suure if this is a typical occurrence but we have to doccument this here as such