Umbrella contract package scenarios

Umbrella Contract Service Package Arrangements let you bundle multiple services into a single, easy-to-manage package on your contracts. Instead of listing every service individually on an invoice, you can present one clear package line—while still tracking every component behind the scenes.

This topic walks you through the most common packaging scenarios so you can choose the approach that best fits your business and your customers' expectations.

  • Simplified invoicing: Present a single package line on customer invoices instead of a long list of individual services.
  • Operational visibility: Continue to track each included service with its own quantity and cost for internal reporting and cost analysis.
  • Flexible pricing: Choose between a fixed package price or a price that automatically rolls up from the included service components.
  • Scalable packages: Link included service quantities to the package quantity so that when the package count changes, the services update automatically.
  • Accurate mid-period billing: Use adjustment types to prorate charges when services are added or removed during a billing period.

Understanding the packaging scenarios

The following scenarios describe the most common ways to structure an umbrella package. You can mix and match these approaches across different contracts to fit each customer relationship.

Scenario 1: Package units match included service units

Use this scenario when every sold unit receives the same set of services. For example, if you sell 50 managed desktops, each desktop receives monitoring, support, an RMM agent, and antivirus.

When to use it: Standardized per-user or per-device bundles where every unit gets identical coverage.

How to set it up:

  1. Create a Service Package Arrangement on the contract.
  2. Set the package quantity to the number of units sold (for example, 50 desktops).
  3. Add each included service and set its quantity to match the package quantity.
  4. Optionally, enable Package Unit count defines service count so that included service quantities stay synchronized when the package quantity changes.

Scenario 2: Included service units are independent of package units

Use this scenario when the package represents an overall service—such as a managed phone system—but each component inside the package has a different quantity.

When to use it: Managed environments where you sell one service but need to track varying quantities for users, devices, lines, or trunks.

How to set it up:

  1. Create a Service Package Arrangement with a package quantity that represents the sellable unit (for example, 1 managed phone system).
  2. Add each included service with its own independent quantity.
  3. Do not link the included service quantities to the package quantity unless that specific service should always move with the package count.

Scenario 3: Single-package unit with variable service quantities

Use this scenario when you sell one monthly managed service to the customer but need to track many internal quantities such as users, endpoints, servers, and licenses.

When to use it: All-inclusive or fixed-fee managed services where the customer expects one monthly line item on their invoice.

How to set it up:

  1. Create a Service Package Arrangement with a package quantity of 1.
  2. Add all included services with their actual operational quantities.
  3. Configure the invoice display based on your agreement with the customer: show only the package line, list included service names, or show full included service details grouped under the package.

Scenario 4: Package price calculated from included services

Use this scenario when the package price should automatically reflect the total of all included service components rather than being a manually entered amount.

When to use it: Modular or component-based packages where the price must transparently roll up from the services being delivered. This works especially well with Scenario 3.

How to set it up:

  1. Create the Service Package Arrangement and add all included services with their quantities and unit prices.
  2. Enable Set unit price based on included services.
  3. The package unit price, cost, and margin are calculated automatically from the included service extended prices (quantity × unit price for each service).

Example packages

The following examples show common real-world packages and how to configure them. Use these as templates and adapt them to your service catalog.

A per-desktop package where each desktop receives monitoring, support, an RMM agent, and antivirus.

Setting Value
Package quantity 50 desktops
Pricing method Manual package unit price or catalog package price
Quantity behavior Included service quantities match the package quantity
Invoice display Show one package line; optionally list included service names

Included services:

Service Quantity Notes
Desktop Monitoring 50 Matches the package quantity
Desktop Support 50 Matches the package quantity
RMM Agent 50 Matches the package quantity
Desktop Antivirus 50 Matches the package quantity

When a customer adds or removes desktops, adjust the package quantity. If quantity linking is enabled, the included services update automatically.

A per-user package combining support, Microsoft 365 licensing, Intune management, security awareness training, dark web monitoring, and documentation access.

Setting Value
Package quantity 75 users
Pricing method Manual package unit price
Quantity behavior Most included services match the package quantity; optional services may vary
Invoice display Show one package line for the user bundle

Included services:

Service Quantity Notes
Desktop Support 75 Per-user support entitlement
M365 Office 75 Per-user license
Microsoft Intune Management 75 Per managed user or device
Monthly Phishing Testing 75 Per-user security awareness
Dark Web Monitoring 75 Per-user monitoring
MyGlue Access 75 Per-user documentation access

