---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Product catalog forms

# Product catalog forms {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 16 Minuten Lesedauer

The product catalog forms enable you to create and publish product offerings so that your customers can order the products or services that they require.

## Characteristics form fields {#ariaid-title2}

The Characteristics form enables you to create characteristics and characteristic options.
{#fields-characteristics-form__table_qrh_qrq_4nb__entry__2}

| Field | Description |
|-|-|
| Name | Name of the characteristic. |
| Description | Description of the characteristic. |
| Input Type | Type of input for this characteristic. Address :   Input for the entry of an address. Attachment :   Input for the attachment of an external document. CheckBox :   Option that you select or clear. Choice :   Options that you choose for the characteristic. If you select Choice, you can define options for the characteristic in the Characteristic Options related list. Hinweis: The SD-WAN Offering characteristics and characteristics are not part of the base system. Define your own characteristics and options for the SD-WAN Offering according to your requirements. Date :   Input for the entry of a date. Date/time :   Input for the entry of a date and time of day. Duration :   Input for the entry of a duration of time. Email :   Input for the entry of an email address. Label :   Input for the selection that enables the production of a label. Single Line Text :   Input for the free-form entry of a single line of text. Yes/No :   Input that requires the selection of a Yes/No response. |
[ ]

{#fields-characteristics-form__table_qrh_qrq_4nb}

## Decomposition rules fields {#ariaid-title3}

The Decomposition Rules form enables you to create a decomposition rule that excludes the service specification when a customer does not select a specific option.
{#fields-decomposition-rules__table_ytw_wcr_4nb__entry__2}

| Field | Description |
|-|-|
| Characteristic | Product characteristic that the customer does not order that triggers the exclusion rule. You can select a characteristic that is associated with the product to trigger this exclusion. For example, if you select a routing characteristic for an SD-WAN product, the exclusion rule triggers if the customer does not order a routing characteristic. |
| Characteristic Option | Product characteristic option that the customer does not order that triggers the exclusion rule. * Select the option that is associated with the product. * Selecting an option makes the exclusion rule even more granular than if you had selected a characteristic only.For example, if you select a specific Routing characteristic option for an SD-WAN product, the exclusion rule triggers only if the customer does not order that option. If they select any other Routing option, it does not trigger the exclusion rule. {#fields-decomposition-rules__ul_xkl_fdh_t4b} |
| Source Specification | Source specification that you associate with the target specification in the selected specification relationship record. |
| Target Specification | Target specification that you associate the source specification with in the selected specification relationship record. |
[ ]

{#fields-decomposition-rules__table_ytw_wcr_4nb}

## Product offerings form fields {#ariaid-title4}

You can use the Product Offerings form to create and publish product offerings to a product catalog.
{#fields-product-offerings-form__table_product_offerings__entry__2}

| Field | Description |
|-|-|
| Number | ID of the product offering. |
| Name | Name of the product offering. |
| Version | Version number that is assigned to the product offering: * When you create the initial version, 1 appears in this field and can't be changed. * When you create subsequent versions of the product offering, the next incremental number appears in this field after you click Create New Version. For example, 4 appears in this field if 3 was the previous version number {#fields-product-offerings-form__ul_vtt_5l4_2tb} |
| Display Name | Displayed name that appears for the product offering in the ServiceNow AI Platform when this version of the product offering is in effect. * When you create the initial, or base version of the product offering (for example, version 1), you must enter free-form text, which is usually the name of the product offering, into the field. * When you create versions of the product offering, a system-assigned concatenation of the product offering 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 product offering. * Version 2 is the current version of the product offering. {#fields-product-offerings-form__ul_tr3_gmv_2tb} {#fields-product-offerings-form__ul_sr3_gmv_2tb} |
| Product Specification | Product specification to associate with the product offering. Hinweis: Only published specifications appear. |
| Contract Term | Term length of the contract |
| Monthly Recurring Charges | Monthly recurring charges for the contract, if any. |
| Non Recurring Charges | Any one-time fees for the contract, if any. |
| Description | Description of the product offering. |
| Offering Catalog | Offering catalog to add the product offering to. After you associate the product offering to a customer contract, the offering catalog is published to the customer instance. It appears as a category in the service catalog on the customer's self-service portal. |
| Distribution Channel | Distribution channel for the product offering. |
| Start Date | Date that the product offering is valid from. You can use this field when you create a version to indicate when it takes effect. However, it is informational only and is not used for actual processing. |
| End Date | Date up until which the product offering is valid. You can use this field when you create a version to indicate when it is no longer in effect. However, it is informational only and is not used for actual processing. |
| Description | Description of the product offering. |
| Initial Version | Name of the product offering at the time you created the initial version. You can't change this field. |
| Previous Version | Name of the previous version of the product offering. For example: * When you create the initial version of the product offering (for example, version 1), this field is empty. * When you create a version (version 2) with a slightly different name, the name of the product offering at its initial creation appears here. * When you create a subsequent version (version 3), the name of the product offering as it was at version 2 appears here. {#fields-product-offerings-form__ul_ytt_5l4_2tb}You can't change this field. |
[ ]

{#fields-product-offerings-form__table_product_offerings}

## Product specifications form fields {#ariaid-title5}

The Product Specifications form enables you to create and publish a product specification to define all the products options that apply to a
product.
{#fields-product-specifications-form__table_pyl_fvq_4nb__entry__2}{#fields-product-specifications-form__form-field-composite-desc2}

| Field | Description |
|-|-|
| Number | Auto-generated ID for the product specification. |
| Name | Name of the product 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 click Create New Version. For example, 4 appears in this field if 3 was the previous version number. {#fields-product-specifications-form__ul_fld_dlf_2tb} |
| Display Name | Displayed name that appears for the specification in the ServiceNow AI Platform 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. {#fields-product-specifications-form__ul_sx4_bss_2tb} {#fields-product-specifications-form__ul_rx4_bss_2tb} |
| Category | Specification category to which the product specification belongs. |
| Type | Type of product specification. Goods :   Product specification for the type of goods that you sell. Service :   Product specification of a service that you sell or provide to your customer. Network :   Product specification of a network. |
| Start Date | Date that the specification is valid from. You can use this field when you create a version to indicate when it takes effect. However, it is informational only and is not used for actual processing. |
| End Date | Date up until which the specification is valid. You can use this field when you create a version to indicate when it is no longer in effect. However, it is informational only and is not used for actual processing. |
| Owner | Name of the person who is responsible for maintaining this specification. Click the search icon (![Search icon.]()) to select the person. |
| Description | Description of the product specification. |
| State | State of the product specification. Draft :   Unpublished draft product specification that is assigned when you first create the specification record. Published :   Published product specification that is assigned when you formally publish it for use in a product offering. Retired :   Product specification that is retired and can no longer be used to create another specification version. Archived :   Product specification is no longer used in the ordering or fulfillment process. |
| Code | Product code of the specification. |
| Line | Product line of the specification. |
| Cost to Company | Cost to the company for this product specification. This field is for profit-calculation purposes only. |
| Composite | Option that designates that the product specification is a complex enterprise product specification. A composite product is typically comprised of a parent or umbrella specification, and multiple child specifications, each with their own characteristics. When bundled together, they constitute a single complex product. |
| Installation required | Option that designates that someone must install the product on site. |
| Location Specific | Option that designates that this product specification requires that you enter the location details into a customer order 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. {#fields-product-specifications-form__ul_dmc_zjc_dtb}You can't change this field. |
[ ]

{#fields-product-specifications-form__table_pyl_fvq_4nb}

## Resource specifications form fields {#ariaid-title6}

You can use the Resource Specifications form to create and publish a resource specification to define all the resource options that apply to a telecommunications product.
{#fields-resource-specifications-form__table_pyl_fvq_4nb__entry__2}

| Field | Description |
|-|-|
| Number | Auto-generated ID for the resource specification. |
| Name | Name of the resource 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 click Create New Version. For example, 4 appears in this field if 3 was the previous version number. {#fields-resource-specifications-form__ul_fld_dlf_2tb} |
| Display Name | Displayed name that appears for the specification in the ServiceNow AI Platform 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. {#fields-resource-specifications-form__ul_sx4_bss_2tb} {#fields-resource-specifications-form__ul_rx4_bss_2tb} |
| Category | Specification category that the resource specification belongs to. |
| Type | Type of resource specification: Physical :   Physical item, such as a router or a handset. Logical :   Logical item, such as an IP address. |
| Start Date | Date that the specification is valid from. You can use this field when you create a version to indicate when it takes effect. However, it is informational only and is not used for actual processing. |
| End Date | Date up until which the specification is valid. You can use this field when you create a version to indicate when it is no longer in effect. However, it is informational only and is not used for actual processing. |
| Owner | Name of the person who is responsible for maintaining this specification. Click the search icon (![Search icon.]()) to select the person. |
| Description | Description for the resource specification. |
| State | State of the resource specification. Draft :   Unpublished draft resource specification that is assigned when you first create the specification record. Published :   Published resource specification that is assigned when you formally publish it for use in a product offering. Retired :   Resource specification that is retired and can no longer be used to create another specification version. Archived :   Resource specification that is no longer used in the ordering or fulfillment process. |
| Product Model | Product model of the specification. |
| Cost to Company | Cost to the company for this resource specification. This field is for profit-calculation purposes only. |
| Composite | Option that designates that the resource specification is a parent that contains multiple child specifications. |
| Installation required | Option that designates that someone must install the product on site. |
| Location Specific | Option that designates that this resource 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. {#fields-resource-specifications-form__ul_dmc_zjc_dtb}You can't change this field. |
[ ]

{#fields-resource-specifications-form__table_pyl_fvq_4nb}

## Service specifications form fields {#ariaid-title7}

The Service specifications form enables you to create and publish a service specification to define all the service options that apply to a telecommunications product.
{#fields-service-specifications-form__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 click Create New Version. For example, 4 appears in this field if 3 was the previous version number. {#fields-service-specifications-form__ul_fld_dlf_2tb} |
| Display Name | Displayed name that appears for the specification in the ServiceNow AI Platform 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. {#fields-service-specifications-form__ul_sx4_bss_2tb} {#fields-service-specifications-form__ul_rx4_bss_2tb} |
| Category | Specification category that the service specification belongs to. * If the selected category that belongs to 5G services, doesn't have any matching slice template, 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. {#fields-service-specifications-form__ul_ogf_g2x_txb} |
| Type | Type of service specification. Customer Facing :   Customers can create a ticket or a case for the service. 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. Hinweis: * When you select the sub type to Slice, 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 the sub type to None, you can manually select a template. {#fields-service-specifications-form__ul_d4d_yfx_txb} |
| Start Date | Date that the specification is valid from. You can use this field when you create a version to indicate when it takes effect. However, it is informational only and is not used for actual processing. |
| End Date | Date up until which the specification is valid. You can use this field when you create a version to indicate when it is no longer in effect. However, it is informational only and is not used for actual processing. |
| Template | Templates that you've defined for the 5G services. Hinweis: 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. |
| Owner | Name of the person who is responsible for maintaining this specification. Click the search icon (![Search icon.]()) to select the person. |
| 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. |
| 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 that designates that the service specification is a parent specification composed of multiple child specifications. |
| Installation required | Option that designates that someone must install the service on site. |
| Location Specific | Option that designates 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. {#fields-service-specifications-form__ul_dmc_zjc_dtb}You can't change this field. |
[ ]

{#fields-service-specifications-form__table_p3t_cxq_4nb}

## Specification Relationships related list fields {#ariaid-title8}

The Specification Relationships form enables you to create specification relationships and optional decomposition rules.
{#fields-specification-relationships-related-list__table_ytw_wcr_4nb__entry__2}

| Field | Description |
|-|-|
| Source specification | Product, service, or resource specification that you create the relationship from. For example, the source specification could be a product specification for an SD-WAN. |
| Target type | Type of specification. To learn more, see [Product catalog data model and catalog versioning](https://servicenow-prod.fluidtopics.net/cgdmqs8Lvt8aShp_YUbCaA#order-mgt-product-data-model "Technical product catalogs have a framework for defining the technical products, services, and resources that you want to sell to your customers."). |
| Target specification | Specification that you create the relationship to. For example, the target specification could be a service specification for an SD-WAN. Hinweis: The target product, service, or resource specification you select can be in any state, including a Draft state. The selected specification does not have to be published before selecting it in this field. |
| Mandatory | Option that designates if the relationship between the selected source and target specifications is mandatory and should always exist when a customer orders the product. * If selected, the target specification is always included with the source specification. During the ordering process, you must select the characteristics and characteristic values for the target specification. For example, if you are defining an SD-WAN Service Package, you designate that the SD-WAN Edge Device and SD-WAN Controller target specifications are mandatory. * If cleared, it is an optional target specification and is only included with the product if the customer selected it during the ordering process. For example, if you designate that the SD-WAN Security specification is optional, it's included in an ordered SD-WAN Service Package only if the customer selected it during the ordering process. {#fields-specification-relationships-related-list__ul_c4s_4xl_s4b} |
| Relationship type | Type of relationship that designates how an order that contains the source specification decomposes for fulfillment after you receive and approve it. Composed of :   Source specification that is composed of the selected target specification. An order that contains the source specification and characteristics decompose into a single service order. Realized as :   Source specification that is realized as the selected target specification. Bundles :   Source specification bundles as the selected target specification. An order that contains the source specification and characteristics decompose into unique order line items for each of the target specifications bundled from that parent product specification. Requires :   Source specification that requires the selected target specification. To enable the delivery of the promised services within the specification, an order that contains the source specification and characteristics also requires the target resource specification. |
| Order |   |
| Minimum quantity | Required minimum number of specifications for an order. |
| Default quantity | Default quantity if there is no selected amount. |
| Maximum quantity | Maximum quantity of specifications. |
| Quantity characteristic | Source specification characteristic that is used for quantity mapping. The quantity characteristic is supported only for a specification relationship in a product specification. |
[Tabelle : 1. Specification Relationship form]

{#fields-specification-relationships-related-list__table_ytw_wcr_4nb}