---
schema_version: "1"
id: e09495c82fc960af5b356d873755d17ace2cbd89a3ccbf215f79a6648d8341c2
title: Plan Your Service Catalog Implementation
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/aps_claims_catalog_plan_service_catalog_implementation.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.aps_claims_catalog_plan_service_catalog_implementation.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f235260bec3392de5c8f24754e9dc0b34f8524c0dc94d643c4e52ef32839b90a
description: Plan how your agency identifies, organizes, describes, and prices services before creating or importing catalog records.
products:
  - Public Sector
release: "264"
---
# Plan Your Service Catalog Implementation

Plan how your agency identifies, organizes, describes, and prices services before creating or importing catalog records.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=ind.psc_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions, user interfaces, and add-ons that support Public Sector.">View supported product editions</a>.</td></tr></tbody></table>

Identify the programs, benefits, providers, contracts, and business processes that use the catalog. Document how catalog data is used in service authorization, service delivery, claims, invoices, and payments.

Use an existing government or industry service code when one meets the agency's requirements. Otherwise, establish a consistent coding convention. Don't reuse a service code after retiring a service.

Create one reusable product for a service rather than duplicating the service for each catalog, provider, benefit, or fee schedule. Decide where to store each type of information:

- Use product fields for the service's identity and description.
- Use attributes for reusable service characteristics.
- Use catalogs and categories to organize services.
- Use price books and price book entries to maintain fee schedules and rates.
- Use Benefit Product records to associate services with benefits.
- Use Provider Product records to associate services with providers.

## Plan Product Catalogs and Categories

Group services by agency, program, service domain, funding source, or another business purpose. Use categories and subcategories only when they help users find services or support reporting requirements.

Use distinct and predictable category names, and don't create duplicate categories for the same business concept. A service can belong to multiple catalogs or categories, so reuse the same service product and create the required category assignments.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-public_sector_solutions-264-0-0-production-enus/25746429-1b1c-4bf3-b014-cf92f9531212/images/icon_note.png)

Note Catalog and category assignments organize services but don’t determine service eligibility, benefit coverage, or rates. Use Provider Product records to specify which services a provider can deliver, Benefit Product records to specify which services a benefit covers, and price books and price book entries to define applicable rates.

## Plan Service Attributes and Classifications

Use attributes to define service characteristics that Salesforce admins manage consistently. Examples include delivery type, service setting, and service duration. Group related attributes into attribute categories, and use product classifications when groups of services share a common set of attributes.

Create an attribute only when the information isn’t already stored in a product field or represented by a Salesforce relationship. Select the appropriate data type for each attribute.

If an attribute changes a service's price, determine whether your enabled pricing capabilities support attribute-based pricing. Mark an attribute as price-impacting only when the pricing process uses it.

## Plan Standard and Negotiated Fee Schedules

Use price books to represent fee schedules and price book entries to associate services with rates. Before creating fee schedules, document how the agency selects the applicable schedule and rate.

- Use a standard fee schedule for default rates established by an agency or governing authority.
- Use a separate negotiated fee schedule for rates established through a provider contract or another agreement.

#### See Also

- [Catalog & Pricing in Public Sector](https://help.salesforce.com/s/articleView?id=ind.aps_claims_catalog_catalog_services_and_pricing_overview.htm&release=264.0.0&type=5 "Use Catalog &Pricing to define and organize agency services, maintain standard and negotiated rates, and associate services with benefits and providers.")
- [Import Service Catalog Data](https://help.salesforce.com/s/articleView?id=ind.aps_claims_catalog_import_service_catalog_data.htm&release=264.0.0&type=5 "Use Catalog & Pricing templates to import your service catalog data. Import records in dependency order so that referenced records exist before records that depend on them.")
- [Plan Your Product Catalog](https://help.salesforce.com/s/articleView?id=ind.product_catalog_plan_catalog.htm&type=5&language=en_US)
- [Organize Your Products with Catalogs and Categories](https://help.salesforce.com/s/articleView?id=ind.product_catalog_catalogs.htm&language=en_US)