Link all user-based services to the package quantity. If any service has a different commercial basis, configure its quantity independently.

A voice services package sold as one managed phone system with each component tracked at its own quantity.

Setting Value
Package quantity 1 managed phone system
Pricing method Set unit price based on included services
Quantity behavior Each included service has its own independent quantity
Invoice display Show one package line; optionally list included service names

Included services:

Service Quantity Notes
3CX 1 One phone system tenant
PBX Line Management 35 Per PBX line
Phone Line Fee 42 Per phone number
Phone Service Support 35 Support for phone service users
SIP Trunks 4 Per trunk
Cisco Phones 35 Per rented phone device
User Support 35 Per phone user
Fiber Trunk 1 Connectivity line fee

Because Set unit price based on included services is enabled, the package price is automatically calculated from the total of all voice components. The package remains one sellable unit on the invoice while individual service quantities are tracked independently.

A fixed-fee managed service sold as one monthly package while tracking user, endpoint, server, security, and hosting quantities internally.

Setting Value
Package quantity 1 monthly managed IT service
Pricing method Manual fixed package price, or set based on services for cost-plus pricing
Quantity behavior Each included service has its own independent quantity
Invoice display Show one package line only

Included services:

Service Quantity Notes
Desktop Monitoring 85 Per monitored desktop
Desktop Support 80 Per supported user or desktop
Mobile Device Support 40 Per mobile device
RMM Agent 93 Desktops and servers monitored
Datto AV 85 Endpoint antivirus license count
Server Antivirus 8 Server antivirus license count
SaaS Backup for Server 8 Server backup count
MSSP Services 1 Proactive security management
Monthly Phishing Testing 80 Per-user security awareness
Dark Web Monitoring 80 Per-user monitoring
M365 Office 80 Office license count
MyGlue Access 80 Per-user documentation access
Hosting Services 2 Hosted sites or services

For a fixed managed service price, define the package price manually. If the price should reflect the sum of the component services, enable Set unit price based on included services.

A security add-on package that can be attached to a base managed service agreement. It can be priced per user or as a rolled-up package.

Setting Value
Package quantity 100 users (standard plan) or 1 security add-on (custom plan)
Pricing method Manual per-user price for standard plans; set based on services for custom plans
Quantity behavior User-based services typically match the package quantity; endpoint and server services may vary
Invoice display Show one add-on package line

Included services:

Service Quantity Notes
MSSP Services 1 Proactive security service
Monthly Phishing Testing 100 Per user
Dark Web Monitoring 100 Per user or monitored identity
Datto AV 90 Per protected endpoint
Server Antivirus 10 Per protected server
Microsoft Intune Management 100 Per managed user or device

For a standard per-user plan, set the package quantity to the user count and link user-based services. For a custom security service, set the package quantity to 1 and configure each service quantity independently.

Avoiding a common configuration conflict

You should not enable both Package Unit count defines service count and Set unit price based on included services at the same time. When both options are active, the package quantity can be counted twice, which inflates the invoiced total.

How the conflict occurs:

  • Package Unit count defines service count copies the package quantity to each linked included service.
  • Set unit price based on included services calculates the package unit price as the sum of each included service extended price (service quantity × service unit price).

If both are enabled, the calculated package unit price already reflects the full package quantity through the included service quantities. When that unit price is then multiplied again by the package quantity on the invoice, the total is inflated.

EXAMPLE  A package with a quantity of 50 includes five services priced at $2.00 each. Quantity linking sets each service to 50 units, so each service extended price is 50 × $2.00 = $100.00. The calculated package unit price becomes $500.00 (five services × $100.00). If that unit price is then billed against 50 package units, the total becomes 50 × $500.00 = $25,000.00—instead of the expected $500.00.

Exception: When the package quantity is 1, the conflict does not occur because multiplying by 1 does not inflate the total. However, quantity linking has no practical effect with a package quantity of 1 because every linked service would also be forced to 1. For a package quantity of 1 with variable service counts, leave quantity linking disabled and use service-based pricing only when the package price should roll up from the included services.

Quick reference

Your goal Package quantity Service quantities Pricing method
Every unit gets the same services Number of units sold Match the package quantity Manual package price
Package represents a solution with varying components 1 or the sellable unit Independent per service Manual or service-based
One line item on the invoice, many services behind it 1 Each service at its operational count Manual fixed price
Price should reflect the actual components 1 or the sellable unit Each service at its operational count Set based on included services