Enforce brand LRP first for MAP compliance

Right now, MAP Compliance on the Product Pricing page only checks against MAP/PMAP values. The problem is that many brands now provide an LRP (Lowest Retail Price) that’s meant to be the true minimum — but the system doesn’t use it. That leaves us doing manual updates to MAP/PMAP tables just to stay compliant, and it’s easy to slip below what the brand actually requires.

Why this matters

• We spend extra time maintaining MAP/PMAP values.

• MAP/PMAP often don’t match the real minimum price when an LRP is given.

• Risk of compliance issues when prices dip below the brand’s rules.

What would help
When MAP Compliance is turned on, the system should automatically enforce pricing using this priority:

1. LRP (if available)

2. PMAP (if no LRP)

3. MAP (if no LRP or PMAP)

4. No enforcement if none exist

This should happen in the background alongside our usual LAP sale price rules. For example: if the LAP rule calculates $1,899 but the brand’s LRP is $1,949, the system should automatically set the price to $1,949.

Extra touches that would make it clear

• If someone tries to enter a price below the enforced minimum, block it and show the same validation error we already see for MAP.

• A tooltip on the MAP Compliance toggle explaining:
  “When enabled, MAP Compliance ensures each model’s Sale Price never goes below its allowed minimum. The system prioritizes LRP if available, then falls back to PMAP or MAP.”

The request
Please update MAP Compliance so it always checks LRP first, then PMAP, then MAP, with the same error-prevention behavior we already know. That way, we can stay compliant automatically without constant manual upkeep.