If you sell brand-authorized products on Amazon Business, you already know that MAP and MSRP compliance can be just as strict on the B2B side as it is on consumer pricing. Sometimes stricter. We added MAP and MSRP enforcement to consumer repricing a few months ago. Those same controls now live on the B2B side, with a dedicated set of toggles so you can configure each stream independently.
Four new toggles, one new section
Open any repricing strategy that has B2B pricing enabled and you will find a new "B2B Safety Nets" section in the editor. Four toggles cover every common scenario. "Respect MAP for B2B" never lets the B2B price drop below the manufacturer's minimum advertised price. "Always price B2B at MAP" sets the B2B price to exactly the MAP value every time. "Cap B2B price at MSRP" prevents the price from going above the suggested retail price. "Always price B2B at MSRP" pins it to MSRP. Each toggle has a short tooltip in the editor so you can pick the right one without leaving the page.
Why two sets of controls
B2B and B2C pricing for the same product are rarely identical. A brand might let you discount aggressively to consumers but require strict MAP compliance on bulk B2B orders. Or the opposite, with looser B2C rules and tighter B2B. Splitting the toggles lets you honor each agreement without compromise. You can run a competitor-driven B2C strategy that floats below MSRP, while pinning the B2B offer to exactly the MAP value the manufacturer requires.
The wizard prevents conflicts
Some combinations do not make sense, for example asking the engine to always use MAP and always use MSRP on the same B2B stream. The strategy editor disables those combinations automatically, with an inline message that tells you which toggle to switch off first. There is also a hard rule we never break: the B2B price is always capped at or below your B2C price. If MAP would push B2B above B2C, the B2C cap wins.
Safe fallback when data is missing
If a listing is assigned to a strategy that requires MAP but does not have a MAP value on file for that product, the engine does not freeze the listing or refuse to update it. It falls back to your normal pricing logic for that listing and writes the fallback reason into Pricing Activity, so you can immediately see why the rule did not apply. Same goes for MSRP. Your catalog can have partial coverage and the strategy still works for everything else.
Example
You sell an authorized brand of professional cookware. Your B2C strategy is competitor-based: beat the Buy Box by $0.50, with a floor at cost plus 15% margin. The same product on Amazon Business has a manufacturer-required MAP of $129.99. With the new toggles, you enable "Always price B2B at MAP" on the B2B side of the strategy. Every B2B submission for that listing now goes out at $129.99, while the B2C side keeps reacting to competitors. One strategy, two compliant streams.
Where you will see the result
Pricing Activity already separates Consumer and Business price changes into their own streams. Each entry shows the rule that drove the price, including when MAP or MSRP overrode the competitive logic. Open the activity drawer on any listing to confirm at a glance that your B2B price is sitting where it should be.