View a markdown version of this page

Deciding what to list in AWS Marketplace - AWS Marketplace

Deciding what to list in AWS Marketplace

Everything you list in AWS Marketplace is one of two things: a product or a solution. This page explains the difference, when to create each, and how they work together, so you can set up your listings in the right order.

You create both in AWS Partner Central. Creating them there is what makes them readable by AWS Marketplace search, Agent Mode, and the Solutions Matching Engine, which is how customers search, evaluate, and buy. A listing created anywhere else does not appear in any of them.

The two building blocks

Note

Not every product needs a solution. A product is discoverable on its own. Create a solution only when you want to target what your product does at a specific audience, use case, or outcome. Creating more solutions does not by itself improve your search ranking.

Product

What you sell. Your software, service, or practice.

A product is your foundation. It is the core capability a customer buys and deploys. It carries the product code that measures the revenue you generate and keeps you eligible for funding, and it holds your pricing and delivery details. You build a product once, then take it to market many ways.

Solution

How you win customers. Your product framed for a specific customer.

A solution is your growth engine. It names who you serve, the problem you solve, and the result the customer gets, so the right customers discover you and choose you. A solution can be one product positioned for a market, or a set of products bundled into one outcome.

Your product is what you deliver. Your solution is the answer to a specific customer's business challenge.

Which one carries what

Build each piece of information in one place only. Do not restate product-level information at the solution level.

On the product

On the solution

Product code and revenue measurement

The customer you serve

Pricing, offers, and delivery

The problem you solve

Funding eligibility

The result you deliver

Integration with AWS

The case studies that prove it

The validations that back it: AWS Specializations and Foundational Technical Review (FTR)

How products and solutions work together

The solution tells the story. The product delivers the result and attributes the revenue.

  • A customer who already knows what they want can find your product directly and buy it.

  • A customer still describing the problem finds you through the solution, reads who you serve and the result you deliver, and buys the product behind it.

Every solution published in AWS Marketplace requires a product behind it. A solution with no product cannot be bought, because the product is what the customer transacts and what AWS uses to attribute revenue to you.

Note

The reverse is not true. Not every product needs a solution, and adding more solutions does not by itself improve your search ranking. Create a solution when you want to reach a specific audience with a specific outcome.

The two types of solution

Type

What it is

When to use it

What it adds

Single-product solution

One product positioned for a specific sector, audience, or outcome

You already sell a product and want to reach a customer you are not reaching, or you sell one thing and want it discoverable by problem rather than by name

A new go-to-market story over an existing product, with no rebuild of the product

Multi-product solution

Several products bundled into one customer outcome

The result takes more than one product, including products from other AWS Marketplace sellers and from AWS

Offer sets, so a customer can transact the bundle as a single purchase

The relationship between products and solutions is many-to-many. Multiple products can power one multi-product solution, and one product can power multiple single-product solutions.

For offer sets and the additional requirements that apply when your solution includes another seller's products, see Preparing your solution listing and Preparing your offer set.

Setting up your listings

Create your products first, then the stories you take to each customer.

Step 1: Create a product for each core thing you sell

One product per software, service, or practice. This gives you a product code, measures your revenue, and establishes funding eligibility. Everything else builds on it.

If you sell software, create the product a customer deploys. If you sell services or consulting, create a professional services product for the capability you charge customers for.

For the product types available and how to choose one, see Preparing your product for AWS Marketplace.

Step 2: Add a solution for each customer cohort you want to win

This step is optional. Not every product needs a solution, and a product is discoverable without one. Take this step when there is a specific customer cohort you want to reach.

Anchor each solution to a customer profile, the use case, and the challenge that customer faces. One product can power many solutions, so you reach new customers by telling a new story, not by rebuilding your product.

  • If you go to market one way, create one solution that extends your product to the customer you serve with the result you deliver.

  • If you go to market across different customer segments, create one solution per customer, each with its own problem, result, and proof, so every customer sees itself.

Step 3: Associate more products to your solutions

Add products to a solution when the result takes more than one, including products from other AWS Marketplace sellers and from AWS. Add the same product to several solutions when it solves the customer challenge more than one way.

Deciding how many solutions to create

Create the number of solutions needed to cover your go-to-market, and make each one distinct. Fewer, sharper solutions reach more customers than a long list that blurs together.

Quick check Take any two of your solutions and answer "who is this for" and "what problem does it solve." If the answers read the same, combine them into one stronger solution. When each solution is distinct, each one wins the customer it was built for.

Multiple use cases can live inside one solution when they serve the same customer and lead to the same result.

AWS Marketplace does not set a number. AI-assisted solution listing identifies when a new solution reads too much like one you already have and shows you how to set it apart or combine them. This is a publishing requirement, not advice: you cannot publish a solution that duplicates your product listing or another of your solutions until you differentiate it. For more information, see AI-assisted solution listing.

If you already have listings

Find your situation and start there. Everything you have already built continues to count, including your specializations and case studies.

You have a product, but no solution

Create solutions for your existing product to target a specific audience. You do not rebuild the product. You attach the relevant case studies, specializations, and use cases. Without a solution, a customer searching by use case cannot find you easily.

You have a solution, but no product

Create a product behind each solution. The product is the only way AWS attributes revenue to you and associates an opportunity with what you sell.

You have both, but they are not linked

