Your new minimum advertised price takes effect. Most authorized resellers update their listings, but a few continue advertising at the old price.

One says its product feed has not updated. Another points to inventory purchased before the increase. A third corrects its listing after a warning—then drops the price again the following weekend.

Should all three receive the same response?

Not necessarily. But the difference should come from your documented policy, verified evidence, and each seller’s history—not from which account manager argues hardest for an exception.

Use warnings to address verified violations at the appropriate stage of your policy. Escalate when correction deadlines or repeat-offense rules are triggered. Consider a supply cutoff when the applicable threshold has been reached and the decision has cleared operational and legal review.

The goal is not to punish every transition mistake. It is to make the new MAP meaningful without turning a price increase into inconsistent enforcement.

Start With the Right Price, Policy, and Effective Date

Before issuing a strike, confirm that the price change actually changed MAP.

A wholesale increase changes what your business charges its customers. MSRP is a suggested retail price. MAP addresses covered advertised prices, rather than automatically controlling the final transaction price. These are different concepts, and a notice about one should not be treated as a notice about all three.

For the transition, publish a clear SKU-level schedule covering:

The pricing change: Current MAP, new MAP, affected products, and the relevant policy version.
The timing: The full effective date, time, time zone, and any separate enforcement grace period.
The inventory treatment: Whether the revised policy covers existing stock, along with any defined sell-through or promotional exceptions.

Distinguish a grace period from an exception. A grace period addresses how enforcement is handled during a specified window. An exception changes the applicable treatment of particular advertising, products, or inventory.

For either one, explain whether incidents count toward strike history during that period.

This applies whether the increase follows higher manufacturing costs, freight costs, tariffs, or a broader pricing review. The commercial reason for an increase should not replace clear notice of the policy change.

Old inventory needs an explicit answer

“We bought these units before the increase” should trigger a review of the transition terms—not an automatic exemption or automatic strike.

If your reviewed policy applies the new MAP to covered advertising of existing inventory after the switch date, make that explicit. If certain stock qualifies for a temporary exception, document its scope and expiration.

When your own notice leaves the question unresolved, resolve the ambiguity before escalating. Do not use a warning letter to introduce a rule that was missing from the transition announcement.

A Practical Warn-versus-Cutoff Framework

Use the following as an operational framework to adapt to your counsel-reviewed policy—not as a universal three-strike rule.

What your team verifies	Appropriate response
The new threshold is not yet effective, an exception applies, or the alert is inaccurate.	Correct the record. Do not count it as a violation of the new MAP.
A first qualifying violation occurs after the switch.	Apply the first-stage response specified in the policy, including a warning and correction period where provided.
The same violation remains unresolved after its deadline.	Advance the existing case under the continued-noncompliance provisions.
A seller corrects the issue, then commits another qualifying violation within the policy’s counting period.	Apply the repeat-offense rules rather than restarting indefinitely.
The seller reaches the stated suspension or termination threshold.	Review the evidence, relevant documents, and operational implications before implementing the authorized consequence.

A price increase changes the threshold you monitor. It should not cause your team to improvise a new enforcement system.

When to Warn: A Verified Violation at the Warning Stage

A warning is appropriate when the incident qualifies under the policy and the seller’s enforcement history places it at that stage.

During a transition, investigate explanations such as an outdated product feed, a scheduled promotion that did not end, or a repricing configuration that still reflects the former threshold. These are possible causes to verify—not blanket exemptions.

The distinction matters. An accidental advertising error may still count under the policy. Conversely, a low displayed price may not qualify as a violation at all.

Verify the evidence before sending the notice

Review the seller account, product version, condition, listing URL, observed advertised price, timestamp, and threshold effective at that moment. Confirm that the screenshot shows the relevant seller’s offer—not another offer on the same marketplace page.

Also examine the discount itself. Your review should distinguish seller-created discounts from platform-funded coupons or other promotional displays rather than automatically attributing every apparent reduction to the seller. Brand Alignment’s monitoring emphasizes timestamped evidence, accurate product matching, and coupon review before enforcement.

Recheck the current listing before sending. If it has already been corrected, follow the policy’s treatment of historical incidents without falsely stating that the violation remains live.

Make the warning specific

A useful warning identifies what happened, which rule applied, and what the next step is.

Include the affected SKU and listing, the observed price versus the applicable MAP, the evidence, the policy version, and the seller’s current enforcement stage. Where the policy provides a correction deadline, state the exact date, time, and time zone.

Give the seller a route to submit factual corrections or evidence of an applicable exception.

