Enforcement
Prepare a notice
Preparing a notice from a case: what has to be in place first, what Prepare notice does, and the blockers the notice page shows before anything can be approved.
Last revised
A notice starts on a case. Preparing one starts the brand’s default sequence for the open breach period and drafts its next stage from the published template — rendered with the seller, the product, the prices, the policy and the sealed package — and puts it in the Enforcement inbox for a Brand Admin. Preparing sends nothing.
Before you prepare
| Requirement | Where |
|---|---|
| The plan includes enforcement sending | Growth and above. On Starter the workflow is a preview and nothing can be sent. |
| A verified sender identity | Settings › Enforcement › Sender identity: a display name, a From address on your own domain, a reply-to, verified through the mail provider. |
| A published template and a published default sequence | Settings › Enforcement. |
| A confirmed candidate with an open breach period | The case. |
| A sealed evidence package for the period | Evidence. Only a sealed package can carry a notice. |
| A seller contact | A recorded email address for the seller. Contacts are never inferred from a storefront or a listing: your team records them on the seller’s page under Sellers › the seller › Contacts (Compliance Manager and above), with where the address came from. See Seller contacts. |
Preparing
- Open the case from Compliance › Cases. Under Enforcement, the line Notices go to names the contact a notice would be addressed to — the nominated primary, or the oldest usable email — or says plainly that none is on file. Change it from Manage contacts before preparing.
- Choose Prepare notice (Compliance Manager and above). The run starts and the stage is drafted; you land on the draft.
- Read the rendered document, the facts it was built from, the eligibility section, and the Recipient panel: the contact’s name, company, where the address came from, and whether it can still be written to.
- Choose Submit for review. The confirmation repeats who the notice is addressed to before you confirm. The draft moves to awaiting approval; nothing is sent.
Canceling a notice
A notice can be canceled while it is a draft, awaiting approval, approved, or queued — every state in which nothing has been handed to the mail provider. Cancel this notice on the notice page (Compliance Manager and above) asks for a reason, records who stopped it and when, and lapses any approval it carried. The draft, its text and its history stay readable; nothing is deleted, and a corrected notice starts from a fresh draft.
The eligibility gate
Before a notice can be approved or sent, every blocker is evaluated and the whole list is shown — a notice blocked by three things is not unblocked by fixing one. The blockers are grouped in the order a person would look, with the ones you can fix first.
| Group | Blockers |
|---|---|
| The account | Workspace not active · plan does not include enforcement. |
| The workflow | Candidate not confirmed · no case · breach period not active. |
| The measurement | No qualifying observation · observation stale · source coverage insufficient. |
| The seller | Seller identity missing · no seller contact · contact undeliverable. |
| Policy | No current policy · an active exception applies. |
| Evidence | No evidence · evidence not sealed · evidence integrity invalid. |
| The policy-change interlock | Policy changed · no observation under the current policy · no evidence under the current policy · renewed approval required. |
| The sender | Sender not configured · sender not verified. |
| Holds and sequencing | A hold is in force · the sequence is paused · the stage’s wait has not elapsed. |
The snapshot
When a notice is prepared, the rendered document — subject, both bodies, recipient, sender, the cited facts — is frozen as a snapshot and hashed. An approval is a signature over that hash. If anything the notice was built from changes afterwards, the approval lapses; see Approval.
Holds
A hold stops every notice in its scope — one case, one seller, one product, or the whole workspace — including ones not yet composed, for a reason your team records: a dispute in progress, a data-quality doubt, a legal review. A hold is not a cancellation: when it is lifted, the workflow resumes where it stopped.
- Place a hold on a case, its seller or its product from the case page under Enforcement (Compliance Manager and above). An Analyst may place a data-quality hold there — the product, ASIN or MAP mapping looks wrong — with a note saying what, and may not lift it.
- Place a workspace-wide hold, and release any hold, from Compliance › Enforcement › Paused, where every hold in force is listed with who placed it and why.
- The case page lists the holds stopping that case. A notice blocked by a hold goes back to ready for review rather than being canceled, because a hold is usually temporary.
No second factor is asked for when placing or lifting a hold: stopping enforcement must never be harder than starting it.