A configured action path, checked for the hotel setup.
Peaqplus currently supports channel-manager paths for D-EDGE and SabeeApp CHM. A supported system name does not mean every version or setup accepts the same actions. During setup, we confirm the connector, property routing, room and rate mapping, and the actions available to the selected Pricing workflows.
- Rates are sent only after automatic saving or human approval in Pricing
- Automation Rules can write restrictions only when the configured connection supports them
- Existing distribution mapping determines which assigned routes receive a change
- The returned delivery status is logged as success or failure
- The PMS remains the analytical source; the channel manager is the optional action path
Send the action the hotel chose — only where it is supported.
Automatically saved or human-approved rates from Pricing can be sent through the configured connection. Room, rate and route mapping must be in place.
Automation Rules can write minimum stay, no-arrival or no-departure only when that action is supported for the configured connector.
Day or channel-group actions are limited to the scopes supported and mapped for that hotel. No universal all-channel action is assumed.
Inventory updates are not a universal capability. If the connection does not explicitly support and use them, inventory remains in the hotel’s existing PMS or channel-manager workflow.
One decision can target several mapped routes.
Channel groups such as “Free Sale” or “Corporate” can help the hotel apply one Pricing decision to several assigned routes while leaving another group unchanged. The existing distribution setup remains the source of truth for where those routes lead.
The mapping is agreed during setup; Peaqplus does not discover or rebuild the OTA configuration automatically. If the channel-manager setup changes, review the affected group and route mapping before relying on the next send.
See what Peaqplus saved and what the connection returned.
The audit separates the hotel’s pricing decision from the reported delivery result:
- Decision record — the saved rate, date and scope, with whether it was Automatic, Accepted, Overridden or Manual and the relevant timestamp.
- Delivery result — the configured connection, requested action and the success or failure status returned to Peaqplus.
A successful channel-manager response means the configured connection accepted the request. It is not a promise that every downstream OTA displayed the change instantly.
Keep the analysis. Scope the write path separately.
BI Core, planning and Decisions can still run from the supported PMS data path without a channel-manager write connection. Bring the exact channel-manager name and version to the demo; we review the available connector before promising actions, cost or timing.
Common questions.
See a supported delivery path without touching live channels.
In a 45–60 minute walkthrough, a simulated hotel creates a sample Pricing decision, routes it through a non-live demonstration path and shows the decision record and returned status separately. We then check the exact channel-manager setup your hotel uses.
The demo is free and needs no live credentials. Pricing has a €135 setup fee with 1 hour of training when selected.