The short answer
Map the full route from pricing tool to PMS to booking channel, then name one place to control each field. Confirm the fields, sync timing and override order for your exact integration before turning on automatic rate updates.
Who this is for: Hosts connecting a standalone pricing tool to a PMS or investigating why a calendar rate changed unexpectedly.
What to take away
- A PMS connection badge does not prove which pricing fields move.
- Manual edits can be overwritten on some third-party sync paths.
- Test a small group of dates in the final booking channel before a broad rollout.
Draw the rate path before connecting
Write the three systems in order: pricing tool, PMS or channel manager, and booking channel. For each one, record where you edit the nightly rate, minimum stay, discounts and promotions. A tool may send a recommended price while another system changes what a guest finally sees.
Hospitable documents accepting nightly rate and minimum night stay from its third-party dynamic-pricing connections. That is a useful concrete scope, but it is not a promise about every PMS or every integration.
Who wins when two systems disagree?
For a named integration, ask which value wins after a manual calendar edit and when the next automatic sync runs. Hospitable warns that a manual rate entered in its calendar can be overwritten by the next third-party pricing sync. Separately, its own built-in Dynamic Pricing documents manual date overrides. These are different workflows; do not combine them into a single universal rule.
Write the answer beside the control your team will actually use. If an override must be entered in the pricing tool rather than the PMS, train everyone on that location.
Check activation and timing
PriceLabs says importing a listing is not the same as enabling price sync: rates are pushed only after Enable Price Sync is on. Its included automatic sync runs once every 24 hours, with a Sync Now option. Ask the vendor what timing and manual actions apply to your connection and how a failed or delayed sync appears.
Keep the old rate visible until you know the first new rate has reached the destination you intended.
Run a controlled connection test
Choose one property and three dates: a normal weekday, a local high-demand date and a short gap. Note the source rate and minimum stay, enable the supported connection, then inspect the PMS and the channel's nightly accommodation rate after discounts for those dates. Make a controlled override and observe the next sync.
If a field does not arrive, pause rollout and ask which part of the path owns it. Do not infer that other listings will behave identically from a logo or a successful account login.
- Record the property/listing mapping and rate owner.
- Compare source, PMS and channel for the same dates.
- Check the timestamp or status of the last successful sync.
- Document how to pause updates and restore a manual rate.
Keep exceptions visible after launch
A connected price can still be affected by channel-level discounts, promotions or restrictions. Review the rate the tool sent and the channel's nightly accommodation rate after discounts for the same date; inspect the full guest total and host payout separately. Assign one person to resolve discrepancies and record whether the correction belongs in the pricing tool, PMS or channel.
Compatibility is a field-by-field operational claim, not a simple yes-or-no badge.
Common questions
Will a manual PMS price stay in place?
It depends on the integration. Hospitable says a third-party pricing tool can overwrite a manual calendar rate at its next sync, while its own native Dynamic Pricing has a different manual-override workflow. Verify your specific connection.
Does a successful connection mean all pricing settings sync?
No. Check nightly rate, minimum stay, discounts, fees and restrictions separately, along with direction and timing.