Required Information for AWS Marketplace AI Agentic Listing

In this article, we'll walk you through the essential information required to create an AWS Marketplace AI Agentic listing.

Creating a listing on AWS Marketplace can be a daunting endeavor, as it is a long and taxing task that requires specific information and items that involve different areas within a company. With the help of Labra's user-friendly UI, we strive to make this process as smooth and painless as possible for our customers, providing step-by-step guidance and specifications throughout the listing stages.

To help you be a step ahead in the game, we have compiled the required data in the list below. Follow these best practices to ensure a swift and successful listing creation process using Labra for Marketplace.

Required assets

Product Details

1. Product Title

Your product title is the first impression you make on potential buyers. It's not just a name; it's your brand identity on AWS Marketplace. Ensure clarity and relevance. (see Fig. 1 for AWS Marketplace reference.)

Specs:

• Max 72 Characters
• Values can not start or end with whitespace characters (space, tab, newline)

Example:

• Product Title: Labra Cloud Marketplace and Co-sell Platform

Fig. 1

2. SKU (Optional)

Stock Keeping Unit is a unique alphanumeric code to identify your product internally within the marketplace ecosystem.

Example:

• Labra Contract 1

3. Product Logo

Make a strong visual impact with a product logo that meets AWS Marketplace specifications, ensuring it reflects your brand identity effectively. (see Fig. 1 above for logo placement on the AWS Marketplace listing).

Specs:

• Format: .png or .jpg
• Size: 120 to 640 pixels, with a 1:1 or 2:1 (wide) ratio
• White or transparent background

4. Short Description

Craft a concise and compelling short description, which will appear below "Vendor Insights" in the Listing Header. Avoid leading or trailing blank spaces for optimal presentation. (refer to Fig. 1 for another example of a short description on a Live listing.)

Specs:

• Maximum 1,000 characters

Example:

• Labra for Marketplace is your go-to solution for seamless cloud marketplace management. Streamline your operations and maximize efficiency with our comprehensive platform.

5. Long Description

Provide more detailed information about your product, giving potential buyers a deeper understanding of its features, benefits, and value proposition. It's an opportunity to elaborate on what sets your product apart and why buyers should choose it over competitors.

 Specs:

• Max 5,000 characters

Fig. 3

Fig. 4

6. Product Video URL (Optional)

Enhance your listing with a video showcasing your product's features and benefits.

Specs:

• Valid URL beginning with https://

• The URL should be publicly accessible.

   

Fig. 5

7. Product Highlights

Key features or benefits of your product that you want to prominently showcase to potential buyers. These highlights serve as quick bullet points that draw attention to the most compelling aspects of your product, helping buyers quickly understand its value proposition. (refer to Fig. 5 for other Product Highlights.)

Specs:

• Max 500 characters per highlight
• Min 1 highlight is required
• Max 3 highlights are allowed

Examples:

• Simplify Cloud Marketplace Management
• Centralized Inventory Management
• Automated Billing and Reporting
• Scalable Solution for Growing Businesses
• Streamlined Operations for Efficiency

8. Support Information

Support information is like a lifeline for customers—it's there to help them whenever they encounter issues or have questions about your product. Providing clear and accessible support details can enhance customer satisfaction and trust in your product. This information will be available in the 'Support' section of your listing (see Fig. 6 for reference).

Specs:

• Must include an email ID or support link.

Example:

• Customers can reach our Support Team via email at support@example.com

Fig. 6

9. Learning Resources (Optional)

Provide links to any resources you’ve created to help buyers learn more about your product, such as product sheets or white papers. Resource links are displayed to buyers in the 'Usage' section.

Specs:

• Provide both the Resource name and the URL.
  • Resource Name: Website (this is the text that will be visible within the Additional support box on your listing, as seen in Fig. 7).
  • URL: https://www.website.com (this is the link that will redirect potential buyers to that learning resource)

Fig. 7

10. Product Categories

This helps to classify your product, making it easier for buyers to find relevant listings when browsing through AWS Marketplace. Choosing the most appropriate categories ensures that your product is visible to the right audience. (refer to Fig. 3)

Specs:

• Min 1 category is required
• Max 3 categories allowed to be chosen

Example:

• Cloud Management Tools
• Business Intelligence & Analytics
• IT Security

11. Keywords for Search Results

Use specific words or phrases that you associate with your product to improve its discoverability in search queries within AWS Marketplace. These keywords help potential buyers find your product when they enter relevant search terms.

Specs:

• They can be single words or phrases
• Min 1 keyword is required
• Max 15 keywords are allowed to be inputted
• Max 250 characters (in total)

