Cloudmore is a Commerce Control Plane that enables the resale and management of cloud services through a multi-tier distribution model.
The platform provides end-to-end subscription lifecycle management, billing automation, and white-label self-service capabilities.
Core Value Proposition:
-
Unified commercial architecture across multiple vendors and cloud services
-
Automated subscription lifecycle management (provisioning, upgrades, renewals, cancellation)
-
Multi-model monetization (subscription, usage, consumption, hybrid)
-
White-label self-service portal for end customers
-
API-first architecture for system integration
Role Hierarchy
The platform operates on a three-tier distribution model:
-
Seller (aka service owner or vendor, like Microsoft or Adobe) publishes services to Marketplace.
-
Broker (aka reseller or distributor) makes services available via E-Store.
-
Organization (company consuming services) purchases subscriptions from the E-Store via self-service.
Entity Relationships
|
Entity |
Description |
Key Actions |
|---|---|---|
|
Seller |
Original service owner/vendor |
Creates services, publishes to Marketplace, sets cost prices |
|
Broker |
Reseller/distributor |
Adds services from Marketplace, sets sales prices, manages organizations |
|
Organization |
End consumer |
Adds services from E-Store, creates subscriptions, manages users |
Key Terminology
|
Term |
Definition |
|---|---|
|
Commerce Control Plane |
Official name of the platform. |
|
CSP |
Cloud Solution Provider (Microsoft partner program) |
|
NCE |
New Commerce Experience (Microsoft's updated commerce platform) |
|
Tenant |
Microsoft-specific term for an organization |
|
Custom Service |
Any non-Microsoft service (seller-created) |
|
Host Admin |
Cloudmore internal super-admin layer |
|
ISV |
Independent Software Vendors who create digital services and publish them to Cloudmore's Marketplace |
|
ERP |
Enterprise Resource Planning — an external financial system where Brokers export Cloudmore's billing data via API or Excel for invoice generation, payment processing, and financial reporting |
Core Concepts
Services
A Service represents a cloud offering made available through the platform. Services contain metadata and configuration including billing date (1–28 of month), provisioning type (Email or REST API), user assignment, licence keys, custom properties, and marketing information.
|
Type |
Description |
Examples |
|---|---|---|
|
Custom Services |
Third-party integrations added by a broker manually |
Dropbox, Kaspersky, WatchGuard |
|
Microsoft CSP |
Microsoft Cloud Solution Provider services |
Office 365, Azure |
Marketplace vs E-Store
|
Concept |
Audience |
Purpose |
|---|---|---|
|
Marketplace |
Brokers |
Catalog of services available for the broker to add |
|
E-Store |
Organisations |
Catalog of services the broker has made available |
Product Types
One-Time Billing
Single payment at purchase. Used for hardware or perpetual licences (~5% of platform subscriptions).
Recurring Billing (Service Plans)
1. Licence-Based (Product-Based) Plans
Pay upfront for a defined quantity. User defines quantity at subscription creation, billed for the upcoming period. Example: 10 Dropbox licences × €15/month = €150.
2. Consumption-Based (Metered) Plans
Pay retroactively based on actual usage. No payment at subscription creation; consumption reported at end of billing cycle. Example: 9.5 GB used × €10/GB = €95.
Key API for Metered Billing: POST /api/consumption (submit) and GET /api/consumption/{taskId} (check status).
|
Setting |
Behavior |
|---|---|
|
Billing Day Only |
Generate billing only on service billing date for full cycle |
|
Pro-rate Billing |
Proportional billing for mid-period changes |
|
First Partial Cycle |
Configurable handling of initial incomplete period |
Subscriptions
Subscriptions are created from Products and represent active service consumption.
Lifecycle: Created → (Trial →) Active → Cancelled → Deleted
|
State |
Description |
|---|---|
|
Trial |
Optional trial period. Seller sets duration, auto-conversion to paid, and whether product change is allowed. |
|
Active |
Generating billing, service accessible |
|
Cancelled |
Marked for non-renewal, still usable until deletion |
|
Deleted |
No billing, access revoked |
Add-ons are optional extras attached to subscriptions with independent pricing (subscription, quantity, selected, or metered pricing models).
Read more about subscription management
Service Agreements
|
Agreement Type |
Configured By |
Triggered When |
Blocks |
|---|---|---|---|
|
Custom Service |
Seller |
Adding service from E-Store |
Service subscription |
|
MCA |
Organisation or Broker on their behalf |
First Microsoft CSP purchase |
Microsoft subscriptions |
|
Broker-Level |
Broker |
User login |
Platform access (after 30 days) |
Pricing Architecture
Price flow: Seller Cost Price → Broker Cost → Broker Sales Price → Organisation
|
Price Type |
Set By |
Description |
|---|---|---|
|
Cost Price |
Seller |
What the seller charges the broker |
|
Recommended Price |
Seller |
Suggested end-customer price |
|
Sales Price |
Broker |
What the broker charges the organisation |
Price determination hierarchy: (1) Subscription-specific price, (2) Organisation-specific price, (3) Global price list entry, (4) Seller recommended price (fallback).
Read more about price management
Organisations can operate in different currencies. ISO 4217 currency codes required. Read more about currency support
Billing System
The billing job runs on configured billing dates (1–28 of month). For each active subscription it checks quantity or consumption, looks up the price, and generates a billing line.
|
Report Type |
Content |
|---|---|
|
Total Billing Report |
All services, all organisations, date range filter |
|
Monthly Billing Per Organisation |
Per-org breakdown by service/subscription/product |
|
Azure Billing |
Microsoft Azure-specific with margin support |
|
NCE Billing |
New Commerce Experience Microsoft subscriptions |
Export formats: UI display, Excel (.xlsx), API (JSON). Read more about billing and reconciliation
What Cloudmore handles: billing data generation, subscription management, pricing, consumption tracking. Does not handle: payment processing, invoice generation, payment collection. Brokers export billing data via API/Excel and integrate with their ERP for invoicing.
White-Label & Branding
|
Element |
Customisation |
|---|---|
|
Logo |
280×54 pixels (expanded menu) |
|
Icon |
54×54 pixels (collapsed menu) |
|
Colors |
Theme colors throughout UI |
|
Banner |
Header banner image |
|
Login Page |
Custom background, logo |
|
Domain |
Custom URL (e.g., |
|
Start Page |
Custom HTML content |
|
Email Domain |
Send from broker's domain |
Read more about branding and white labelling
User Management
Cloudmore uses role-based access control (RBAC) across three tiers. Full permissions matrix (Google Sheets)
Authentication methods: (1) Username/Password, (2) Microsoft SSO — Azure AD integration, (3) SAML SSO — Enterprise identity providers.
Read more about user management
Microsoft Integration
|
Service |
Description |
|---|---|
|
Microsoft 365 CSP Direct |
Office 365, Enterprise solutions |
|
Microsoft Azure |
Virtual machines, cloud storage, infrastructure. Exists as Azure Plan and Azure Legacy (deprecated). |
Tenant Linking
Microsoft customers (tenants) must be linked to Cloudmore organisations. Methods: (1) Automatic — Organisation adds Microsoft service from E-Store, (2) Manual — Broker links existing tenant, (3) Bulk — "Auto create and link" all tenants at once. Unlinked tenants do not appear in billing reports.
Read more about Microsoft tenant linking
Microsoft Authentication
Brokers must configure an MFA token for Partner Center API integration. In Cloudmore 5.0, navigate to Services > Microsoft 365 CSP Direct > Microsoft CSP Authentication. Prerequisites: Privileged Role Administrator account with MFA enabled, Admin Agent role in Partner Center. Token auto-refreshes nightly.
Read more about Microsoft authentication
API Reference
Seller level: https://api.cloudmore.com/api/sellers/{sellerId}
Broker level: https://api.cloudmore.com/api/resellers/{resellerId}
Full documentation: https://api.cloudmore.com/swagger/
|
Entity |
ID Format |
Example |
|---|---|---|
|
Organization |
UUID |
|
|
Service |
UUID |
|
|
Subscription |
UUID |
|
|
Product |
UUID |
|
Organisation Management APIs | Subscription Management APIs | Billing APIs | Consumption APIs
Service Integrations
Provisioning types: Email (notification to configured address) or Service Connector (webhook call to predefined endpoint).
Read more about service integrations
All provisioning events are logged. In Cloudmore 5.0, navigate to Reports > Audit Log > Provisioning Log.