Multi-product solutions FAQ
This FAQ addresses common questions about multi-product solutions, including solution listings and offer sets.
Topics
What's the difference between AWS Marketplace Management Portal and AWS Partner Central?
How do I use solution in the rest of AWS Partner Central co-selling?
Why is my solution stuck in "pending review" or "preparing" status?
What happens if my solution fails the Update Visibility request to go public?
What solution details can I modify when my solution is in public status?
How do I get consent from product owners to include their products in my solution listing?
Can I mix AWS Marketplace products with non-AWS Marketplace products?
What are the requirements for enabling Request private offer on my solution?
Can I include products from multiple sellers in my solution?
Can customers purchase individual products from my solution separately?
What is the difference between a product and a solution?
A product is any single software (SaaS, AMI, Container, AI Agent, ADX), service, or AWS Service. Partners can transact and deploy a product through AWS Marketplace or can sell and deploy it directly outside of AWS Marketplace. A solution is a collection of one or more products that addresses a specific customer problem and defines how partners go to market. When a solution includes two or more AWS Marketplace products, it can be taken public on AWS Marketplace as a multi-product solution. To sell a multi-product solution, create an offer set that groups multiple private offers from each constituting product. Then extend the offer set to your customer.
Do I need to be an AWS Partner to create solutions?
You need AWS Marketplace seller credentials to create solutions. Requesting private offers for customer engagement requires you to be an AWS Partner Network (APN) partner eligible for APN Customer Engagements (ACE). Basic solution creation requires you to access AWS Partner Central.
Note
Your partner solutions from legacy Partner Central migrate to AWS Partner Central as AWS Marketplace solutions. Active solutions start in a Limited state. In this state, you can add products and enrich your solution before you publish it on AWS Marketplace as a multi-product solution.
What's the difference between AWS Marketplace Management Portal and AWS Partner Central?
For more information about AWS Partner Central, see the AWS Partner Central console
How do I use solution in the rest of AWS Partner Central co-selling?
Solutions can be used throughout AWS Partner Central for Foundational Technical Review (FTR) validation, program applications, opportunities, and funding. Your solutions will be required in various features throughout the partner co-selling journey. To start receiving co-sell benefits, you must get your solution FTR validated. You need FTR validation before obtaining AWS Customer Engagement (ACE) eligibility, which is required to activate the Request Private Offer feature and receive leads from multi-product solution listings that you make public. Existing partners can migrate solutions from legacy Partner Central into the AWS Marketplace catalog in AWS Partner Central. Migrated active solutions start as Limited solutions and can be used in other AWS Partner Central features. For more information about AWS Partner Central, see the AWS Partner Central Documentation.
How do I track the status of my change requests?
After you submit a change request, you can view the status from the Requests tab of the Solutions page in the AWS Partner Central. The status could be any of the following:
Under review – Your request is being reviewed. Most requests are reviewed automatically in the system, though some require manual review by the AWS Marketplace team.
Succeeded – Your request is complete. Your solution has been updated as requested.
Action required – You need to update your request to fix an issue or answer a question. Choose the request to see the details, including any issues.
Failed – Something went wrong with the request. Create a new request for the change with the same data.
Why is my solution stuck in "pending review" or "preparing" status?
Your solution may be under review because it requires either automatic system validation or manual review by the AWS Marketplace operations team. Most requests are reviewed automatically. However, updates such as going public on AWS Marketplace require a manual review of the solution.
What happens if my solution fails the Update Visibility request to go public?
If your solution fails validation, the change request status shows as "Failed" in the Change history tab of the Solutions page. You need to create a new request for the change with the modified data to try again.
What solution details can I modify when my solution is in public status?
When your solution is in public status, you can edit some details but not others. This helps maintain quality and consistency for customers viewing your solution.
You can edit:
Details – You can update general details about your solution at any time.
Embedded media – You can add, remove, or change embedded media such as videos and images.
Use cases – You can edit your use cases. However, your solution must have at least one use case to remain public.
Visibility – You can modify the visibility settings for your solution.
You cannot edit:
Adding or removing product – You cannot modify product details while your solution is public. To edit product details, you need to change your solution status back to limited. After you make changes, your solution must go through the vetting process again before returning to public status.
Buyer engagement – You cannot remove individual items like Request private offer. However, you can replace the entire buyer engagement section if needed.
Can I include products I don't own in my solution?
Yes, you can include AWS Marketplace products owned by others by obtaining their Product ID and entering it in your solution (Option 2 in Add product). The product must be public and supported in solutions. You need to coordinate with the product owner to obtain the necessary ID. Keep in mind that this Product ID is on the seller side in AWS Partner Central, AWS Marketplace Management Portal, or AWS Marketplace Catalog API. It's not the Listing ID found in AWS Marketplace website URL.
How do I get consent from product owners to include their products in my solution listing?
Before making your solution public with products owned by others, you must obtain consent from product owners to showcase their products in your public solution listing. You also need to coordinate with them to obtain Product IDs and ensure they're ready to provide selling authorization for extending channel partner private offers.
Can I mix AWS Marketplace products with non-AWS Marketplace products?
Yes, you can include non-AWS Marketplace products in your solution using Option 3 during the product addition step. You need to manually enter the product type, description, and URL for each external or custom product. Non-AWS Marketplace products do not show up to customers on the public listing.
How does the "Deployed on AWS" badge work for my solution?
Your solution displays the "Deployed on AWS" badge when all products included in the solution are deployed on AWS. This badge helps buyers quickly identify solutions that run entirely on AWS infrastructure. In procurement and transaction workflow, "Deployed on AWS" is tracked at individual product and offer level. The display on the solution listing represents the constituent products being marketed together but not necessarily the same set of products being offered to the customer for procurement.
What are the requirements for enabling Request private offer on my solution?
All public solution listings require Request private offer to be enabled, allowing buyers with unique or enterprise use cases to request a private offer directly from the solution detail page. To enable this option, you must be an AWS Partner Network (APN) partner eligible for APN Customer Engagements (ACE). After AWS qualifies these requests, they become AWS-originated opportunities in ACE tooling.
What is APN Customer Engagements (ACE)?
APN Customer Engagements (ACE) is an AWS Partner Network program that enables qualified partners to receive and manage customer opportunity requests. When buyers request private offers through your solution listing, these requests become AWS-originated opportunities in ACE tooling for eligible APN partners.
How do I choose the right use cases for my solution?
Search the predefined use cases using keywords relevant to your solution's purpose. Choose up to three that best match how your solution addresses specific customer needs. For each use case, provide a description (up to 500 characters) that explains how your solution solves that particular challenge.
What is the logo requirement?
You can upload either a solution-specific logo or your company logo. The logo must meet the following requirements. If you don't have a logo that meets these requirements, you can use a placeholder to submit the request until you're ready.
PNG or JPG format
5 MB maximum file size
120 to 1080 pixels in width and height
Transparent or white background (preferred)
1:1 (square) or 2:1 (wide) aspect ratio (preferred)
I have multiple AWS accounts for AWS Marketplace, which account should I choose to create multi-product solution?
Use the AWS account that is linked to Partner Central and owns your Marketplace product listings. This allows you to manage your solution's Foundational Technical Review (FTR) status, attach the solution to opportunities in ACE, and publish the solution to AWS Marketplace, all from a single location. If your products are distributed across multiple AWS Marketplace accounts, choose the account that owns the majority of the product listings you plan to include in your solution.
Can I include products from multiple sellers in my solution?
Yes. For solution listings, you need agreement from other sellers to include their products. For transactions (offer set), you need formal selling authorization to resell their products via CPPO.
How is "Deployed on AWS" badge eligibility determined?
Badge eligibility is evaluated separately for each product that run entirely on AWS infrastructure. You can have a mix of products that are eligible and not eligible in an offer set. On offer set procurement, only eligible products will qualify for PPA drawdown.
Can customers purchase individual products from my solution separately?
Yes. Each product maintains its own product detail page on AWS Marketplace. Customers can discover and purchase products individually through standard marketplace search and product pages, regardless of whether those products are included in the solution listing.
Important
Solution listings and offer sets serve different purposes and can contain different products:
Solution listings are marketing pages that showcase how products work together to address customer challenges. They can include any combination of products for discovery and educational purposes.
Offer sets are transactable packages containing specific private offers for procurement. The products in an offer set don't need to match the products listed in an associated solution.
For example, your solution listing might showcase a comprehensive architecture with 7 products, while a specific offer set associated with that solution might only include 3-4 products tailored to a particular customer's needs. This flexibility allows you to maintain rich marketing content in your solution while creating customized transactable offers for different customer scenarios.
How do renewals work for multi-product solutions?
Each product has its own agreement with independent renewal terms. Customers can renew individual components as needed.
How does ACE opportunity linking work?
ACE allows linking opportunities to offer. As part of this launch we will enable linking offer set to an opportunity. When an offer set is linked, all offers that are part of that opportunity get accounted for. One offer can be linked to only one opportunity regardless of whether the offer is standalone or part of an offer set
What editing options are available for offer set?
Before releasing the offer set (Draft state): Yes, you have full flexibility. First, publish individual offers with the OfferSetId specified. While offers are published but the offer set remains in Draft, you can modify buyer targeting and expiration dates to ensure consistency, and add or remove offers as needed.
After releasing the offer set: No. Once released to your customer, the offer set becomes immutable.
If changes are needed after release: You must recreate the entire offer set: create a new offer set, create new offers (or clone existing ones) with the new OfferSetId, associate all offers, release the new offer set, and cancel/expire the original.
What notifications do sellers receive for offer sets?
When you release an offer set, AWS Marketplace sends multiple notifications to help you track and manage your offerings. Sellers receive an email confirmation with the offer set ID, name, and a list of all component offers including their IDs and names. AWS Marketplace also publishes EventBridge events when offer set state changes occur, enabling you to build automated workflows and integrations that trigger custom actions when offer sets are released.
How does listing fee work for multi-product offer set?
Listing fees are calculated at the individual product level when the customer is billed for each product. Each private offer incurs listing fees based on the product, the vendor, and any selling authorization involved. For more information about listing fees for AWS Marketplace sellers, see the Understanding listing fees for AWS Marketplace seller documentation.
