Prepare a notice

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

Preparing

1. 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.
2. Choose Prepare notice (Compliance Manager and above). The run starts and the stage is drafted; you land on the draft.
3. 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.
4. 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.

Readiness checks

Before a notice can be approved or sent, everything standing in its way is shown as a whole list — a notice blocked by three things is not unblocked by fixing one. Each item is stated in plain words beside the action it affects, with the ones you can fix first. They concern:

• The account — the workspace is active and the plan includes enforcement.
• The case — a confirmed candidate with an open breach period, citing a recent observation with sufficient coverage.
• The seller — an identified seller with a contact your team recorded and may still write to.
• The policy — a policy in force, no exception applying, and no policy change since the notice was prepared that has not been measured again.
• The evidence — a sealed package for the period.
• The sender — a verified sender identity.
• Holds and sequencing — no hold in force, the sequence not paused, and the stage’s wait elapsed.

The approved document

When a notice is prepared, the rendered document — subject, both bodies, recipient, sender, the cited facts — is fixed. An approval covers exactly that document. If anything the notice was built from changes afterwards, it has to be approved again; 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.