Start with the exact system and version you run today.
Peaqplus currently has supported paths for the systems below. The list qualifies the connection route; it does not mean every version exposes the same fields or history.
We confirm field coverage, available history and access requirements before setup.
Map the fields your hotel actually has.
Read the reservation and stay fields exposed by the supported connection — such as stay dates, room nights, status, room or rate type and guest count. Exact coverage varies by PMS and version.
Map room revenue and the other categories supplied by the PMS. F&B, ancillary revenue, local fees or package detail remain separate only when the source exposes them separately.
Map the available source codes to the hotel's agreed reporting structure. The hotel validates the mapping before live use, so the same label means the same thing in each recurring view.
Load the historical data available through the agreed path, then store recurring imports as dated snapshots. The backfill period depends on the connector and source data.
Map the hotel data. Do not rebuild the hotel around the software.
The PMS remains the source system. During onboarding, we map the available codes and categories into an agreed Peaqplus reporting view and validate the result with the hotel. Existing PMS reports, an RMS, a channel manager or a revenue provider can keep their current jobs; Peaqplus adds the analytical and decision layer.
- Hotel-specific mapping — available source codes are mapped to the agreed reporting structure
- Multi-property management — property-level data remains separated under one Peaqplus account
- Currency handling — source and reporting currencies are agreed from the fields available
- Group, MICE and ancillary detail — preserved where the PMS exposes it separately
- Read-only analytical path — reservations and the live PMS database are not changed
Supported PMS paths are typically live in 7–14 days.
Timing starts once the required access and data are available. Missing fields, custom development, data-quality work or chain-level IT approval can extend the path.
Confirm the PMS name and version, available connection path, access owner, reporting needs and the fields the hotel expects to reconcile.
Configure the supported API, export or import path after the required access is available. Custom integration work is scoped separately before development starts.
Agree segments, channels, revenue categories, currencies and group fields, then compare the first load with a PMS report the hotel trusts.
After validation, start the recurring data flow and train the team on the mapped views. BI Core setup includes 2 hours of team training.
Each validated recurring load creates the next dated snapshot. A PMS upgrade, new source field or mapping change may require another review.
Verify the path before promising the connector.
Bring the exact system name and version. We review the available API, export or import path, the fields it exposes and the access needed from the PMS provider or hotel IT.
A supported import or custom integration may be possible, but we scope the connector, cost and timing only after that review. One trusted PMS report helps us define the required reconciliation.
What validated PMS data unlocks.
- Dated snapshots of each validated recurring PMS load
- Pickup and pace analysis from changes between snapshots
- Same Point YoY and Time Machine on preserved historical states
- Mapped filters for the segments, channels and accounts available in the feed
- Group, MICE and ancillary analysis when the source provides the required detail
- Property-level separation for multi-property management
- Budget and Forecasting beside the latest available hotel snapshot
- Decisions and Revenue Meeting linked to the evidence the team reviewed
Common questions.
Bring your PMS name, version and one report you trust.
In a 45–60 minute walkthrough, a simulated hotel with data that moves day to day shows the dated analysis, mapping questions and decision workflow. We then check how the same path fits your PMS and reporting needs.
Simulated data. No PMS credentials or system changes required for the demo.