Example:

• Cloud marketplace management
• Cloud automation
• Inventory management
• Billing automation
• Scalable cloud solution

12. Configure End-user license agreement (EULA)
 

This legal agreement between you as the vendor and the end user (customer) outlines the rules and permissions for using your software or service on AWS. It clarifies what the customer can and can't do with your product, ownership of the product and its intellectual property, and procedures for handling any issues or disputes. Customers must agree to the terms of your EULA before using your product on AWS, ensuring a clear understanding of rights and responsibilities.

Choose between the Standard Contract for AWS Marketplace, or a Custom EULA (you will need to provide a URL to a custom end-user license agreement for your product).

The EULA will be visible to buyers in the 'Legal' section of your listing, as seen in Fig. 8 below:

Fig. 8

13. Refund policy
 

This outlines the terms and conditions under which customers can request a refund for your product on AWS Marketplace. It's important to have a clear and concise refund policy to manage customer expectations and ensure a positive buying experience. This will be visible in the 'Pricing' section of your listing (see Fig. 9).

Specs:

• Include contact information for refund requests
• Max 250 characters

Fig. 9

14. Allowlisted Accounts (Optional)

Allowlisted accounts on the AWS Marketplace are specific accounts that have been granted access to a product before it is publicly available. These accounts can view and test the product during its Limited status phase, ensuring everything functions correctly before full public release.

Specs:

• Add the AWS account IDs

AI Agent

15. API endpoint URL

The URL where your API receives requests.

Specs:

• Valid URL beginning with https://
• The URL should be publicly accessible.

16. API usage instructions

Provide detailed instructions for buyers to use your API such as API schema, rate limits, and usage examples. You can also add links to your documentation.

Specs:

• Maximum 4000 characters

Choose how customers authenticate and access your API. This selection determines the security approach for API requests. You can choose API Key, OAuth 2.0 or both.

18. API integration protocols (Optional)

Add additional information around how your agent or tools communicates with other systems. You can choose A2A, MCP or both.

Product Dimensions

19. Dimension Unit Type

It's basically the way you measure how customers use your product for pricing. Here are some common types:

• Bandwidth (Gbps/Mbps): Measures how fast data moves between servers.
• Data (GB/MB/TB): Measures the amount of data stored or transferred.
• Hosts: Counts the number of servers used.
• Requests: Measures the number of times customers ask for something.
• Users: Counts the number of people using the service.
• Units: A flexible option for custom usage metrics.

Specs:

• Choose the one that fits best with how your customers use your product.
• If it varies by dimensions or you're uncertain whether the unit type will change, choose the generic ‘Units’ option.

20. Purchasing Options

This refers to the ways customers can buy your product on AWS Marketplace. There are typically two main options:

• Multiple dimensions per contract: This option allows buyers to purchase different quantities of units for each pricing dimension you define. It provides flexibility for customers to mix and match their purchases based on their specific needs.
• Single dimension per contract: With this option, buyers can choose from a list of tiered pricing dimensions to purchase a desired tier or volume of units. It offers simplicity by presenting predefined options for customers to select from.

Example:
 

Let's consider a software product that offers different tiers based on the number of users and storage capacity.

• Multiple dimensions per contract: A customer can select 10 users and 100 GB of storage as one package.
• Single dimension per contract: A customer can choose from predefined tiers, such as a "Basic" plan with 5 users and 50 GB of storage or a "Pro" plan with 20 users and 200 GB of storage.

21. Contract Duration Options

This refers to the lengths of time for which customers can commit to using your product on AWS Marketplace. Offering flexible contract durations allows customers to choose the option that best suits their needs and budget. They can choose  (refer to Figs. 11.1 and 11.2 to see several contract duration examples).

Options:

• 1 month
• 12 months
• 24 months
• 36 months

Example:
 

• 12 and 24 months:

Fig. 11.1


Fig. 11.2

22. Display Name

This is the name that customers see when they interact with your product on AWS Marketplace. It's the user-friendly name that helps customers understand what your product is about. 

Specs:

• Max 80 characters

Example:

• Display Name: Platform fee, Labra CRM automation app, Additional Lisitng

Fig. 12

23. Contract Price (USD)

This is the price per unit in USD per each contract duration selected (see Figs. 13.1 and 13.2 for 12 and 24 months example).

 

Example:

Fig. 13.1


Fig 13.2

24. Description of Contract Dimension

This is a short explanation that helps customers understand what each dimension represents in your product's pricing. It's like a brief label that accompanies each pricing option (refer to Fig. 14).

