You referred an opportunity to AWS through ACE (APN Customer Engagements) in AWS Partner Central, and it came back as Action Required. That means AWS reviewed it and wants something changed before it approves it. Rejected means AWS disqualified it. The review status applies only to opportunities you refer to AWS, not to referrals AWS sends you. This guide covers what each status means, where to read AWS's feedback, the usual causes, what you can still edit, and how to resubmit. If the API refused your request outright rather than AWS asking for changes, see ACE validation errors explained.
The review statuses
AWS records the review in LifeCycle.ReviewStatus. In the AWS catalog you cannot set it yourself. These are the values the Partner Central Selling API returns, as of November 2026:
| Status | What it means | What you can edit |
|---|---|---|
Pending Submission | You created the opportunity but have not submitted it. | Most fields |
Submitted | You submitted it and AWS has not started the review. | Nothing |
In review | AWS is validating it. | Nothing |
Action Required | AWS found issues you need to address. | Only the fields AWS opens |
Approved | AWS validated it and added it to the AWS seller's pipeline. | Most fields, with some locked |
Rejected | AWS disqualified it. | Nothing |
The API value is In review, with a lower-case r, although AWS's own prose also writes "In Review" and "In-Review". Match the exact value in code and in CRM picklists.
After you fix an Action Required opportunity, it goes back into validation. The cycle repeats until AWS sets it to Approved or Rejected. AWS's CRM integration guide says validation can take up to five business days. When AWS needs more information, it emails the alliance lead and the opportunity's contacts.
What changed in June 2026
On 16 June 2026 AWS launched agentic co-selling in Partner Central. Every submitted opportunity now gets an Opportunity Quality Score out of 100 and a co-sell motion: AWS Field-engaged, Agent-engaged or Partner-led. AWS rescores the opportunity when you edit the fields it scores. In the Agent-engaged and Partner-led motions, AWS accepts your updates straight away. In AWS Field-engaged, updates pass through an AWS review step. As of November 2026, Action Required and Rejected are still review status values in the API and the console.
Where to read what AWS wants
In Partner Central:
- Open Sell, then Opportunities, and filter on Action required.
- Open the opportunity by its ID.
- Read the Opportunity Quality score, the recommendation and AWS's recommended actions. AWS's Partner Central agent can help you make the changes.
Through the API:
GetOpportunityreturnsLifeCycle.ReviewComments, AWS's detailed feedback on what to provide or clarify. It also returnsLifeCycle.ReviewStatusReason, a code for the decision, set when the status is Action Required or Rejected. AWS does not publish the list of reason codes, so treat the comments as the instruction.GetAwsOpportunitySummaryreturnsInsights.OpportunityQuality(aScoreand aTrend, empty until AWS scores the opportunity),Insights.NextBestActionsandCosellMotion.- AWS recommends subscribing to the
Opportunity Updatedevent in Amazon EventBridge and callingGetOpportunitywhen it arrives. That is how you learn the status changed.
Common reasons and how to fix them
AWS says its validation checks an opportunity against criteria for deal size, solution alignment and customer engagement status. The review comments name the specific problem. These are the causes AWS's documentation points to.
The customer business problem is vague
Project.CustomerBusinessProblem accepts 20 to 2,000 characters, but length is not what AWS judges. AWS asks for this customer's specific problem, what is forcing them to act now, and the outcome they expect. It is the main input to the Opportunity Quality Score. AWS advises against three habits:
- text that would fit any customer, or the same paragraph reused across opportunities;
- describing your product instead of the customer's situation;
- letting a CRM or integration fill the field without anyone reading it.
The field is editable in Action Required. Write it carefully now, because AWS locks it once the opportunity is approved.
Customer details are missing or wrong
AWS uses the customer's website to match the customer in its own CRM. Customer.Account.WebsiteUrl is required except for national security opportunities. In the Partner Central form, every customer field is required except the DUNS number, and AWS says it needs the website and postal code to align the opportunity with the right AWS teams. If you give a DUNS number, Duns must be nine digits. For a US customer, StateOrRegion takes a state name from AWS's list, such as California.
The address fields and the website are editable in Action Required. The company name and the industry are not, so check both before you submit.
The opportunity duplicates another
AWS asks partners not to split one engagement into several opportunities. The AWS seller reads near-identical records for the same customer as one opportunity, and the extra records crowd out the one that matters. Keep one opportunity per customer engagement, put the detail into that one, and check your CRM for an existing record before you create another.
The use case or industry is wrong, or left as Other
AWS routes opportunities by use case and industry. It asks for the most accurate value rather than Other. AWS Training Partners should choose Training as the use case. If you do choose the industry Other, fill in OtherIndustry. Neither field is editable in Action Required, so get them right before submission.
The expected spend does not hold up
Project.ExpectedCustomerSpend is what the customer is expected to spend on AWS each month because of this opportunity, sent with Frequency Monthly and TargetCompany AWS. Deal size is one of the things AWS validates. Partner Central's deal sizing can forecast monthly recurring revenue, and you can attach an AWS Pricing Calculator estimate link. The amount and the currency are editable in Action Required.
No solution is attached
AWS requires a solution on the opportunity before it starts the engagement: one to ten Partner Solutions, AWS Marketplace solutions or AWS Marketplace products, each in Public or Limited status. Since 1 July 2026, moving an opportunity to Committed or Launched also requires one of these. Attach it in the console's AWS Marketplace products and solutions section, or with AssociateOpportunity. The solution is also one of the components of the Opportunity Quality Score.
The target close date is in the past
LifeCycle.TargetCloseDate is when AWS expects significant billing to start, written as YYYY-MM-DD. It must not be in the past. It is editable in Action Required.
The stage is wrong for a submission
AWS takes submissions from Qualified onwards. A Prospect must mature to Qualified first. Do not submit an opportunity that is already lost, launched or won.
What you can change, by status
Action Required
AWS opens only these fields:
- the customer address:
Customer.Account.Address.City,CountryCode,PostalCode,StateOrRegionandStreetAddress; Customer.Account.WebsiteUrl;LifeCycle.TargetCloseDate;- the amount and currency in
Project.ExpectedCustomerSpend(AWS's developer guide also lists frequency, target company and the estimate link); Project.CustomerBusinessProblem;PartnerOpportunityIdentifier.
Everything else, including the title, stage, industry and next steps, cannot change in this status.
Approved
You can keep updating the opportunity, but AWS locks these fields:
Customer.Account.Address.CountryCodeandPostalCode;Customer.Account.Industry;Customer.Account.WebsiteUrl;Project.CustomerBusinessProblem;PartnerOpportunityIdentifier;Project.Title.
AWS notes that other business rules can restrict more fields. In CoSell's own syncs, AWS has also refused a company name change on an approved opportunity.
Launched
AWS publishes no list for launched opportunities. In CoSell's syncs, AWS has refused changes to the stage and to the customer's city after launch, with messages such as lifeCycle.stage is not editable post launch (as of November 2026).
Submitted, In review and Rejected
Nothing can change. A rejected opportunity stays read-only.
Pending Submission
You can update the opportunity, but AWS does not act on it until you submit. CoSell has seen AWS refuse a stage change while an opportunity is still Pending Submission, so set the right stage when you create it.
How to resubmit
In Partner Central, open the opportunity, choose Edit, make the changes, choose Save, then choose Submit.
Through the API:
- Call
GetOpportunityto get the current record and itsLastModifiedDate. - Change only fields on the Action Required list.
- Send the whole record with
UpdateOpportunity, includingLastModifiedDate. AWS treats any field you leave out as null, so a partial payload can erase values. IfLastModifiedDateno longer matches AWS's copy, AWS returnsConflictException: fetch the record again and reapply your change. - AWS documents that the opportunity then re-enters validation. Watch for the next
Opportunity Updatedevent and read the status again.
If AWS asks for several changes, make them all in one pass. Each round of validation takes time.
Avoid it next time: a pre-submission checklist
- The business problem is about this customer: what is wrong today, why they must act now, the outcome they expect and how they will decide. It is not a product description.
- The website, full address and postal code are filled in, and a US customer has a state.
- Industry and use case are the closest real values, not Other.
- At least one solution or AWS Marketplace product is attached, in Public or Limited status.
- The expected monthly AWS spend is realistic, and an AWS Pricing Calculator estimate backs it where you have one.
- The target close date is in the future.
- The stage is Qualified or later, and the deal is not lost, launched or won.
- If you want AWS to co-sell,
PrimaryNeedsFromAwsnames a specific need. AWS's scoring does not credit Deal Support on its own. - Next steps name an action, a date, your owner and a contact at the customer.
- No other open opportunity covers the same engagement.
- The title, country, postal code, industry, website and business problem are correct, because AWS locks them after approval.
- Someone has read what your CRM integration is about to send.
Where CoSell fits
CoSell connects Salesforce, HubSpot, Microsoft Dynamics 365, Zoho CRM or LeadSquared, or CoSell's built-in CRM, to Partner Central through the Selling API. It checks each deal against AWS's rules inside your CRM workflow before submission and lists what is missing; AWS's own Partner Central agent can also check drafts in the console. After submission, CoSell shows AWS's review status and comments on the deal, keeps an error inbox with retry, and does not send changes to fields AWS has locked. It runs hosted by HabileLabs or in your own AWS account, from USD 10 a month on AWS Marketplace; the offer is currently for AWS accounts in India. See features and pricing.
Sources
- Selling API types and actions: LifeCycle (opens in a new tab), LifeCycleSummary (opens in a new tab), Account (opens in a new tab), Project (opens in a new tab), UpdateOpportunity (opens in a new tab) and GetAwsOpportunitySummary (opens in a new tab) (checked 13 November 2026)
- Selling API developer guide: working with opportunities (opens in a new tab), opportunity updates (opens in a new tab), associating opportunities (opens in a new tab) and optimistic locking and data sync (opens in a new tab) (checked 13 November 2026)
- Partner Central sales guide: AWS opportunity review process (opens in a new tab), creating an opportunity (opens in a new tab), agentic co-sell engagement (opens in a new tab) and agents for opportunity management (opens in a new tab) (checked 13 November 2026)
- Working with referrals, leads, and opportunities (opens in a new tab), Partner Central CRM guide (checked 13 November 2026)
- AWS Partner Central now supports AWS Marketplace listings for co-selling (opens in a new tab), AWS What's New, 1 July 2026 (checked 13 November 2026)