P2

 In Amazon’s internal operations and support systems, P2 (Priority 2) refers to significant problems that affect business performance or user experience, but allow for some short-term workarounds or reduced functionality while resolution is underway.

Typical P2 issues may include:

• Errors or bugs in Seller/Vendor Central tools that affect some (not all) users
• Delayed data syncing (e.g., sales reports, advertising dashboards)
• Product listings that are partially suppressed or incorrectly flagged
• Payment discrepancies not affecting large volumes
• Intermittent API or integration failures with limited impact

Amazon’s P2 response expectations:

• Investigation usually begins within a few business hours
• Assigned to engineering or support teams with SLA-based timelines
• Does not stop core business functions, but may degrade them
• Escalations may happen if issue persists or grows in severity

Why P2 classification matters:

• Allows Amazon and sellers/vendors to triage effectively
• Ensures the issue is prioritized, but not at the cost of P1 emergencies
• Helps maintain operational continuity while problems are addressed
• Used widely across Tech, Ops, Finance, and Retail teams

💡 Example: A temporary bug that prevents some sellers from editing their listings via flat file upload would be classified as a P2 - urgent, but not platform-breaking.

In short:
P2 (Priority 2) is a high-priority issue that impacts Amazon operations or sellers significantly - but not critically - and is addressed with urgency after P1-level problems.