You are here:
Plan Your Service Catalog Implementation
Plan how your agency identifies, organizes, describes, and prices services before creating or importing catalog records.
Required Editions
| View supported product editions. |
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.
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.
