Policies
Exceptions
An exception exempts a seller, a product or a scope from judgment, or lets it be measured but never enforced. How to create one, the two effects, and what an exception can never do.
Last revised
An exception is an effective-dated instruction about what happens next for a scope: either do not judge these observations against the policy, or judge and record them but never make them eligible for enforcement. It is the tool for a distributor under negotiation, a product under legal review, a storefront of your own, or any relationship you want measured rather than acted on.
The two effects
| Effect | What the evaluation does | What the queue does |
|---|---|---|
| Exempt from policy | Returns Not applicable with the exception as the reason. The seller is not judged. This is deliberately not Compliant: an offer nobody assessed does not raise your compliance rate. | Nothing reaches the review queue. |
| Monitor only — never enforce | Judges and records normally, including Below policy. | A below-policy observation is still recorded and visible; it never becomes a violation candidate and can never be cited by a notice. |
Creating an exception
- Open Configuration › Exceptions and choose New policy exception.
- Choose the Brand and what the exception covers: one seller; one seller on one product; one product, every seller; a product group, every seller; or the whole brand, every seller. For a seller-scoped exception, pick a seller already observed or enter a seller id directly.
- Choose the Marketplace (or every channel) and the Condition.
- Under Effect and period, choose Exempt from policy or Monitor only — never enforce, set From and optionally Until (read as UTC), and record the Reason.
- Choose Create exception. It is active from its start instant. Creating and revoking exceptions needs the Compliance Manager role or above.
Several exceptions at once
Any number of exceptions may apply to one observation. They combine in the safe direction: if any live exception exempts the observation, it is exempt. There is no precedence to configure and no tie to resolve, which is why exceptions and promotions are two mechanisms rather than one.
What an exception can never do
- It cannot erase an observation, an evaluation or an evidence package. It changes what happens next, never what was seen.
- It cannot close a period. A Monitor only exception created while a period is open stops future enforcement; the period closes on cure as before.
- It does not classify the seller. A seller with an exception is still Unknown, Authorized or whatever your team has set on the Sellers page.
Revoking
An exception is revoked from its row. From the revocation, observations are judged normally again; observations evaluated while it was active keep their Not applicable outcome. A revoked exception stays in the list for the record.