Monitoring MAP Compliance End-to-End

This page walks through the complete MAP compliance cycle: recording your prices, detecting violations, and resolving each case with a retailer. It is written for brands. Reference detail for individual features lives on MAP Price Configuration, MAP Violations, and Alerts.

Step 1: Record your MAP prices

Violation detection only runs against products that have an active MAP price. You can add prices one at a time or upload them all at once.

Adding or changing prices individually

Open MAP Price Configuration, under Governance in the left navigation. The page itself is titled MAP Configuration. Each row in the catalog shows a product’s current MAP status: Active, Scheduled, Expired, or No MAP Price. A search box and a row of status chips (All, With MAP Price, No MAP Price, Active, Scheduled, Expired) narrow the catalog to a specific product. Open a row’s Actions (⋯) menu. Products with an Active or Scheduled price offer Change MAP Price and Delete MAP Price. Products with no current price, including one whose price has expired, offer Add MAP Price. Choosing Add or Change opens the editing dialog, where you set:

Price and currency. EUR, GBP, SEK, NOK, DKK, CHF, or USD.
Effective date. Defaults to today; you can back-date when recording historic prices.
Expiration date. Optional; leave blank for an open-ended price.
Notes. Optional free-text for your records.

Choosing Delete MAP Price: for an Active price, choose Set end date to keep it in force until a chosen day, or choose Delete entirely to remove it immediately. The chosen day must be today or later, and on or after the price’s effective date. A Scheduled price offers only Delete entirely.

Uploading prices in bulk

Click Upload MAP prices at the top of the MAP Configuration page to open the upload wizard. Use it when you have a spreadsheet of prices to apply at once. The wizard has three steps.

1. Upload file. On the upload step, click Download Template to export your full catalog as a CSV, pre-filled with any MAP prices you already have. Fill in or update prices offline, then drop the file onto the upload area, or click to browse. The system validates it immediately.

2. Review & fix. The summary at the top names your file and tells you how many products matched, how many are unchanged (they are ignored), how many have a changed MAP price, and how many have errors (they are skipped). A diff table lists every row that actually changes something: add, change, remove, or error, with a “was → now” price comparison. Rows your file leaves unchanged are not listed individually, only counted in the summary. If your file matches the current MAP prices exactly, the step shows “No changes to apply” instead of a table. If any rows are invalid you can click Download failed rows to get just those rows, fix them, and re-upload. Rows can be left blank in your file when a product currently has a MAP price but no price in the upload. When that happens, you must choose how to handle them:

Delete the MAP price entirely. Removes the price immediately.
Set end date. Keeps the price until a chosen date, which must be today or later, then expires it.

Once you are happy, click Apply changes. A line beside the button states what will happen, for example how many prices will be applied or removed and how many rows will be skipped. If you leave the review to open a product and come back in the same browser tab, your review is restored. Restart discards it and returns to the upload step.

3. Take action. After the prices are committed, this step summarises what happened:

How many prices were Added, Updated, Removed or End-dated, and Unchanged. The third counter reads Removed if you chose to delete the prices of blank rows, and End-dated otherwise, including uploads with no blank rows, where no choice comes up.
A Violations card. If the upload produced new MAP violations, it reports how many, and, when they span more than one retailer, across how many retailers. It also reports how many existing violations the upload resolved and the largest single deviation. A View MAP violations button opens the violations page with the newest violations first. If there are none, the card says no new MAP violations were found.
An Alerts card. See Step 2 below.
A list of any rows that were skipped, with the reason for each.

From here, Back to MAP Configuration returns to the catalog and Upload another file starts a new upload.

Step 2: Set up a MAP-violation alert rule

You need an alert rule to be notified automatically when new violations are detected. You can create one directly from the Take action step or through the full wizard later.

Creating from the Take action step

If no MAP-violation alert rule exists, the Alerts card on the Take action step shows a recipient picker and a Create alert rule button. The current user is pre-selected; you can add other org members by name, or any external email address.

Clicking Create alert rule creates a company-wide rule named “Monitor product prices for MAP violations”, with locked defaults and a monitor-from baseline set to the moment of the upload. This means:

Only violations that arose from this upload onward trigger notifications. The pre-existing backlog does not flood your inbox.
Any violations this upload just created are emailed immediately to every chosen recipient.
From then on the rule continues alerting on new violations exactly as any other rule would.

Once the rule is created the Alerts card flips to a summary showing the recipients’ names and an Edit alert rule link if you want to adjust anything later.

If a MAP-violation rule already exists, the Alerts card instead shows who is being notified. If you have more than one MAP-violation rule, only one rule’s recipients are listed. If this upload triggered alerts, the card says how many. Otherwise it confirms the rule is alerting when any retailer’s price falls below MAP. If every MAP-violation rule is disabled, the card says no alerts were sent. An Edit alert rule link is offered when exactly one MAP-violation rule exists; if you have more than one, it links to Manage alert rules instead.

