Set Up a Consumption-Based Product

Learning Objectives

After completing this unit, you’ll be able to:

• Recap the five key components of Usage Management.
  
• Sign up for a special Developer Edition org for Agentforce Revenue Management.
  
• Identify the different usage model types.
  
• Configure a consumption-based product.
  

Before You Start

Before you start this module, make sure you complete this content. The work you do here builds on the concepts and work you do in that content.

• Agentforce Revenue Management Foundations
  
• Usage Management Foundations
  

Also, consider completing the following recommended content.

• Efficient Sales with Agentforce Revenue Management
  

Revenue Cloud is now called Agentforce Revenue Management. You might see references to Revenue Cloud in our application and documentation.

A Quick Recap

In the Usage Management Foundations badge, you learned that consumption-based pricing is changing how companies buy and sell software and services. Unlike a traditional subscription where you pay a flat fee regardless of usage, consumption-based pricing means you pay only for what you use. This model gives you flexibility and control. It’s ideal for products where usage volume is unpredictable, such as data storage, compute power, or API calls.

You also learned about the Usage Management capability and its five key components.

• Usage Modeling: Define your consumption-based products and the resources they use.
  
• Rate Management: Set up pricing, including consumption tiers.
  
• Usage Selling: Configure your sales process to generate accurate quotes and orders for customers.
  
• Wallet Management: Create wallets for each purchased usage resource and provide a dashboard to track them by account.
  
• Consumption Management: Track customer usage, manage grants, and generate invoice-ready summaries.
  

Now, it's time to turn that knowledge into practice. In this badge, you implement Usage Management by working with the first three components: Usage Modeling, Rate Management, and Usage Selling.

But before you dive into the details, start by setting up your own Salesforce org.

Sign Up for a Developer Edition Org with Agentforce Revenue Management

To complete this badge, you need a special Developer Edition org that contains Agentforce Revenue Management and our sample data. Get the free Developer Edition and connect it to Trailhead now so you can complete the challenges in this module. Note that this Developer Edition is designed to work with the challenges in this badge, and might not work for other badges. Always check that you’re using the Trailhead Playground or the special Developer Edition org that we recommend.

1. Sign up for a free Agentforce Revenue Management Developer Edition org.
   
2. Fill out the form.
   

• For Email, enter an active email address.
  
• For Username, enter a username that looks like an email address and is unique, but it doesn’t need to be a valid email account (for example, yourname@example.com).
  
• Your Developer Edition org uses USD as currency. So to pass all the challenges, it's important to specify the correct country. For Country, select United States.
  

3. After you fill out the form, click Sign me up. A confirmation message appears.
   
4. When you receive the activation email (this might take a few minutes), open it and click Verify Account.
   
5. Complete your registration by setting your password and answering the challenge question. Tip: Save your username, password, and login URL in a secure place—such as a password manager—for easy access later.
   
6. You’re logged in to your Developer Edition Org.
   

Now connect your new Developer Edition org to Trailhead.

1. Make sure you’re logged in to your Trailhead account.
   
2. In the Challenge section at the bottom of this page, click the playground name and then click Connect Org.
   
3. On the login screen, enter the username and password for the Developer Edition you just set up.
   
4. On the Allow Access? screen, click Allow.
   
5. On the Want to connect this org for hands-on challenges? screen, click Yes! Save it. You’re redirected back to the challenge page and ready to use your new Developer Edition to earn this badge.
   

A Business Scenario

Liam Hoko is the usage admin at InfinitraBytes, an electronic product and solution provider.

InfinitraBytes has recently adopted Agentforce Revenue Management, and Liam is focused on mastering its Usage Management capabilities to efficiently manage and track the company’s new consumption-based products. He understands the fundamentals of Usage Management, specifically, Units of Measure (UoMs), Usage Resources, and allocating free usage via Product Usage Grants.

Now, Liam's goal is to create a consumption-based product called the Cell Phone Plan that includes several distinct resources. To ensure InfinitraBytes charges customers fairly, the plan comes with a specified amount of included usage, or Product Usage Grants, for each resource.

Here are the specific requirements for the Cell Phone Plan product that Liam plans to implement.

Follow along Liam to configure this in your Developer Edition org. This critical work lays the foundation for accurate usage tracking and billing at InfinitraBytes. But first, briefly review the different usage model types in Revenue Management.