Avoid messages such as “Please fix your pricing immediately or further action may follow.” They leave too much unanswered: Which price? Which listing? Which deadline? Which action?

A professional warning can be firm without accusing the seller of deliberate misconduct.

The purpose of the first notice is to make the issue unambiguous—not to make the language threatening.

When to Escalate: Missed Deadlines and Repeat Violations

Escalation should follow documented events, not frustration.

Two situations need separate treatment: a violation that never stops, and a new violation after a verified correction.

Continued noncompliance

Suppose a reseller remains below the applicable MAP after the correction deadline. Your team sends another reminder, then another, but the listing never changes.

Keep that case open and follow the policy’s continued-noncompliance process. Do not quietly extend the deadline every time another email goes out.

Equally, do not turn each monitoring scan into an additional strike unless the policy expressly defines incidents that way. Multiple screenshots can document the duration of one event without establishing multiple separate events.

Recurring violations

Now consider a seller that corrects its listing, remains compliant for a period, and later advertises below MAP again.

That is a different pattern. Evaluate it under the policy’s recurrence rules and strike-counting period.

Define in advance whether strikes are counted by seller, SKU, listing, marketplace, or another unit. Establish when an incident closes, how long prior strikes remain relevant, and whether any reset provisions apply.

A correction can close an incident without necessarily erasing its history.

Repeated technical explanations need more scrutiny

“The repricer did it” is worth investigating. It should not become a permanent reason to restart the process.

Ask whether the seller has addressed the underlying configuration, feed, or promotion responsible for the recurring advertisement. Verify the resulting listing behavior rather than relying only on assurances.

You do not need to speculate about intent to document repeated qualifying incidents. Follow the policy’s actual standards.

Likewise, a serious commercial impact can justify prioritizing a case for review. It should not, by itself, manufacture extra strikes or eliminate a notice period.

When to Cut Off: The Threshold Has Been Reached

“Cut off” needs a precise definition.

It might mean temporarily suspending new orders for an affected SKU, restricting access to a product line, or ending the reseller relationship. Those are materially different decisions.

In U.S. federal antitrust guidance, the FTC recognizes that suppliers generally may independently choose their business partners. That principle has limits, including anticompetitive coordination and certain exclusionary conduct; it is not blanket permission for every termination. Federal Trade Commission

Before implementing a cutoff, work through three questions.

Has the applicable policy actually reached this stage?

Confirm the correct strike count, qualifying history, required notices, and elapsed deadlines.

Do not skip a stated warning stage because the price increase is strategically important. Do not promise another opportunity if the policy calls for a consequence that your team is prepared to apply.

Where a policy provides accelerated escalation for particular conduct, use that provision only after verifying that the facts fit it and obtaining the appropriate review.

A suspected distribution breach should be investigated under the relevant distribution terms—not relabeled as additional MAP strikes.

Is the decision supported by a complete record?

The review file should connect the policy to the conduct.

Preserve the applicable policy and price schedule, transition notices, timestamped evidence, exception checks, previous communications, correction history, and the reason the proposed consequence applies.

Check any unresolved factual dispute before approving the action.

Also verify that a material policy change has not distorted the history. For example, moving from a UPP that addresses transaction pricing to an advertising-only MAP policy should trigger a review of which historical incidents remain relevant. Removing a SKU from MAP coverage should stop new MAP strikes for advertising after the removal takes effect.

Have the commercial and legal implications been reviewed?

Have qualified counsel assess the relevant reseller and distribution documents, termination provisions, notice obligations, accepted purchase orders, and applicable law.

Operationally, define the affected account, products, order types, effective date, duration, and any reinstatement process.

Do not assume a decision to stop accepting future business also authorizes canceling accepted orders, withholding accrued benefits, or changing consumer warranty obligations.

A written MAP policy is one part of the review—not a substitute for it.

Do Not Let Account Size Decide the Strike Count

A major reseller may generate substantial revenue. A smaller account may have fewer people available to manage listings.

Those facts can inform the commercial planning around a decision. They should not quietly rewrite the evidence or strike history.

Decide how any permitted discretion will be exercised, who may approve it, and how the reasoning will be recorded. Keep sales teams informed, but do not let an informal sales conversation override the policy administrator’s decision.

The same care applies when another retailer demands that you “do something” about a discounter.

The FTC distinguishes independent manufacturer action from collective pressure or agreements among competing dealers. A brand may receive information about another seller’s pricing, but enforcement should remain the brand’s own independently reviewed decision—not a commitment negotiated among competing resellers. Federal Trade Commission

