Enforcement
Templates
The words a notice is built from: placeholders, the allowed markup, immutable published versions, starter examples, and who may publish.
Last revised
A template is the text of a notice with placeholders where the facts go. MapProtector supplies the mechanism — the editor, the placeholders, the preview, the version history — and your team supplies the words. The product asserts nothing about a seller’s conduct; a template that does is your brand’s statement, reviewed against your own legal and compliance policy.
The library
Settings › Enforcement › Notice templates lists every template with its status and whether it is in use by a sequence. Open one to see its name and description (mutable without a new version), what is in force now, and its version history.
| Status | Meaning |
|---|---|
| No published words | Created, nothing published yet. It cannot be used by a sequence. |
| Published | A version is in force. Sequences may name it. |
| Archived | Retired. An archived template cannot start new work; a sent notice that points at one of its versions is unchanged. |
Writing a template
- Open the template and, in the designer, write the Subject, the Email body and the Plain-text body. Both bodies are authored, not derived — a plain-text notice should read as a letter, not as stripped HTML.
- Insert facts with Insert a variable. Each placeholder is replaced at preparation time with the value from the notice snapshot: the seller, the product, the observed price, the MAP, the gap, when it was observed, the case and evidence references, your brand and contact name, the SKU, the marketplace and the policy name.
- Use the preview. It renders the template with sample values exactly as a seller would receive it.
- Choose Save to keep a working copy, and Publish to make an immutable version. Publishing requires a fresh second factor.
Placeholders
| Placeholder | Value |
|---|---|
brand_name · contact_name | Your brand and the contact name on the sender identity. |
seller_name · seller_id | The storefront name at the time and the marketplace seller id. |
product_name · asin · sku · marketplace | The product as your catalog names it and the listing it was seen on. |
observed_price · map_price · gap_amount | The price seen, the floor it was measured against, and the difference — with currency. |
observed_at | The instant of the cited observation, in UTC. |
policy_name · case_reference · evidence_reference | The policy, the case and the sealed package the notice cites. |
An unknown placeholder fails publication rather than being dropped. Every interpolated value is escaped, so a storefront name containing markup cannot change your notice.
Markup
The email body accepts a small, closed set of tags — paragraphs, emphasis, lists, line breaks, links — and refuses everything else, including scripts, images, styles and forms. A link’s target must be an ordinary web address. Validation reports every problem at once.
Versions
- Publishing creates a version. A version is never edited; a change is a new version.
- A sent notice points at exactly one version, so “what did the template say when this went out” is always answerable.
- Placeholders used by each version are recorded, so a sequence can tell what a stage will need before it is drafted.
Starter templates
A new workspace carries example wording, labeled Example wording. The examples say in their own text that they are examples and claim no legal validity. Review them against your own policy before publishing anything derived from them.
Who may do what
Creating, renaming, duplicating, publishing and archiving templates need the Brand Admin role — the words a seller reads are the tenant’s own statement. Compliance Managers and Analysts can read the library and the preview. Template management is available on plans that include enforcement configuration; on Starter the library is a preview of what a seller would receive, and nothing can be sent.