Link each solution to the product that delivers it. This is the most common situation for sellers who listed in AWS Marketplace and worked with AWS Partner Network separately, and it is the one worth acting on first. An unlinked solution cannot be made public, and cannot be discovered by customers.

You have neither

Start at step 1. Create a product for the core thing you sell, then build the solutions that take it to each customer you want to win.

Where to start if you have many solutions

Prioritize the solutions you are actively selling. If a solution is attached to an opportunity, or carries a specialization, link it to a product first. Solutions you have not used in years can wait.

If several of your solutions each carry a specialization but describe the same customer and the same result, they should be one solution. Contact AWS Partner Network support and they will consolidate them for you without losing the attached specializations.

Scope

  • AWS Marketplace does not support hardware listings.

  • If you resell AWS services and add Professional Services, Advisory or Consulting Services, or Managed Services on top, this guidance applies to you.

What a strong solution looks like

Expand into new markets from one product

Each solution opens a new audience, as long as it speaks to a genuinely different customer and result. Read down a column and you see one product carrying several different stories. Read across a row and you see one product going to market in different ways.

The following example shows two products supporting six solutions across three industries.

Product

Solution

Customer

Result

Proof

Migration and Modernization Service

Healthcare Compliant Cloud Migration

Hospital system IT department

Regulatory compliance guarantee and sign-off in half the time

3 case studies, Migration and Modernization specialization, Healthcare Industry specialization

Migration and Modernization Service

Modernize Financial Data for Growth

Banking line of business buyer

Insight into customer behaviors and trends to create data-driven strategies

2 case studies, Migration and Modernization specialization, Financial Services specialization

Migration and Modernization Service

Seasonal Scale for Retail

Retail

Modernized applications that keep up with demand and streamline operations at scale

2 case studies, Migration and Modernization specialization, Retail Industry specialization

Security Software

Secure and Connect Healthcare Systems

Hospital system IT department

Reduced regulatory costs from cybersecurity attacks while maintaining PHI compliance

3 case studies, Security specialization, Healthcare Industry specialization

Security Software

Secure Financial Transactions

Banking line of business buyer

Protected customer financial data, with bad actors stopped, while maintaining agility and compliance

2 case studies, Security specialization, Financial Services specialization

Security Software

Protect Your Brand and Storefront

Retail

Protected business and customer data while meeting retail compliance standards

2 case studies, Security specialization, Retail Industry specialization

What this is not: look-alike solutions that dilute each other.

What each solution should say

1. Identify the customer. The industry, size, and role you serve. Create a separate solution only where the buyer, the problem, and the proof are genuinely different. Where your positioning is the same across industries, use one solution and select multiple industries.

2. State the result. The problem you solve and the outcome you deliver. A specific number makes the story land harder.

3. Show the proof. Case studies for that customer segment. Include as many case studies as you can, and reuse a case study on every solution it supports.

After you publish

Specializations and product-led growth features are additive on an existing solution. You apply for a specialization through a Program Application in Program Navigator in AWS Partner Central by selecting a solution, and each one makes an existing listing stronger. For more information, see Preparing your solution listing.

Frequently asked questions

Do I need a solution for every product?

No. A product is discoverable on its own. A solution makes you discoverable to customers describing a problem instead of searching your name, so it is how you reach customers who do not know you yet.

Does a solution need a product?

Yes. Every solution requires a product behind it. The solution tells the story, and the product delivers the result and attributes the revenue, so a solution with no product behind it cannot be bought.

How many solutions should I create?

As many distinct solutions as you need to address your target customer segments. See Deciding how many solutions to create.

Can one case study support more than one solution?

Yes. A customer win can support every solution it applies to, so a strong case study works across your portfolio rather than sitting on one listing.

Where do I create my product?

In the AWS Partner Central console. In the left navigation pane, under Build, choose the product type you want to create, then choose Create product. For more information, see Creating a product in AWS Marketplace.

What is a leads-only listing, and when should I use one?

A listing with no pricing and no public offer. Use it when you want to be discoverable before you are ready to transact, or when your business runs on private offers. You can add pricing and offers later without starting over.

What a leads-only listing supports depends on your product type:

  • AMI and container products support contract-priced private offers only. Usage-based private offers are not available on a leads-only listing.

  • Machine learning products cannot be leads-only, because a machine learning private offer requires a public offer.

For more information, see Leads-only listings.

How do specializations work?

An AWS Specialization is how AWS confirms that a partner has proven technical skill and real customer results in a specific industry or technical domain, such as Data and Analytics or Security. You apply through a Program Application in Program Navigator in AWS Partner Central, selecting a solution and the case studies that support it. It is a validation, not a field you fill in, and it is additive after your listing exists. Specializations on solutions support discoverability and customer trust. For more information, see AWS Specialization Program.

Several of my solutions each carry a specialization, and they really should be one solution. How do I consolidate them?

Contact AWS Partner Network support and they will consolidate them for you, so you do not lose the specializations attached to the solutions you are merging.

I have a hardware or resale solution for AWS resell. Does this guidance apply to me?

This guidance covers software products and the solutions built on them. Hardware and resale follow a different path:

  • AWS Marketplace does not list hardware. Hardware is listed on the Device Listing Page. You can create a solution for a hardware offering, but it stays in Limited.

  • You cannot create a AWS Marketplace product that only resells AWS services. To launch an AWS opportunity you still need a product or a solution, and AWS attributes your resale revenue because you handle the billing.

These paths apply to few sellers. For the right approach, contact AWS Partner Network support.