~20% of First-Time Submissions Get Rejected. Here's What AWS Is Actually Scoring You On.
- AWS reviews every Marketplace listing against 5 core criteria before approval
- ~20% of first-time submissions get rejected — most for avoidable reasons
- Review takes 3–10 business days; well-prepared listings pass on the first try
- This guide covers exactly what reviewers evaluate and how to pass each check
Roughly one in five first-time AWS Marketplace submissions gets rejected. Not because the product is bad. Not because the company is unqualified. Because the listing itself fails to meet the specific criteria that AWS's review team evaluates before approving any new product.
AWS has reviewed thousands of listings across 42,240 products in over 70 categories. Their review team has a well-defined rubric, and they apply it consistently. The problem is that most ISVs don't know what's on that rubric until they receive a rejection email that says "your listing requires changes" with a list of issues that could have been addressed before submission.
If you're seeing a rejection notice and wondering what went wrong, or if you're preparing a first-time submission and want to pass on the first try, this guide breaks down exactly what AWS evaluates, why each criterion matters, and where most teams get stuck. We're inverting the perspective here. Instead of telling you what to do as a seller, we're showing you what AWS is looking for as a reviewer.
The most common mistake ISVs make when approaching the listing review is treating it like a formality. It's not. AWS uses this review to protect buyer trust across the entire Marketplace. They take it seriously, and you should too.
The Review Process Explained
Here's what actually happens after you hit "Submit" in the AWS Marketplace Management Portal (AMMP). Your listing enters a two-phase evaluation pipeline.
Phase 1: Automated validation. AWS runs automated checks against your listing metadata, pricing configuration, and technical integration endpoints. This catches structural issues — missing fields, invalid URLs, malformed metering dimension definitions. If your listing fails automated checks, you'll get feedback within 24–48 hours.
Phase 2: Human review. A member of the AWS Marketplace team manually reviews your listing content, screenshots, pricing model alignment, and — for SaaS products — your technical integration behavior. This is where most rejections happen. The human reviewer is evaluating whether your listing meets the bar for buyer readiness.
Timeline: expect 3 to 10 business days for the full review cycle. If you're rejected and resubmit, the clock resets. ISVs who invest 400 to 700 hours in a DIY listing process often lose additional weeks to revision cycles that could have been avoided with proper preparation. Understanding the criteria before you submit is the single highest-leverage thing you can do to compress your time-to-live.
ISVs that pass AWS Marketplace review on the first try share one trait: they treat the listing like a product launch, not a form submission.
The 5 Criteria AWS Evaluates
The first thing AWS checks is whether your pricing model configuration matches your delivery method and intended sales motion. This sounds straightforward, but it's where a surprising number of listings stumble.
AWS Marketplace supports several pricing models for SaaS products: SaaS Subscriptions (flat recurring fees), SaaS Contracts (committed-spend agreements), and usage-based pricing via the Metering API. Each model has different implications for private offers, MACC burn-down eligibility, and buyer procurement workflows.
Choosing SaaS Subscriptions when your enterprise sales motion requires private offer flexibility. SaaS Subscriptions don't support the negotiation mechanics that enterprise buyers expect — custom pricing, installment schedules, or committed-spend agreements. If your average deal size is above $25K ARR and involves procurement teams, SaaS Contracts is almost certainly the right starting point.
The second common mistake: defining a flat per-seat model on Marketplace when your product actually charges by usage (API calls, data volume, compute hours). This pricing mismatch creates confusion for buyers who see one billing model on your website and a different one on Marketplace.
Step 3 is where most teams get stuck. Here's the fix: Before you configure anything in AMMP, map your existing direct-sales pricing model to the Marketplace equivalent. Consult our step-by-step listing guide for a pricing model decision matrix. If your motion involves enterprise deals with negotiated terms, start with SaaS Contracts and enable private offers from day one.
AWS reviewers read your product description carefully. They're not skimming. They evaluate it against specific quality criteria: completeness, accuracy, specificity, and buyer-readiness.
Here's what the reviewer is looking for:
- Clear value proposition: What does the product do, and what business outcome does it deliver? Vague language like "comprehensive platform" or "enterprise-grade solution" will get flagged. AWS wants you to be specific.
- Defined use cases: Who is this product for, and what problems does it solve? If your description reads like it could apply to any software product, that's a problem.
- Integration details: How does the product work within an AWS environment? Buyers on Marketplace are AWS customers — they want to know about VPC deployment, IAM integration, CloudWatch compatibility, and data residency.
- Proof points: Customer counts, deployment metrics, compliance certifications, analyst recognition. AWS Marketplace buyers are evaluating risk, and evidence reduces perceived risk.
Listing completeness score matters more than most ISVs realize. AWS uses it as a ranking signal in Marketplace search. Every empty optional field is a missed opportunity — both for passing review and for organic discovery. The data supports this: of the 42,240 products on AWS Marketplace, 89% are listed, but only 22% generate more than 20% of the seller's total revenue. The difference between listings that perform and listings that sit idle often comes down to description quality and completeness.
The most common mistake ISVs make when writing descriptions is recycling their website copy. Marketplace descriptions need to be written for the Marketplace context — a buyer who's comparing your listing against competitors in the same category. Avoid the common listing mistakes we've documented separately.
For SaaS listings, AWS doesn't just review your content — they test your technical integration. This is where engineering teams often discover gaps they didn't anticipate.
AWS validates three core integration flows in their sandbox environment:
1. ResolveCustomer flow. When a buyer subscribes through Marketplace, AWS sends a registration token to your Fulfillment URL. Your application must call the ResolveCustomer API with that token to identify the customer and activate their subscription. If this flow fails — due to missing error handling, incorrect endpoint configuration, or timeout issues — the subscription doesn't complete, and your listing gets rejected.
2. Metering API integration. For usage-based listings, your application must call BatchMeterUsage or MeterUsage to report consumption. AWS checks that your dimension definitions match what's configured in AMMP, that your reporting cadence is correct, and that your integration handles edge cases. For a deep dive on getting this right, see our metering integration guide.
3. Subscription lifecycle handling. AWS tests what happens when a subscription is created, renewed, cancelled, and expired. Your application needs to handle each state transition gracefully — provisioning access on subscribe, revoking on cancel, sending appropriate notifications throughout.
Common failures that trigger rejection: missing retry logic on API calls (the Metering API rejects reports older than 6 hours), incorrect dimension definitions that don't match AMMP configuration, and Fulfillment URLs that return 500 errors under load.
Most teams build the happy path and skip edge-case handling. AWS tests the edge cases. Build your integration defensively, add alerting on every failure path, and test exhaustively in the AMMP sandbox before submitting for review.
The Foundational Technical Review is not technically required to get a listing approved. But without FTR completion, you cannot qualify for the ISV Accelerate program. And without ISV Accelerate, you don't get co-sell access, reduced transaction fees, or visibility to AWS's field sales organization.
What FTR covers:
- Security: IAM least-privilege policies, encryption at rest and in transit, secrets management practices
- Logging and monitoring: CloudTrail integration, centralized logging, alerting on security-relevant events
- Disaster recovery: Documented DR runbooks, RPO/RTO targets, tested failover procedures
- Well-Architected alignment: Evidence that your architecture follows AWS Well-Architected Framework principles
FTR takes 2 to 4 weeks to complete. AWS deprioritizes non-FTR partners for co-sell engagement, and enterprise buyers increasingly ask whether ISVs have completed the review as part of their security due diligence. If you're planning a Marketplace launch, start FTR preparation at least 8 weeks before your target go-live date.
This criterion surprises most ISVs, but AWS now uses image quality as a ranking signal in Marketplace search results. Your screenshots aren't just decoration — they directly affect your listing's discoverability and conversion rate.
AWS requirements for visual assets:
- Minimum resolution of 1600 x 900 pixels for screenshots
- Images must show actual product UI, not mockups or placeholder graphics
- No watermarks, stock photos, or marketing collateral masquerading as product screenshots
- Logo must meet format and dimension specifications
- At least three screenshots recommended (AWS rewards completeness)
The reviewer checks that your screenshots accurately represent the product described in your listing. Mismatches between description and visuals — a common issue when marketing teams prepare assets before the product UI is finalized — will trigger a revision request.
The fix: Capture screenshots from your production environment showing real data (anonymized if necessary). Include your most differentiated UI surfaces — the views that make a buyer think "this solves my problem" rather than generic dashboards.
The First-Pass Checklist
Before you hit submit, verify every item on this list. Each row maps to a specific review criterion that can trigger a rejection.
| Area | Check | Why It Matters |
|---|---|---|
| Pricing | Model matches sales motion (Contracts for enterprise, Subscriptions for self-serve) | Mismatched models get rejected and are hard to change post-launch |
| Pricing | Metering dimensions defined and tested in sandbox | Dimension errors are permanent until new listing version |
| Description | Short description under 200 chars, specific, no buzzwords | Reviewer flags vague or keyword-stuffed descriptions |
| Description | Long description follows problem → solution → capabilities → proof structure | Completeness score affects search ranking |
| Description | All optional fields populated (highlights, categories, support info) | Empty fields lower your completeness score |
| Integration | ResolveCustomer flow tested end-to-end in sandbox | Broken subscriber activation is an automatic rejection |
| Integration | MeterUsage/BatchMeterUsage calls include retry logic | Reports older than 6 hours are permanently rejected |
| Integration | Subscription lifecycle (create, renew, cancel, expire) handled | AWS tests all state transitions |
| Visuals | 3+ screenshots at 1600x900+, real product UI | Image quality is a search ranking signal |
| Visuals | Logo meets format and dimension specs | Invalid logos trigger revision requests |
| FTR | FTR checklist downloaded and ownership assigned | Required for ISV Accelerate and co-sell access |
| Categories | All 3 category slots used with relevant selections | More categories = broader discovery |
If every row checks out, your listing is positioned to pass on the first try. If even one area is incomplete, you risk adding 3 to 10 business days of delay for each revision cycle.
- Product description includes specific use cases and target audience
- At least 3 pricing dimensions defined with clear metering
- EULA or custom license agreement prepared
- Product logo meets 120x120px minimum at high resolution
- FTR self-assessment completed for AMI/container products
- Support contact and documentation URLs active and accessible
- ResolveCustomer flow tested end-to-end in AMMP sandbox
- Subscription lifecycle (create, renew, cancel, expire) handled
- All 3 category slots populated with relevant selections
- Screenshots captured from production UI at 1600x900+ resolution
If You're Submitting for the First Time, Get It Right the First Time
If you're preparing your first AWS Marketplace submission and want to pass review on the first try, or if you've already been rejected and need to fix the resubmission, this is the leverage point that matters most: understanding what AWS is scoring you on before they score you.
The data tells a clear story. DIY submissions face a ~20% rejection rate. The full listing process consumes 400 to 700 hours of engineering and GTM effort. And even after getting listed, most ISVs underperform — 89% of products are listed, but only 22% generate meaningful revenue through the channel.
Automatum's platform handles listing submission, metering integration, pricing configuration, and FTR preparation with a near-zero rejection rate. Not because we've found a shortcut, but because we've internalized exactly what AWS looks for across every criterion in the review rubric — and we build it right before you submit.
Instead of spending months navigating rejection cycles, our clients go from listing preparation to live in weeks. The difference isn't magic. It's process rigor applied to a review process that rewards precision.
See how Automatum accelerates your Marketplace launch, or book a listing review with our team to get a pre-submission audit of your current listing.
Automatum handles listing submission, metering, and FTR preparation across AWS, Azure, and GCP — with a near-zero rejection rate.
Book a Listing Review →Frequently Asked Questions
Common questions about the AWS Marketplace listing review process.
How long does AWS Marketplace listing review take?
The listing review itself takes 3 to 10 business days. If you need to complete the Foundational Technical Review (FTR) for ISV Accelerate eligibility, that adds an additional 2 to 4 weeks. Plan for at least 8 weeks total if FTR is part of your launch timeline.
What causes most AWS Marketplace listing rejections?
The three most common rejection triggers are incomplete product descriptions that lack specificity and proof points, mismatched pricing models that don't align with the seller's actual sales motion, and missing technical integration requirements such as broken ResolveCustomer flows or metering API errors.
Is the Foundational Technical Review (FTR) required for listing?
Not technically required to get your listing approved, but it is required for ISV Accelerate enrollment and co-sell access. AWS deprioritizes non-FTR partners for co-sell engagement, and enterprise buyers increasingly ask for FTR completion as part of their vendor security due diligence. Treat it as effectively mandatory for any serious Marketplace revenue strategy.
Can I update my listing after it's approved?
Yes, but with important caveats. Content updates like descriptions, screenshots, and support information can be submitted as listing updates and go through a lighter review. However, changes to metering dimensions or pricing model structure require creating a new listing version, which resets the review timeline and can disrupt existing subscribers who need to be migrated to the new version.
Keep building your marketplace motion
AWS Marketplace guides to help you pass review and launch faster.
