A promotion and a rate plan rule contradict each other on an OTA and the guest ends up with a price nobody intended, and this explains the usual conflicts and how to prevent them before they ship.
You run a promotion on a channel, and the price a guest actually pays doesn't match either your standard rate or the discount you thought you'd configured — it's some third number produced by two rules stacking in a way you didn't plan for. Promotion and rate plan conflicts are mechanical, not random, which means they can be checked for before they go live.
You enable a promotion — a limited-time discount, a last-minute rate, a seasonal offer — on top of a rate plan that already has its own restrictions: a minimum stay, a non-refundable condition, a child-pricing structure. The guest-facing price ends up either lower than intended, because the discount stacked with another active adjustment, or the booking doesn't allow a date range it should, because the promotion's rules and the rate plan's rules disagree about what's valid.
The symptom is almost always noticed after a booking lands, not before — which is what makes these conflicts expensive. By the time the wrong price shows up on a reservation, the booking is usually already confirmed.
A rate plan carries its own set of conditions — cancellation policy, minimum length of stay, occupancy pricing — and a promotion layers an adjustment on top of all of that, usually a percentage or fixed discount applied to whatever the rate plan already produces. Each piece can be configured correctly on its own and still interact badly, because the promotion engine and the rate plan engine don't always evaluate conditions in the order you'd expect, and a channel's own promotion rules can override or ignore a restriction your rate plan set.
Before activating a promotion on a rate plan that already has restrictions, run a test search on the channel's guest-facing side for a few representative dates and read the actual price and conditions shown — not what the extranet's configuration screen implies should happen. Check the edges deliberately: the first and last day the promotion is valid, the minimum stay boundary, and a date where another promotion might already be active. If any of those produce a price or condition you didn't intend, fix the conflict before it reaches a real guest, not after the first incorrect booking.
Read-back verification applies to promotions the same way it applies to any other rate change — once a rate plan or promotion update is pushed, the system reads back what the channel actually stored and displays, rather than trusting the configuration screen matched intent. Prime Shield adds the guest side of the check, comparing the rate you sent, the rate you intended, and what the guest actually paid, and flagging a gap worth more than 5% in plain money. Together they catch a stacking conflict close to when it happens instead of after several bookings have gone out at the wrong price — the public demo at try.primehostpartners.com is open to try without signing up.