Validate complaints as leads. Do not treat them as instructions.

Carry the Decision Into Ordering and Distribution

A cutoff notice is incomplete if the next order ships normally.

Assign an operational owner to implement the decision in ordering systems and confirm that the restriction matches the approved scope. Check relevant customer accounts, purchasing portals, and distributor arrangements where applicable.

Be precise when reviewing related entities. A similar name or address is a reason to investigate, not sufficient proof that two accounts belong to the same business.

For a temporary suspension, specify who reviews reinstatement and what the policy requires. Do not let supply resume automatically because the listing looked compliant during one check.

Keep the enforcement record connected to the order decision so sales, operations, and the policy administrator are working from the same information.

Plan for inventory already in the channel

Stopping future supply does not physically remove stock the reseller already holds.

Before the cutoff, assess how much inventory may remain, whether replenishment is continuing through another route, and how residual stock will be handled. Have the appropriate teams review any available return, buyback, or other inventory-resolution options.

If a reseller continues obtaining stock despite a direct-account restriction, investigate the source. Sending increasingly severe emails to the same storefront will not answer where the next shipment came from.

Keep Grey Market Pressure Separate From MAP Strike Decisions

An authorized reseller may argue that it cannot compete while a grey market seller remains below the new MAP.

Treat that as two issues to investigate.

First, determine the authorized reseller’s status under the applicable MAP policy. Another seller’s low price should not create an undocumented exception.

Second, investigate the unfamiliar seller’s identity, inventory, and supply source. Domestic diversion, liquidation stock, and genuine products sourced from another country may require different operational responses.

Do not try to solve both problems with the same warning sequence.

Also keep brand-issued strikes separate from marketplace enforcement. A MAP dispute does not establish that goods are counterfeit or that a listing infringes intellectual property. Amazon’s IP process concerns actual rights violations and allows sellers to dispute claims or provide authenticity evidence. Use those processes only where the underlying facts support them. Amazon Seller Central

A supply decision, an unauthorized-channel investigation, and an infringement complaint are different actions. Each needs its own factual basis.

Measure Whether Warnings Change Behavior

The purpose of a warning is to achieve compliance. If your warnings are not producing that result, the sequence needs adjustment—not more warnings.

After each warning cycle, check whether pricing returned to MAP, how long it took, and whether the same account appeared again at the next violation review. If compliance rates after first notice are low, the warning itself may be unclear, the timeline may be too long, or the consequence may not be credible.

If you see the same seller repeatedly cycling through warnings without reaching a cutoff, the framework is not working as designed. Either the threshold is too high, the documentation is not reaching the decision-maker, or the commercial relationship is being treated as a reason to avoid consequences.

Use your managed MAP pricing enforcement program data to track compliance rates by account tier, channel, and product category. Patterns in the data tell you where the framework is holding and where it is not.

If your current MAP enforcement notifications are generating responses but not compliance, review the content of the notice itself—not just the process around it.

Make Warnings Useful—and Consequences Credible

A warning that is never followed by a consequence trains sellers to ignore warnings.

That does not mean you should be quick to cut off accounts. It means the consequences you describe need to be ones you will actually implement. If your policy says three violations in twelve months results in a suspension, apply that standard consistently. Sellers who are paying attention will notice when peer accounts are treated differently.

Usefulness means the seller can act on the warning. Include the specific product and channel, the violation date, the current listed price, and the MAP. State clearly what needs to change and by when. Do not send a warning that requires the seller to guess what you observed.

Credibility means you will follow through. Review the enforcement record before each decision. If a seller has reached the cutoff threshold under the written policy, apply the consequence unless there is a documented basis for an exception—and document that basis too.

MAP strike policies work when sellers believe that warnings lead to consequences and that consequences are applied to everyone. Consistency is what makes the system credible. Contact Brand Alignment to review your current MAP enforcement program and identify where your warning-to-consequence sequence can be strengthened.

This article is for general informational purposes only and does not constitute legal advice. MAP policies, selective distribution agreements, and reseller enforcement practices may raise legal considerations that vary by jurisdiction, industry, and individual circumstances. Consult qualified legal counsel before implementing or modifying any pricing enforcement program.

Start Protecting Your Brand Today

Take control of your marketplace presence with fast, effective brand protection strategies.

Every day, unauthorized sellers and MAP violations can erode your pricing, reputation, and revenue. Don’t wait for problems to escalate, start enforcing your policies and reclaim your market authority with our proven tools and expert support.

If you Like it, Share it!

Products

Coverage

Resources

Company