Channel Manager & Rate Parity
Lesson 4 / 9Parity engineering

Where parity actually breaks (it's not where you think)

A revenue manager who has spent two years chasing parity breaks knows: 80% of breaks come from 5 specific patterns, 4 of which are not the OTAs' fault. Knowing where to look first saves 4-6 hours per week of investigation time.

The five pattern sources

In rough order of frequency:

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

What this means for diagnostics

When a KAM flags a parity break, the first investigation question is not "did we change the rate" — it is "which of these 5 patterns is this?" The wrong question leads to 2 hours of fruitless searching in the wrong system.

A practitioner runs through the patterns in order: check the wholesaler-leak audit log (most common), check the rate-plan mapping (next most common), check if a mobile/member rate is leaking, check the CM sync timestamps for the relevant period, check the currency conversion. 80% of cases land in the first three.

The fix discipline

Once the source is identified, the fix is rarely just "match the rate." For a wholesaler leak: contact the wholesaler with a 48-hour fix demand and document the breach. For a mapping error: fix the mapping and audit the rest of the rate plans for similar issues. For a stale sync: force-resync and investigate why the original sync failed. The "match and move on" approach treats the symptom and leaves the structural cause for another day.

Finished this lesson?
Mark complete and move to the next lesson.
Where parity actually breaks (it's not where you think) · Channel Manager & Rate Parity · OtelCiro Academy