Third-Party Seller SLA Breach Remediation Notice
Draft a formal performance breach remediation email to a marketplace merchant.
Use this template when a third-party seller violates critical fulfillment or customer experience metrics on your retail marketplace. It delivers a structured, compliant cure notice with explicit remediation deadlines.
Role: Senior Marketplace Merchant Operations Specialist specializing in seller performance compliance and fulfillment standards.
Context
- Seller Account Name: {{seller_name}}
- Marketplace Platform: {{marketplace_platform}}
- Violated Metric: {{metric_breached}}
- Current Performance Level: {{current_performance_rate}}
- Required SLA Target: {{threshold_target}}
- Cure Period Deadline: {{cure_deadline}}
Task
Draft a formal, authoritative, and actionable performance breach email to an underperforming third-party marketplace seller, detailing their service level deficit, operational risks, and the mandatory steps required to avoid account suspension or listing suppression.
Method
- Analyze the delta between {{current_performance_rate}} and {{threshold_target}} for {{metric_breached}} on {{marketplace_platform}}.
- Draft an urgent, unambiguous email subject line incorporating the merchant account name and compliance status.
- Open with a clear statement acknowledging the merchant partnership while citing the exact policy and metric breached.
- Explain how this metric failure negatively impacts customer fulfillment, delivery reliability, and marketplace trust.
- Outline likely root causes (e.g., late dispatch, inventory sync lag, carrier scan delays) for the merchant to audit.
- Detail the mandatory requirements for submitting an operational Plan of Action (POA).
- Set an explicit deadline of {{cure_deadline}} for measurable metric improvement or POA submission.
- State the tiered enforcement actions (buy-box suppression, category gating, full account suspension) if compliance is not achieved.
Constraints
- MUST clearly state the numerical gap between current performance and standard threshold.
- MUST NOT use emotive, unprofessional, or accusatory language.
- MUST include the specific cure deadline date {{cure_deadline}} in both the body and summary.
- Keep the total email body between 250 and 400 words for operational clarity.
Output format
- Subject Line: [Action Required] Account SLA Breach Notice - {{seller_name}}
- Section 1: Performance Breach Summary (metric, current rate, required target)
- Section 2: Impact Assessment and Root Cause Guidance
- Section 3: Required Plan of Action (POA) & Verification Steps
- Section 4: Enforcement Timeline & Operational Support Contact
Self-review
- Did I clearly contrast the current rate against the SLA target without ambiguity?
- Is the tone firm and compliance-driven yet constructive for vendor retention?
- Are the specific cure dates and consequences explicitly articulated?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.