P3

 In Amazon’s internal support and issue-tracking systems, P3 (Priority 3) refers to non-critical bugs, system limitations, or operational concerns that have a limited impact on sellers, vendors, or customers. These issues can typically be worked around, and resolution may be scheduled as part of a future release or sprint.

Common examples of P3 issues:

• Cosmetic UI bugs in Seller or Vendor Central
• Incorrect labeling or minor display glitches
• Intermittent issues with non-essential reports or metrics
• Feature requests or usability improvements
• Documentation errors that don’t block workflow

Amazon’s approach to P3s:

• Logged and acknowledged by support or engineering
• Prioritized after P1 and P2 issues are resolved
• Typically resolved during routine maintenance cycles or product updates
• Tracked internally but not escalated unless business impact increases

Why P3 classification matters:

• Helps Amazon teams focus on urgent vs. non-urgent fixes
• Keeps track of backlogged improvements
• Provides visibility into minor issues that still affect seller/vendor experience
• Ensures resource allocation is efficient

💡 Example: A small formatting issue in the FBA Shipment Summary page that doesn’t affect data accuracy would be classified as a P3.

In short:
P3 (Priority 3) represents low-urgency issues or feature requests that have minimal business impact - addressed after higher priority problems and often queued for future resolution.