We integrate with the channel manager you're on.
Whatever CHM you're using today, the connection is two-way: Peaqplus pushes rate decisions to it; the CHM sends back your channel structure so Peaqplus stays in step with how you actually sell. Configured once during onboarding — after that, every push finds its own way automatically.
- Two-way sync — rates out, channel structure in
- Standard industry protocols supported — connector picked per hotel
- Inventory sync opt-in — off by default; you decide whether Peaqplus or your PMS drives stock
- Per-hotel routing — multi-property setups handled with a single platform configuration
- Audit-trailed — every push logged with success or failure status
Four fields. One push per decision.
Per room type, per rate type, per day. Direct from your decision in Peaqplus.
Minimum stay, no-arrival, no-departure. Configured at the rate-matrix level, propagated automatically.
Day-level closures. When you mark a date closed in Peaqplus, the CHM closes it on every channel in the affected group.
Room counts. Off by default — most hotels prefer their PMS to drive inventory and Peaqplus to drive only rates. Enable in per-hotel settings.
One decision. Many channels.
Group your OTA channels into logical pools — e.g., a "Free Sale" pool covering general OTAs, a "Corporate" pool for travel-management portals, a "Cancellation Strict" pool for the cancellation-tighter channels. When you make a rate decision targeting a pool, Peaqplus pushes to every channel inside it simultaneously.
You define pools once during onboarding. Refresh from the channel manager pulls the current channel list for any pool — so when the CHM reorganizes underneath, the pool definitions in Peaqplus stay accurate.
Every rate push is auditable.
Every channel-manager request is logged in two places at once:
- The full record — the exact rate we sent, per hotel, with timestamps. Useful when an OTA reports a rate mismatch and you need to see exactly what was pushed.
- The summary — a searchable row with the hotel, the connection, what was sent, success or failure, and when — so you can filter and search across years of pushes.
Silent on success, loud on failure — the way it should be.
Not currently integrated? Let's connect anyway.
We're expanding channel-manager coverage continuously. If your channel manager isn't on the supported list today, tell us during the demo — many systems become natively supported within weeks once we've reviewed the integration spec. Meanwhile, you can run Peaqplus in read-only mode (analytics + decisions, no auto-push) until the native connector is ready.
See a rate push live.
In our 45–60 minute walkthrough (length depends on how deep you want to go), we run Peaqplus on our live demo environment — a simulated property with data that moves day to day — make a sample rate decision, push it through a deactivated test pool, and show you the audit trail. The full path — decision to OTA — in front of you.
No setup fee. We use a test pool to demonstrate.