Harpy Glossary

P1 (Priority 1)

Amazon & D2C glossary · Harpy Media

P1 (Priority 1) is the highest severity classification Amazon applies to incidents, technical failures, and operational escalations: a business-critical problem demanding immediate attention because it disrupts customers, sellers, orders, payments, or core platform functionality.

What is P1?

It comes from support and engineering culture rather than commerce — the tiered severity system that decides how fast a problem is looked at. Understanding it is useful for sellers and vendors for two reasons: it explains why the platform responds to some issues within hours and others within weeks, and it clarifies what kind of problem is worth escalating and what kind simply has to be managed.

What qualifies as P1 — and what does not

A P1 is reserved for issues with broad impact or severe operational risk: platform or site outages, Seller Central or Vendor Central access failures at scale, widespread payment disruption, checkout failures, and anything that blocks work across many accounts during a critical period. When an issue is classified P1, resources are reallocated immediately, leadership visibility rises, and resolution targets tighten.

The instructive part is the boundary. A single suppressed ASIN, one stranded shipment, or a delayed case reply can be serious for one business — and usually is not a P1, because the severity model measures the blast radius, not the pain. Sellers who understand the distinction use escalation energy where it can actually work instead of spending it on issues that will be queued regardless.

How to escalate well when it matters

When something genuinely breaks at scale, precise reporting is the lever: what stopped working, when it started, how many orders or units are affected, what revenue is at risk, and what evidence you can attach. A case written like an incident report travels further than frustration, because it gives the receiving team the facts they need to classify and route it.

For problems that are real but not P1-class, the practical strategy shifts from escalation to mitigation: keep selling through the disruption where possible, document what happened, and follow the normal channel. And for the account-threatening events that sit between the two — suspensions, lost privileges — the escalation belongs with the formal recovery process (plan of action, account health appeals) rather than with severity language.

In practice

A Vendor Central outage blocks invoice submission during end-of-month reconciliation. Because the failure affects financial operations, blocks workflow for many suppliers, and lands in a critical reporting window, the platform treats it as P1-class: triage begins immediately, and the disruption is resolved with urgency proportional to the number of businesses it is holding up. The severity label is what bought the speed.

⚠️ Watch out. A seller labels every urgent-seeming problem as a P1: one listing suppressed, a case unanswered for two days, a report rendering oddly. Each case is written with escalating urgency, each gets the same standard queue, and the seller concludes the platform does not care. The problems were real; the classification was not — and treating routine issues as catastrophes uses up the attention that a genuine platform-level failure would need.

💡 Harpy tip. Describe the blast radius, not the frustration. When something breaks, quantify it: orders affected, revenue at risk, time stopped, other sellers seeing the same thing. Then match the channel to the severity — incident-style reporting for platform failures, formal recovery processes for account-level events, and ordinary case management for everything else.

How Harpy Media helps

Account-health and escalation routines sit inside our account management work: what to escalate, how to document it so it moves, and how to keep trading through the disruptions that no amount of urgency will speed up.

P1 FAQ

What does P1 mean on Amazon?

Priority 1 — the highest severity tier for incidents and escalations. It signals a business-critical problem with broad impact on customers, sellers, orders, payments, or platform functionality, and it drives the fastest possible response.

Should I escalate my seller issue as a P1?

Almost never. P1 classification is for platform-level failures with wide impact. Individual listing problems, slow case replies, and single-account issues have their own channels — and describing them accurately gets them handled better than overstating severity.

What should I include when reporting a serious issue?

The timeline (when it started), the scope (orders, units, or revenue affected), the evidence (screenshots, IDs, affected listings), what you have already tried, and the business impact. Incident-style reporting is what gets an issue classified correctly.

Want these numbers watched for you, every week?

Book Free Consultation