---
schema_version: "1"
id: ea33e3a56f37e6b229c1c469119c83b9ccce1700b20ee5c00bfec17eb03f1eb8
title: Billing Considerations for Salesforce Catalog
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_salesforce_catalog_billing_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_salesforce_catalog_billing_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bd1e0c7989a94e4a19fcc1c85d26881e758b628d6238357ee16425572c0d0b35
description: When you use Salesforce Catalog, you process unstructured data and search index configurations in Data 360. Use of Salesforce Catalog with Data 360 impacts the consumption of credits in these usage types.
products:
  - Data 360
release: "264"
---
# Billing Considerations for Salesforce Catalog

When you use Salesforce Catalog, you process unstructured data and search index configurations in Data 360. Use of Salesforce Catalog with Data 360 impacts the consumption of credits in these usage types.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note When you enable and access Salesforce Catalog through the Metadata Grounding Model Context Protocol (MCP) server in pre-production orgs such as Developer Edition, Sandbox (all its variations), and Preview orgs, Data 360 usage isn’t billed. Production orgs are billed for all Data 360 usage.

Use Digital Wallet to check which consumption cards are active in your org, find out how many credits are available on each card, and determine how many credits have been consumed in each usage type.

Some usage types aren’t metered for certain licenses or editions, such as a Data 360 Profiles license or Agentforce 1 Edition. Check your licenses and review license documentation for more information.

Unstructured data processing features such as search index are not available for orgs operating Data 360 under the Customer Data Platform (CDP) license.

## Data 360 Usage

When you use Data 360 for data collection and processing, your org consumes credits from either the Data Services consumption card or the Flex Credits consumption card.

- If your contract included Data Service Credits, those are consumed for all Data 360 usage.
- If you run out of Data Service Credits, your org is billed at your Data Service Credit overage rate for the remainder of your term unless more credits are added.
- If you have Flex Credits for Data 360, those credits are consumed instead.

Data Services and Flex Credits organize data services within different usage type groupings. For more information, see [Data Services Billable Usage Types for Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_data_usage_types.htm&type=5&language=en_US) and [Flex Credits Usage Types for Data 360](https://help.salesforce.com/s/articleView?id=data.c360_a_flex_credits_for_data360.htm&type=5&language=en_US). To check multipliers for each usage type, see the [Multipliers for Data Services Rate Card](https://www.salesforce.com/data/rates/multipliers/) or the [Agentforce & Data 360 Flex Credits Rate Card](https://www.salesforce.com/agentforce/rates/). The cost of each credit is determined by your contract.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:16.666666666666664%">
          <col style="width:16.666666666666664%">
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d206295e125">Digital Wallet Card Consumption Card</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d206295e128">Usage Type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d206295e131">Usage Type Description</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d206295e134">Notes</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Digital Wallet Card Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e125 "><span>Data Services</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e128 ">Unstructured Data Processed</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e131 ">
              <p>Usage is calculated based on the amount
                of unstructured data that is processed without using AI assisted content processing and
                extraction. For example, if the search index processes 100 PDF documents that are 1 MB each,
                usage is calculated as 100 MB. If the search index processes five audio/video files that are
                on average 100MB each, usage is calculated as 500MB. </p>
              <p>In Data 360, unstructured data may
                be chunked and vectorized using an embedding model. Usage is computed only once across both
                these activities. For example, if one 100 MB PDF document is chunked and vectorized, usage
                is computed as 100 MB, not as 200MB.</p>
              <p style="margin-bottom:0;">If you create a search index that uses a data
                model object (DMO) as a data source and select Text data type fields from the DMO, all
                strings from those fields are indexed and the sum total of all bytes processed is reported
                as Unstructured Data Processed.</p>
            </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e134 ">
              <p>In Data 360, unstructured data may be chunked and vectorized using an embedding
                model. Usage is computed only once across all these activities. For example, if
                one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB,
                not as 200MB. </p>
              <p style="margin-bottom:0;">The cost of creating a search index remains the same for vector search index and
                hybrid search index.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Card Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e125 "><span>Flex Credits</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e128 ">Data 360 Unstructured Processing</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e131 ">
              <p>Usage is calculated based on the amount of unstructured data that is processed
                without using AI assisted content processing and extraction. For example, if the search
                index processes 100 PDF documents that are 1 MB each, usage is calculated as 100 MB. If the
                search index processes five audio/video files that are on average 100MB each, usage is
                calculated as 500MB.</p>
              <p style="margin-bottom:0;">In Data Cloud, unstructured data may be chunked and vectorized
                using an embedding model. Usage is computed only once across both these activities. For
                example, if one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB,
                not as 200MB.If you create a search index that uses a data model object (DMO) as a data
                source and select Text data type fields from the DMO, all strings from those fields are
                indexed and the sum total of all bytes processed is reported as Unstructured Data
                Processed.</p>
            </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e134 ">
              <p>In Data 360, unstructured data may be chunked and vectorized using an embedding
                model. Usage is computed only once across all these activities. For example, if
                one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB,
                not as 200MB. </p>
              <p style="margin-bottom:0;">The cost of creating a search index remains the same for vector search index and
                hybrid search index.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Card Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e125 "><span>Data Services</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e128 ">Data Queries</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e131 ">
              <p>Usage is calculated based on the number of records
                processed. </p>
              <p style="margin-bottom:0;">The count of records processed depends on the structure of a query as well as
                other related factors such as the total number of records in the objects being
                queried.</p>
            </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e134 ">
              <p style="margin-bottom:0;">For hybrid search queries against unstructured data, the number of vectors and
                keyword records in the search index are counted. In a typical search index, the
                number of keyword records is the same as the number of vectors.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Digital Wallet Card Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e125 "><span>Flex Credits</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e128 ">Data 360 Queries</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e131 ">
              <p>Usage is calculated based on the number of records processed. </p>
              <p>The count of records processed depends on the structure of a query as well as other
                related factors such as the total number of records in the objects being queried.</p>
              <p style="margin-bottom:0;">When an object is queried in the context of a data space, the number of rows processed is
                based on the total number of processed rows in the source object, not the number of rows
                pertaining to the particular data space</p>
            </td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e134 ">
              <p style="margin-bottom:0;">For hybrid search queries against unstructured data, the number of vectors and
                keyword records in the search index are counted. In a typical search index, the
                number of keyword records is the same as the number of vectors.</p>
            </td>

          </tr>
        </tbody>
      </table>

## Data 360 Storage Usage

Storage costs are determined by your contract. Use Digital Wallet to check your current usage.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:16.666666666666664%">
          <col style="width:16.666666666666664%">
          <col style="width:33.33333333333333%">
          <col style="width:33.33333333333333%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d206295e274">Digital Wallet Consumption Card</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d206295e277">Usage Type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d206295e280">Usage Type Description</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d206295e283">Notes</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Digital Wallet Consumption Card" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e274 "><span>Data Storage</span></td>

            <td data-label="Usage Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e277 ">Storage Beyond Allocation</td>

            <td data-label="Usage Type Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e280 ">Usage is calculated based on the amount of
              storage used above the amount allocated.</td>

            <td data-label="Notes" class="slds-cell-wrap" style="vertical-align:top;" headers="d206295e283 ">
              <p style="margin-bottom:0;">Every file ingested and table created, including unstructured data lake objects
                (UDLO), unstructured data model objects (UDMO), CDMO, or index data model objects
                (index DMO), count toward Data 360 data storage, such as, the chunk and index DMOs
                generated when vector or hybrid search indexes are created.</p>
            </td>

          </tr>
        </tbody>
      </table>