Marketplaces

Updated: September 29, 2021
Contents

Video Introduction

Overview

Marketplaces represent objects on the CloudBlue Connect platform that logically define available go-to-market channels of Distributors and Resellers. Marketplaces are used to express different logical concepts as introduced and schematically illustrated below:

  • Regions: Marketplaces can represent different geographical regions or countries. Namely, you can create a marketplace for the “United States” region, “Canada”, “Germany”, and so on.
  • Sizing: Marketplaces can be differentiated by the size or scale of the target businesses. For instance, “Consumer”, “SOHO”, “SMB”, “Enterprise”, etc.
  • Industries: Marketplaces can represent different industries of the offered solutions. You can create different marketplaces for “Healthcare” products, “Fintech”, “Energy”, and so on.

Marketplaces are linked with the operational systems that are used to execute their go-to-market strategies and that are referred to as Hubs on the Connect platform. The following illustrates and describes hubs, marketplaces, and tier accounts relationship on the platform:

  • Marketplace should be bind to at least one hub.
  • Each hub hub can serve multiple marketplaces.
  • Each marketplace can be represented in multiple hubs

Mapping Marketplaces to Hubs

While most commercial systems natively support the marketplace concept, some systems might need to map their generated marketplaces to their hubs manually. Therefore, the system prompts Distributors and Resellers to map their hubs during the manual marketplace creation and allows editing selected hubs via the configuration wizard:

In general, several hub are linked with a single marketplace (usually staging and production). Note that generated tier accounts are also managed by your specified hubs. Therefore, the system prompts to specify the Tier Account External ID.

This allows the CloudBlue Connect platform to detect a required marketplace when a created subscription is linked with a particular tier accounts hierarchy as schematically illustrated below:

Marketplaces can be defined on the same or different levels of the tier accounts hierarchy. The system supports large number of possible configurations.

Marketplace Detection Logic

Subscriptions are usually created in the hierarchy of tier accounts as illustrated below:

In general, a subscription is associated with 3 tiers (Tier-0, Tier-1, and Tier-2). In case the marketplace was not explicitly specified while creating a subscription, the system uses a certain logic to detect a required marketplace as illustrated below:

Namely, marketplace is associated with the lowest tier of a given hierarchy is associated with the requires subscription. In the example above, T1 Reseller represents a marketplace that is associated with the provided subscription.

Next Steps

To learn more about Hubs, Marketplace and Hub API, the provided graphical user interface, and other operations that are interconnected with the Marketplace module, refer to the following sub-articles:

Is this page helpful?
Translate with Google
Copied to clipboard