Skip to content

Key terms

Here are some of the key terms used in the Cloudmore API and this document:

Seller – A Seller in Cloudmore is a tenant that wants to offer services to Brokers. A seller is typically a Service Provider, ISV, Distributor, Managed Service Provider(MSP), or Enterprise. The Seller will create and publish services to the Marketplace, where a broker can resell to end-users.

Broker – A Broker is a tenant that wants to offer services to end-users. A Broker can be an MSP, Reseller, Telco, or larger Enterprise organization. A Broker can provide services from Sellers or add their own services.

Organization – An organization is a tenant that consumes services. An Organization can be a company, business unit, or department. An Organization purchases services that the Broker is offering to them.

User – A User is a person in an organization that is using a service. Users can also be used for administrative access at all levels in Cloudmore.

Services – A service is a wrapper that contains the general service marketing information and provisioning action. In Cloudmore, services are either provided by a Seller, set up at the Cloud Service Broker level, or provided by Cloudmore as a “pre-integrated” service. Any service set up
by the Seller or Cloud Service Broker is known as a Custom Service.

Product / Service Plan – A Product / Service Plan is the actual item the organization buys. A product has a name, item code, price, and subscription and cancellation rules. A service may have one or several products.

Addons – Addons are products offered together with another product. An addon will have a name, item code, and price details. An addon will follow the same subscription and cancelation rules as the product.

Product Custom Properties – A product may have unlimited custom properties. These properties allow additional structured data to be stored with the product. Custom properties can be hidden data used to provide additional data to an external API or used to collect information
from the user and store it with the subscription.

Subscription – A subscription is created under a service. The subscription will contain one (1) product and, optionally, addons. The subscription terms will be based on the product. If the product is an annual subscription with monthly payment, those properties will make up the terms of the

Marketplace – The Marketplace is where a Cloud Service Broker finds new services that they want to resell. Services are presented with marketing information and may also have an associated agreement. After adding a service from the Marketplace, the service will be shown in the
Services and is ready for reselling.

E-store – The E-store is where organizations find new services to buy. After adding the service from the E-store, the organization can start to create subscriptions and use the service.

Approval Process (AP) – The approval Process can be enabled per organization. When active, any purchase, either new or change of an existing subscription, will generate an approval request that needs to be approved by the Cloud Service Broker. An approval trigger amount may also be
specified to allow purchases below a certain threshold, while purchases above the threshold would trigger the Approval Process.

Organization Custom Properties – Organizations and users may have custom properties. Custom properties are created by the Cloud Service Broker and can be used to capture or store additional information. Custom properties can be text fields, dropdowns, or checkboxes and can be
marked as mandatory.

Subscription Period – The subscription period is the agreement length of a subscription that the customer commits to buying the service. Cloudmore supports both the Pay-As-You-Go (1-month subscriptions) model and long-term subscription periods. Renewal rules are set on the
product if it is a custom product, otherwise defined by the service provider.

Payment Frequency and Billing Interval – The payment frequency defines how often payment should happen. The frequency can either be monthly, quarterly, or yearly. The payment frequency can be aligned with the subscription period or a shorter value. For instance, an annual subscription may be paid monthly. The payment frequency may be referred to as a billing interval in billing reports.

Billing Date – The date when billing data is generated. Each service has its billing date either set in Cloudmore or decided by the vendor. On the billing date, billing data for the service will be generated and stored.