--- sourceDocument: Xanadu Sales Customer Relationship Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/order-management Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu Sales Customer Relationship Management ft:clusterId : - omgmt bundleId : - omgmt workflow : - Customer and Industry --- # Create a service specification for a remote catalog item # Create a service specification for a remote catalog item {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Create a service specification on a Service Exchange provider instance. When you publish the service specification, a remote record producer creates the remote catalog item for the service specification. ## Before you begin Define the characteristics, characteristic options, and specification categories before you create a service specification. Role required: sn_prd_pm.product_catalog_admin or sn_prd_pm.product_catalog_manager ## About this task When you create a service specification for a service request, use the Distribution channel field to set the channel to Service Exchange. When the service specification is published, a remote record producer is created for the specification. ## Procedure 1. In the CSM Configurable Workspace, select the List ![]() view. 2. Navigate to SpecificationsService specifications and select New. On the Details tab, fill in the form.{#create-sb-service-specs__table_p3t_cxq_4nb__entry__2} | Field | Description | |-|-| | Number | Auto-generated ID for the service specification. | | Name | Name of the service specification. | | Version | Version number that is assigned to a specification: * When you create the initial version, 1 appears in this field, and can't be changed. * When you create subsequent versions of the specification, the next incremental number appears in this field after you select Create New Version. For example, 4 appears in this field if 3 was the previous version number. {#create-sb-service-specs__ul_emb_m5j_bcc} | | Display name | Display name that appears for the specification when this version of the specification is in effect. * When you create the initial, or base version of the specification (for example, version 1), you must enter free-form text, which is usually the name of the specification, into the field. * When you create versions of the specification, a system-assigned concatenation of the specification name and its current version number appears, but can be overwritten. For example, SD-WAN Edge Device v2 appears in this field when: * SD-WAN Edge Device is the name of the specification. * Version 2 is the current version of the specification. {#create-sb-service-specs__ul_ft3_gvj_bcc} {#create-sb-service-specs__ul_xt4_dvj_bcc} | | Category | Specification category that the service specification belongs to. * If the selected category that belongs to 5G services doesn't have any matching slice templates, the system checks for existing templates. * If the selected category has multiple templates mapped to it, the systems chooses the latest published template to the specification. {#create-sb-service-specs__ul_ogf_g2x_txb} | | Type | Type of service specification: Customer Facing : Customers can create a ticket or a case for the service. When you select this type, the Distribution channel field is displayed to specify how the service is provided. Note: If you're using Service Exchange Order Management for Providers, only Customer Facing Service specifications are eligible for remote catalog creation. Service Exchange must be specified as the distribution channel so that remote record producers can be created. Resource Facing : Services are required for a resource to function properly. Not Applicable : Service specification is not customer facing or resource facing. | | Sub type | Sub-type of the specification. Choose Slice to define 5G network service specifications. Note: * When you select Slice as the sub type, the templates are automatically selected based on the mapping of templates with the specification categories of service specifications in the decision table. * If you select None as the sub type, you can manually specify a template. {#create-sb-service-specs__ul_d4d_yfx_txb} | | Start date | Date that the specification is valid from. Use this field when you create a version to indicate when it takes effect. It's informational only and isn't used for actual processing. | | End date | Date up until which the specification is valid. Use this field when you create a version to indicate when it's no longer in effect. It is informational only and isn't used for actual processing. | | Template | Templates that you've defined if you're using 5G services. Note: When you change a template, it deletes all the specification characteristics that are marked as true and are associated with the old template and re-associates the specification characteristics as per the new template that you've selected. | | Description | Description for the service specification. | | State | State of the service specification. Draft : Unpublished draft service specification that is assigned when you first create the specification record. Published : Published service specification that is assigned when you formally publish it for use in a product offering. Retired : Service specification that is retired and can no longer be used to create another specification version. Archived : Service specification is no longer used in the ordering or fulfillment process. | | Distribution channel | Option to set and lock in a distribution channel. For example, you can specify web as a channel. You can specify multiple channels. Note: If you're using the Service Exchange Order Management for Providers application and have a customer facing specification, enter Service Exchange as the distribution channel so that remote record producers can be created for remote catalog creation. | | External code | Service code of the specification. | | Line | Service line of the specification. | | Cost to company | Cost to the company for this service specification. This field is for profit-calculation purposes only. | | Composite | Option indicating that the service specification is a parent specification composed of multiple child specifications. | | Installation required | Option indicating that someone must install the service on site. | | Location specific | Option indicating that this service specification requires the location details for fulfillment and installation. | | Initial version | Name of the base version of the specification that appears but can't be changed. | | Previous version | Name of the previous version of the specification. For example: * When you create the initial version of the specification (for example, version 1), this field is empty. * When you create a version (version 2) with a slightly different name, the name of the specification at its initial creation appears here. * When you create a subsequent version (version 3), the name of the specification as it was at version 2 appears here. {#create-sb-service-specs__ul_dqp_gwj_bcc}You can't change this field. | [Table 1. Service Specification] {#create-sb-service-specs__table_p3t_cxq_4nb} 3. Select Save and then Publish. A remote record producer creates the remote catalog item for the specification. ## What to do next [Associate consumer criteria to a remote record producer](https://servicenow-prod.fluidtopics.net/XSZJJkMhKDe~hS_8e9xnUg "In the provider instance, associate the appropriate consumer criteria to the remote record producer created for a remote catalog item. The consumer criteria determines which consumers are entitled to the catalog item. Service Exchange automatically generates the entitlement records that are replicated to eligible consumer instances.") for this remote catalog item. *[\>]: and then