Teams getting started with Revenue Cloud Advanced (RCA) typically begin with setting up and deploying their first product bundle. While we're developing a tailored solution for RCA metadata, data deployment currently offers the most reliable way to deploy these bundles between environments.

What is a Product Bundle in RCA?

In Revenue Cloud Advanced (RCA), a product bundle isn't just a single item; it's a collection of interconnected components that define what's being sold. Here's a breakdown of what it typically contains:

Product (Root): This is the main product that represents the bundle itself. It's the core around which the other components are organized.
Product Configuration: This defines how the bundle can be set up or customized. It might include rules about which options are available, required, or compatible.
Product Option Groups: These organize the available choices within the bundle. For example, a computer bundle might have option groups for "Processor," "Memory," and "Storage."
Product Options: These are the specific choices within each option group. For instance, under the "Processor" group, you might have options like "Intel Core i5" or "AMD Ryzen 7."
Product Attributes: These are characteristics or properties of the products within the bundle, which might influence pricing, configuration, or display.
Expression Sets: These are sets of rules or logic that control how the bundle behaves, often dynamically. For example, an expression set might determine which options are displayed based on other selections.

In simpler terms, an RCA product bundle is a structured way of packaging multiple products and options together, with rules and logic to manage how they are configured and sold.

These components are stored as Custom objects, not standard Salesforce metadata, which is why data deployment is the best option for now.

Prerequisites

Before starting, make sure:

You’ve identified the root product of the bundle in your source org.
Your target org has any necessary metadata pre-deployed (like Custom fields or object definitions).
Data deployment is enabled. Here’s how you can check.

Step-by-step deployment

If you're new to Gearset's data deployment tool, we recommend starting with this guide to running your first data deployment, which walks through the basics of the UI and configuration.

Once you're familiar with the tool, follow the steps below to deploy your RCA product bundle:

1. Open the Data Deployment tool

In Gearset, go to Data deployment from the left-hand menu.
Click "Configure data deployment".
Select your source org and target org.
Click "Configure deployment".

2. Build your deployment plan

Start with the root product for the bundle:

Select the object: Product2 (or your RCA-specific custom product object).
Optionally, use filters to narrow down the product records — for example, by product name or type. If no filters are applied, Gearset will include all matching records from the source org.
On the next screen, Gearset will show the reference fields on Product2. These represent relationships to other objects (e.g. Seller, TaxPolicy, UnitOfMeasure).

You can also add additional objects to the deployment plan — for example, PricebookEntry if you want to include pricing information for your products.

When you're done configuring objects, click Next to continue selecting related objects and deployment methods.

3. Select Related Objects and Deployment Methods

In this step, you'll configure how records should be matched and which related objects to include in your deployment.

1. Match existing records.

For each object (like Product2 and PricebookEntry), choose how Gearset should match records in the target org.

Use unique, stable fields like ProductCode for Product2.
For PricebookEntry, consider combining fields like ProductCode, Pricebook2.Name, and Pricebook2.IsActive.

2. Include related objects.

Gearset lists related objects that can be included in the deployment. For each one, you can configure:

Whether to include it
The deployment method (upsert, look up existing, or create new)
Matching fields for alignment in the target org

Common related objects may include:

Pricebook2
Seller
ProductClassification
RecordType
User
ProductSellingModel, TaxPolicy, and others depending on your bundle structure

Note: Objects like User and RecordType cannot be deployed via data deployment. Instead, use the look up existing records method to reference the matching records in the target org.

Once you're done configuring related objects and matching rules, click Next to continue.

4. Configure Data Masking

Please note that RLM specifics objects are not available for masking and this below guidance is for other objects.

If you're deploying to a sandbox or lower environment, you can choose to mask sensitive data in this step. This is especially useful when working with personally identifiable information (PII) or production-like data. Learn more about data masking.

On this screen, you can:

Mask fields by type — e.g., mask all address or name fields.
Mask fields individually — select specific fields to obfuscate (e.g., FirstName, LegalEntityStreet).
Preview sample outputs — Gearset shows examples of how data will be masked.

Gearset won't let you mask data if the target is a production org, to help avoid costly deployment mistakes.

When you're ready, click Next to move on to the deployment summary.

5. Review and deploy

The final step shows a full summary of the data deployment plan:

All selected objects and fields
Record counts
Fetch and matching behavior
Deployment actions (e.g., create, update, fetch from target)

Use this screen to review everything before you proceed.

You can also:

Save your plan as a template for future reuse
Go back to previous steps if you need to adjust anything

When you’re ready, click Deploy data to begin the deployment. For a detailed walkthrough of this step, see our documentation on deploying the data records (this section is part of a wider article on running your first data deployment).

Post-deployment checklist

After deploying:

Open the product in your target org to confirm its structure and options.
Once you've finished your data deployment, you can re-enable the rules, triggers and flows by selecting Rollback deactivation deployments via the deployment summary:
Run tests to verify pricing logic, if expressions were included.
Adjust any org-specific values that aren’t portable (e.g., RecordTypes).

Known Limitations

Some reference fields (e.g., User, RecordType, ProductSellingModel) can’t be upserted and must exist in the target org already. Gearset will flag these during setup.

RecordType IDs are org-specific, so matching on developer name is recommended.

For other data deployment limitations please refer this document.