MAP Violations

A MAP violation occurs when a retailer lists one of your products at a price below your Minimum Advertised Price (MAP) threshold. Aperture detects violations automatically as product pricing data arrives. It organises them into cases that you can review, notify the retailer about, and resolve.

Violation statuses

Each violation case has one of three statuses:

Open. The retailer is currently advertising the product below MAP, whether newly detected or reopened after a previous Notified or Resolved state.
Notified. The retailer has been formally contacted. The violation is still active and Aperture still monitors it.
Resolved. The latest observed price shows that the retailer no longer advertises the product below MAP. Monitoring continues automatically.

Aperture also resolves active cases on its own. This happens when the observed price rises to MAP or above, and when you change or delete the product’s MAP price so that the observed price is no longer below MAP or the listing is no longer under a MAP rule. The activity log records the reason.

Severity levels

Severity shows how far the observed price falls below your MAP:

Severity	Gap below MAP
Minor	0 to 10%
Moderate	10 to 30%
Severe	30% or more

The MAP Violations page

Go to MAP Violations in the sidebar to see all violations across your entire retailer network.

Filters

Use the filter bar at the top of the page to narrow results:

Time range. Show violations first detected in the last 24 hours, 7 days, 30 days, or 90 days. The default is 7 days.
Severity. Filter to Minor, Moderate, or Severe violations. Minor is 0 to 10%, Moderate is 10 to 30%, and Severe is 30% or more. You can select more than one severity at once.
Search. Type to filter by product name or retailer name.

Summary cards

Below the filter bar, five summary cards show at a glance where things stand. Click a card to switch the table to that view:

Card	What it shows
Active MAP violations	Open and Notified cases combined
Retailers in violation	Retailer-grouped view of active cases
Notified	Cases where the retailer has been contacted
Repeated offenders	Retailers who have an active violation after a previous violation for the same product was already resolved. The count reflects distinct retailers with this recurrence pattern
Resolved	Cases that have been closed

An outline marks the selected card as the active view.

Product view

The default table groups violations by product. Each row shows:

Product. Product image, name, and EAN. The product name links to that product’s price detail page.
Case scope. Coloured dots for the distinct statuses present, plus the total case count. Red is Open, amber is Notified, and green is Resolved. The dots reflect whichever filter card is active.
Retailers. The retailer of the most recently detected case, plus a count of additional retailers involved.
Severity. The worst severity among this product’s cases in the current view.
Detected. How long ago the first violation was detected.
Actions. Open the case details or send a notification to the retailer.

The Product, Case scope, Severity, and Detected columns are sortable. Click a column header to sort ascending. Click again for descending. Click a third time to clear the sort. Severity and Case scope default to descending on first click, so the worst or most cases come first. Detected defaults to descending, newest first. Product defaults to ascending.

Retailers view

Click the Retailers in violation card to switch to a retailer-grouped table. Each row shows:

Retailer. The retailer’s name with an expand/collapse toggle.
Violating products (open). How many of your products this retailer is currently violating, and the total open violation count.
Worst severity. The most severe violation this retailer currently has.
Oldest violation. How long ago their earliest active violation was first detected.

Click any retailer row to expand it and preview up to five of their violating products inline. If the retailer has more violations than the five previewed, a View all link appears. It opens the full, retailer-specific list.

Violation details

Click any product row, or choose Review from the Actions menu, to open the violation details dialog.

The sidebar lists all violation cases for this product. Active cases, Open and Notified, are separated from resolved cases. Each entry shows the retailer name, the case status, and the observed price. Click a case to inspect it in the right panel.

Right panel: Review

The review panel shows:

Pricing comparison. The retailer’s observed price next to your MAP price, with the exact amount and percentage by which the price falls below MAP.
Severity alert. A colour-coded banner with the deviation percentage and a Notify retailer button, which reads Notify retailer again once the case is Notified. The button is hidden on Resolved cases. The banner is red for Severe, orange for Moderate, and amber for Minor.
Evidence. A link to view the offer on the retailer’s site and the date the evidence was captured, if available.
Violation status. Buttons to switch the case between Open, Notified, and Resolved. Click a different status to open the status-change form. A Resolved case also shows its resolution reason.
MAP Activity. A timeline of status changes and notes, newest first. A sent notification appears as the status change to Notified, not as a separate notification entry.
Add note. A free-text field to record context about this case. Notes appear in the activity timeline.

Updating case status

Click a status button to open an inline form:

Open → Notified. You can add a note, for example how the retailer was contacted. No note is required.
Open or Notified → Resolved. A resolution reason and a note are both required. The reason options are Price Corrected, Override Added, False Positive, or Other. If the latest observed price is still below MAP, Aperture shows a warning before you can proceed.
Resolved → Open or Notified, or Notified → Open. A note is required to explain why you reopen the case. The activity log records the transition.

Notifying a retailer

Choose Notify retailer from the review panel or from the Actions menu to open the notification composer.

Enter the recipient’s email address.
Edit the subject line if needed.
Choose an email tone: Professional, Assertive, or Friendly. Each tone produces a different pre-written template. If you switch tone after you edit the body, a prompt asks you to confirm before the template replaces your edits.
Edit the message body in the rich-text editor. The editor includes a price-comparison table pre-filled with the product name, observed price, MAP price, and deviation percentage.
Click Send.

The first notification moves an Open case to Notified and records the status change in the activity log. If you notify a case that is already Notified again, Aperture sends the email but leaves the status and activity log unchanged. You cannot notify a Resolved case.

Retailer-specific violations page

Expand a retailer’s row in the Retailers view and click View all to open a focused page that shows only that retailer’s violations. The page reuses the same filters as the main page, time range, severity, and search, and the same product columns, scoped to the selected retailer. The table there is a plain, paginated list. Column sorting and the summary cards are not available on this page.

When you view an individual offer, a banner further down the offer details, beneath the price snapshot and the MAP enforcement banner, relates the offer to your alert rules. It appears once a violation case exists for that retailer at a price below MAP. If an alert rule monitors this product and there is currently an unresolved MAP violation alert that covers this retailer, the banner shows how long ago that alert first fired. Otherwise, the banner prompts you to create an alert rule so you are notified automatically when prices drop below MAP. This also applies when a rule exists for the product but no alert is currently open for this retailer.