Creating through the Alerts page

You can also build or edit MAP-violation rules through the standard alert wizard on the Alerts page. There you can scope monitoring to specific retailers, or leave it covering all of them, and set a minimum violation percentage so only violations at or beyond that threshold trigger the rule. Rules created there are baselined at their creation time, so they do not fire on violations that pre-date them.

Step 3: Review detected violations

Go to MAP Violations, under Monitoring next to Alerts in the left navigation, at any time to see the current state of all cases.

KPI cards and views

Five cards across the top act as both counters and view selectors. Click any to switch the table below:

Card	What it shows in the table
Active MAP violations	All active cases, open and notified, shown in the products view and sorted by severity
Retailers in violation	A retailer-level summary: products and violations per retailer
Notified	Cases where a retailer has been formally contacted but the violation is still active
Repeated offenders	Active cases where the same product was already resolved at that same retailer and has since started violating again. The card’s number counts the distinct retailers involved
Resolved	Cases marked resolved

Filters

At the top of the page, three filters narrow the table and the KPI counts:

Time range. 24 hours, 7 days, 30 days, or 90 days.
Severity. Minor (0–10% below MAP), Moderate (10–30% below MAP), or Severe (30%+ below MAP). You can select any combination.
Search. Filter by product name or retailer name.

Product view vs retailer view

The default product view lists products with at least one violation, showing the total case count, the number of retailers involved, and the worst severity. The Product, Case scope, Severity, and Detected columns are sortable; the Retailers column is not.

The retailer view groups violations by retailer, shown when you click “Retailers in violation”. Each retailer row can be expanded to show up to five of its active cases, open and notified. When a retailer has more, a View all link opens a dedicated page listing every one of that retailer’s violation cases, with the same time-range, severity, and search filters as the main page.

Step 4: Work a violation case

Click any row in the product view to open the MAP Violation Details dialog for that product.

The sidebar lists all active cases, open and notified, for the product, followed by any resolved cases. Each entry shows the retailer name, its observed price, and its current status badge. Click a retailer to switch the right panel to that specific case.

Right panel: review a case

The review panel shows:

Observed price vs MAP price. The current advertised price, the amount it is below MAP, and the percentage deviation.
Severity indicator. Colour-coded: amber for Minor, orange for Moderate, and red for Severe. Includes an enforcement prompt.
Evidence. When the price was captured and, where available, a direct link to the offer on the retailer’s site.
Violation status. Three buttons, Open, Notified, and Resolved, let you update the case status manually. Clicking a different status opens a confirmation step before the change is saved. Marking a case Resolved requires choosing a resolution reason (Price Corrected, Override Added, False Positive, or Other) and a note. Every other transition besides the initial Open → Notified, including moving off Resolved, or back from Notified to Open, also requires a note explaining why. A resolved case also shows its resolution reason.
MAP Activity. A chronological timeline of status changes, including the automatic change to Notified recorded when you send a notification email, and notes added. Re-notifying a retailer on a case that is already Notified does not add a new entry.
Notes. A free-text field to add an internal note to the case, visible in the activity timeline.

Status definitions

Open. The retailer is currently violating MAP; no action taken yet.
Notified. The retailer has been formally contacted; the violation is still active and being monitored.
Resolved. The retailer is no longer violating MAP based on the latest observed price.

Notifying a retailer by email

From the review panel, click Notify retailer, or Notify retailer again if the case is already Notified, to open the notification composer. The button is not shown on Resolved cases.

Fill in:

Recipients. The retailer contact’s email address.
Subject. Pre-populated but editable.
Email tone. Choose Professional, Assertive, or Friendly. Each tone applies a pre-written template that includes the product name, your MAP price, and the retailer’s observed price. You can freely edit the body; switching tone replaces the body, and a confirmation prompt appears if you have unsaved edits.

Click Send to deliver the email. Sending automatically moves the case status to Notified.

Step 5: Follow notifications and close cases

Receiving alerts

When the violation detection engine evaluates your MAP-violation alert rule and finds new violations, it fires alerts. Those alerts:

Appear as unread events in the Alerts inbox, the bell icon in the navigation.
Are delivered by email, and optionally by Slack, to everyone listed as a recipient on the rule.
Can be reviewed in the inbox, and acted on individually or in bulk: mark as read or unread, postpone, or unsnooze. Postponing an alert sets a snooze. It returns to your unread alerts inbox when the snooze window expires.

Resolving cases

A violation case resolves automatically when observed prices return to or above MAP. It also resolves automatically if you delete or change the product’s MAP price in a way that removes or clears the violation, for example by deleting the MAP price entirely, or by lowering it so the observed price is no longer below it. You can also resolve a case manually from the violation details dialog, for example after confirming off-system that a retailer has corrected their price. Once resolved, the case moves to the Resolved view and no longer counts against your active violation total.

Reopening is available at any time: click the Open status button inside the details dialog to move the case back to active.