Navigation Menu: Settings > Customer Portal > Catalog Look & Feel

TIP:  For best results, use Google Chrome when working in the platform


Design the content, fonts, colors, images, and links that appear on your Cloud Marketplace home page.



Save all updates

Example:  Tech Data's Cloud Marketplace Demo LINK

How to add products to your marketplace - Premium Marketplace Subscribers

Products > My products

  1. Click Add+.
  2. Enter the SKU label for internal tracking.
  3. Enter the product name.
  4. Mark the product status as Active or Inactive.
    If the status is active, the product appears in the marketplace catalog, and the user can purchase it.
    As a best practice, keep the status inactive until you're ready to publish the product.

Set the available actions




Test drive the product. If you turn on this setting, you can set the maximum spend and select the test drive.


Purchase the product. Disable Buy for products that are informational only.


Learn more about the product. Common use cases for Info are an email link or a referral program where the user is directed from the marketplace to a third-party domain. If you include Info, you must include an Info URL, such as:

Require approval?

To require product-specific approval, click the Approval Required checkbox.
This puts the transaction into a "Pending" state and begins the approval workflow for the admin to approve the purchase. Then, when you're ready, you can complete the transaction.

Select an administrative user's (see Settings > Users) email address to approve the transaction. The administrator approves the transaction via email or in the admin portal at Settings > Approval requests.

Tip To automate administrative processes, see Step 10: Configure deployments.

Add descriptive content

  1. Enter a brief description of the product or service. This description appears in the marketplace catalog.
  2. Add one or more images of the product. The first picture is presented in the catalog view. Subsequent images appear in the product detail view.
    Supported formats include GIF, JPEG, SVG, and PNG. Width: 1720px. Height: 960px.
  3. Add a product logo.
  4. Add one or more keywords for search engine optimization (SEO).
  5. Associate the product with a category.
    Examples: Virtualization, Storage, or Managed Services.
    Categories that you create here are listed in the marketplace's left navigation panel.

When you're finished - Click Create.

Example product settings


Edit product details Premium Marketplace Subscribers

This is where you can set the user-facing content for your product.

Products > My products

  1. Find your product and click Edit.
  2. Click Edit product details.
  3. In the Description field, enter a detailed product overview.
  4. Add features with titles and descriptions.
  5. Add reviews with titles and content.
    SES currently does not support direct user feedback. Instead, you control what reviews and testimonials are shown for your product.
  6. Add FAQs with questions and answers.
  7. Add support information with titles and content.
  8. Add videos with titles and embedded links.
    For example:
<iframe width="560" height="315" src="" frameborder="0" allowfullscreen=""></iframe>
  1. Click Update.
  2. Click Back to product.


Configure deployments

Deployments use API calls and scripts to take action automatically, triggered by user events.

Multiple actions can be made in response to a single user event. For example, when a user creates a subscription, you can:

  1. Do an API call to your provisioning endpoint.
  2. Then do an API call to your SAP system to register the purchase.

API calls and scripts are executed in order, from top to bottom.

All actions for a given event must execute successfully for the deployment to be considered successful.

Suppose, for example, a deployment has three API calls. The first call succeeds, the second fails, and therefore the third is not executed. The effects of the first API call remain in place and are not "undone." There is no rollback of the first call. However, because all calls in the deployment are not executed successfully, the deployment status is marked as failed.

Action chains

The actions can be "chained." This means that response values can be captured and used as input to a subsequent action within the deployment.

Response values cannot currently be captured and used at a later time. They must be used within the working deployment.

Select a user event

Products > My products

  1. Find your product and click Edit.
  2. Under Deployment Actions, click Add+.

        Under Event, select a user event:

  • Deployment
  • Subscription create
  • Subscription trial end
  • Subscription change
  • Subscription cancel

Configure an API call

  1. Under Type, select API.
  2. Enter the endpoint URL.

Set the API request type

Under Request Type, select:

  • Post: Create a resource.
  • Get: Retrieve information about a resource.
  • Put: Update a resource.

Add any input fields

1. Click Fields and Add+.

2. Enter a field name and a label name. Field and label are the same, by default.

3. Enter a type:

  • String
  • Password
  • Number
  • Select
  • Multi-select
  • Cloud account

4. (Optional) Enter a default value.

5. (Optional) Enter a description.