Explore Usage Model Types

A usage model type determines the fundamental role a product plays in a consumption-based model, such as whether the product itself is the core service, a minimum financial commitment, or a grant of prepaid units. This classification ensures Revenue Management processes and prices consumption records correctly.

Usage Management offers five usage model types to help define your consumption-based product. Start by looking at the two fundamental ones: Anchor and Pack.

• Anchor: Use Anchor for the main product or primary service that you're selling to a customer. For example, a customer buys a monthly subscription of InfinitraBytes cloud data warehouse service. Here, the subscription itself is the Anchor product as it grants the customer access to the platform.
  
• Pack: Use Pack for products and services that are add-ons providing additional, measurable units of usage resources. Always link a Pack to an Anchor product. For example, if InfinitraBytes data warehouse subscription, the Anchor product, includes 1 terabyte (TB) of storage, an additional 5 TB storage is the Pack product. Buying this product adds more consumable resources to the main service.
  

Next, the focus shifts to usage model types that involve customer commitment.

Discover Commitment Usage Model Types

Businesses often want predictability and better pricing, which is where commitment models come in. A commitment is an agreement where the customer promises a minimum level of spend or usage over a specific period. In exchange, the customer often receives a discounted rate. Here are the three commitment usage model types.

• Token Commitment: A Token Commitment is when your customer agrees to purchase a minimum number of virtual tokens. These tokens act as a form of pre-paid currency that they can spend across different products or services. This model offers maximum flexibility for how they use their pre-paid balance. For example, an InfinitraBytes customer purchases a token commitment of 50,000 tokens, and 1 token is equal to 10 API calls or 1 GB of archive storage. This offers the customer the flexibility to use the tokens across different services.
  

• Monetary Commitment: With a Monetary Commitment, customers agree to spend a minimum amount on a product or service. If they don't hit the minimum spend, they pay the difference anyway. If they spend more, the system bills them for the overage, often at a discounted rate. For example, an InfinitraBytes customer gets a 10% discount on all data processing fees in exchange for guaranteeing that they spend at least $25,000 on processing credits over a 12-month term.
  

• Quantity Commitment: A Quantity Commitment means the customers agree to use a minimum quantity of a specific product or resource. This commitment locks in a minimum usage level rather than a fixed monetary amount. For example, a company commits to using at least 1 million support case contact hours per year for InfinitraBytes customer service platform. The system bills the customer for this minimum quantity, even if their actual usage is only 800,000 hours.
  

In this unit, you focus on creating a consumption-based product that uses the Anchor usage model type.

Prepare Your Consumption-Based Product

Good News! Your Developer Edition org already contains the Cell Phone Plan product record. Your task here is to configure this product by setting its specific usage model type and validating that all essential selling models and pricing components are set up correctly.

To pass the challenges in this badge, make sure to set the Country to United States when signing up for your Developer Edition org.

Follow along with Liam in your Developer Edition org.

1. From the App Launcher, find and select Rate Management.
   
2. On the Rate Management home page, click the Products tile. Alternatively, click and select Products.
   

3. Click Recently Viewed and select All Products.
   
4. Under Product Name, select Cell Phone Plan.
   
5. Click Edit.
   
6. For the Usage Model Type field, select Anchor.
   

7. Save your changes.
   

Next, validate that this product has a selling model and price book entry defined.

1. On the Related tab, scroll to the Product Selling Model Option section.
   
2. Confirm that the Product Selling Model is set to Term Based - Monthly.
   

3. Now, scroll further to the Price Books section.
   
4. Here, confirm that the List Price is set to $100.
   

The Cell Phone Plan is set up as Term Based—Monthly with a $100 list price, so the customers pay a $100 monthly fee to access all the usage resources associated with this consumption-based product.

Up Next

In this unit, you successfully configured the Cell Phone Plan product to use the Anchor usage model type. You also validated its selling model and price book entry. In the next unit, you prepare for usage tracking by setting up the unit of measure and unit of measure classes needed for the product's usage resources. Stay tuned!

Resources

• Salesforce Help: Considerations for Creating Usage-Based Products
• Trailhead: Usage Management Foundations
• Trailhead: Product Catalog Management with Agentforce Revenue Management