Specs:

• Max 70 characters

Example:
 

Let's say you offer a contract dimension for "Data Storage" in your product pricing. The Description of the Contract Dimension for this could be: "Storage space for your files and data".

Fig. 14

25. Usage Dimensions (optional)

In a SaaS contract listing, you can choose to meter and charge your users on their additional usage by adding usage dimensions below. Assign a unique buyer-friendly description and price (as seen in Fig. 15) so your buyer knows what additional charges they may be charged upon apart from the usage permitted in the purchased contract dimension.

Fig. 15

26. Offer Availability by Country

This is like setting the boundaries for where your product can be sold. You can choose to make your product available in all countries, exclude certain countries, or limit it to specific countries where you want to focus your sales efforts. You can choose between:

• All countries (product available for purchase in all countries)
• All countries with exclusions (product available for purchase in all countries except the ones you exclude)
• Allowlisted countries only (product available for purchase only in countries you specify).

Buyer Registration Page

When a client purchases your product from AWS Marketplace, the final step is to click the “Subscribe” button at AWS, redirecting users to a dedicated buyer registration page hosted by Labra.io. This page allows you to collect buyer information such as email, name, company name, and other defined fields since AWS does not provide this information. You can customize the design of this landing page to align with your branding guidelines. (See Fig. 16 for an example Buyer Registration Page and the customizable fields.)

Fig. 16

1. Logo - the logo you previously provided will be incorporated into the Buyer registration page. 
   
   Specs: transparent or white background, 120 to 640 pixels in size, and a 1:1 or 2:1 (wide) ratio.
   
    
2. Background color - This color is shown behind the white input box.
   
   Specs: HEX or RGB
   
    
3. Heading Message - This text appears at the top of the white box and above all input fields and serves as the heading of the seller’s landing page.
   
   Example: Welcome! Fill in the information below to set up your account!
   
    
4. Form submission success message - This message is displayed to the buyer after they submit the form on the landing page. They will see this message before being automatically redirected to your Application's login page URL in 5 seconds, where they can log in, as seen in Fig. 17.
   
   Example: You will now be redirected to our signup page.
   
   
   Fig. 17
   
    
5. Button/button text color - The color of the ‘Submit’ button and its text, which is visible when all mandatory fields are filled.
   
   Specs: HEX or RGB
   
    
6. Background image (optional) - This is an image you can add which will appear on the left side of the screen. A photo or image depicting the seller's branding is recommended. (If no image is selected, this area will be white)
   
   Specs: .png or .jpg format, 1440 x 1080 pixels in size, with a 4:3 ratio
   
    
7. Form fields - You can add custom fields to the form on the landing page.
   
   Specs: The form includes mandatory fields (First name, Company name, and email address) which are required so Labra.io can notify buyers of different events.
   
    
8. Existing Buyer Message - This message appears to buyers who already bought your product. Since they already have login details, the message might be different from what new buyers get (refer to Fig. 18 below.).
   
   Example: Welcome back! You will be redirected to our sign-in page.
   
   
   
   Fig. 18
   
    

9. Email custom endnote (optional) - This message appears as the last paragraph in the email that Labra sends to your buyer confirming their purchase. The email is sent immediately after they submit the form on the landing page (refer to Fig. 19)

   
   
    

   📒  Note: Buyer's personally identifiable information is shared with the seller via email and will be visible in Labra.io’s UI whenever a buyer subscribes to the product.

Notifications

Notifications will be sent only to the email addresses you specify. You have full control over who receives these emails—it's entirely up to you. These notifications are fully customizable to align with your branding guidelines. (see Fig. 19 below.) Add at least one email address in each notification box to add specific recipients to each notification.

Fig. 19

Available Buyer Email Customizations

1. Custom logo on the buyer notifications (optional) - Add a custom logo which will be present as a banner at the top of the email sent to your buyer via Labra. (Refer to number 1 in Fig. 17).
2. Custom endnote on the buyer notifications (optional) - Add a custom endnote to buyer emails. (Refer to number 2 in Fig. 17).
3. Custom signature on the buyer notifications (optional) - Add a custom signature to buyer emails. (Refer to number 3 in Fig. 17).
    

The 3 event categories which sellers will get notifications for are:

1. Buyer lifecycle events:
   This includes notifications for buyer registration, subscription, entitlement updates, subscription status, and free trials.
2. Private offer events:
   This includes notifications for offer creation, acceptance, expiration, and restriction.
3. Metering events:
   This includes notifications for when metering is sent to AWS.
    

Specs:

• Min 1 email address per notification
• Add a comma after each email address