Set the content type

  • Form URL-Encoded
  • JSON
  • Custom JSON

Edit the API credentials

  • Currently, only basic authentication is supported.
  • Add any query parameter names and user-input fields.

  • Add key-value pairs as request parameters sent with the API call. The values can contain placeholders that are replaced with values during deployment.
  • When deploying a product with an API callback, the customer completes a form built using input fields. To automatically generate the user-input fields, click Inp+.
  • Add output field names and mapping.

  • Output fields allow you to take output from this call and use it as input to the next call.

Example API call: create entitlement

Example API call: create report key

Output from "Create entitlement" is used as input to this API call.

Notes on API calls

  • Only JSON responses supported.
  • Following redirects is not currently supported.
  • Only GET, POST and PUT methods are supported.
  • Only 2xx status codes are considered successful.
  • The binary file substitute parameter returns a signed and timed URL to the file in a GCS bucket.
  • Currently, output variables can only be defined from root-level objects in JSON responses. Data types must be a string, number, or bool.


{  "first_name": "Jane", // <== OK to extract  "last_name": "Doe", // <== OK to extract  "addresses": [ // <== Can't extract from nested datatype    { "address": "1234 main st", "city": "mycity", "state": "zip": "11111" },    ...  ]  "is_customer": true

Test API calls

As a best practice, use cURL to test and verify API calls prior to entering the calls into SES.


curl -D --X POST -d '{"foo": "bar"}'

Configure plans

Offer multiple plans to allow users to choose one that's right for them. The product tile provides the initial product discovery in the marketplace. When the user double-clicks the product tile, they can view one or more plans. Plans can be the same product configuration offered with different payment methods, or plans can offer different levels of features.

Products > My products

  1. Find your product and click Edit.
  2. Under Plans, click Add+.
  3. Enter a plan name.
  4. Enter a short description.
  5. To add additional plans, click Duplicate or Add+.
  6. Click Save.


Add features to your plans

Typically, some features are common across all plans, while some vary among the plans.

1. Under Features, click Included.

2. Click Add+.

3. Enter a feature name.

4. For each plan, either:

  • Click to enter a checkmark.
  • Double-click to enter a string value.
  • Leave the field blank if the feature isn't included in the plan.

5. Click Save.


Configure prices for your plans

Typically, prices include a one-time setup fee and some recurring fees.

1. Under Price, click Edit.

2. Click to select time periods:

  • One Time (setup fee)
  • Month
  • Quarter
  • Year

Tip For best results, SES recommends monthly, quarterly, or yearly time periods.

3. For each plan, enter a price for the associated time period.

4. Select when the billing cycle starts:

  • Subscription date: Subscription renews on the same day of the month that signup occurred
  • Beginning of the month: Subscription renews at the beginning of every month
  • Specific date: Subscription renews on a specific date.

If you choose Beginning of the month or Specific date, the first bill is prorated. Suppose the customer signs up on the 12th and billing happens on the 15th. In this case, at the time of subscription an invoice is generated with two lines:

  • One for any setup fee
  • Another one for the prorated value of the recurring price for the days until the first renewal, in this case for three days

And then a second invoice is generated on the 15th, with the price for the full month.


You might charge a standard setup fee of $100, and a monthly fee that varies by plan type.

Add optional features to your plans

Options are added features that end users can choose to purchase.

1. Under Features, click Optional.

2. Click Add+.

3. Enter a feature name.

4. For each plan, either:

  • Enter a checkmark
  • Enter a string value
  • Leave the field blank if the option cannot be added to the plan

Configure prices for your optional features

1. Under Features, click Optional.

2. Under Price, click Edit.

3. Click to select time periods:

  • One Time (setup fee)
  • Month
  • Quarter
  • Year

4. For each plan, enter a price for the associated time period.

5. (For monthly only) Select when the billing cycle starts:

  • Subscription date: Subscription renews on the same day of the month that signup occurred.
  • Beginning of the month: Subscription renews at the beginning of every month.
  • Specific date: Subscription renews on a specific date.

6. (Optional) Require the feature.
This is often used for regulatory fees or taxes that are not included in the base price, but need to be included on the invoice.

7. (Optional) Force fixed quantity.
This allows you to require that an option be purchased in groups, for example, seats must be bought in groups of five.

Example 1

Example 2