--- sourceDocument: Australia Telecommunications, Media, and Technology sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-media-technology Release : - australia ft:locale : - en-US ft:publication_title : - Australia Telecommunications, Media, and Technology ft:clusterId : - telmt bundleId : - telmt workflow : - Customer and Industry --- # Product offering versions # Creating and publishing product offering versions {#ariaid-title1} Release version: Australia Updated April 16, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Creating and publishing product offering versions As a product catalog manager in ServiceNow, you can create and publish versions of product offerings by combining updated product, service, and resource specifications. Proper versioning ensures customer service agents have access to the latest offerings, enabling upselling of upgraded or complementary products to customers. Show full answer Show less ## Creating Versions of Product Offerings * Assign version numbers to affected product, service, or resource specifications and product offering records. * Edit relevant data to reflect engineering changes, including characteristics, options, and product specifications. * Define specification relationships, decomposition rules, and attribute mappings for each new version. * Create and publish the product offering version to update your product catalog. * Retire or archive outdated specifications and offerings to maintain catalog accuracy. ## Updates and Validations During Version Creation and Publishing When creating a new version of a published product offering, ServiceNow AI Platform® copies key details such as product specifications, contract terms, charges, descriptions, catalog info, and cost indicators into the new record. It also populates version identifiers like the incremental version number, display name, and links to previous versions. Additional validations ensure data integrity before publishing. ## Product Offering Life Cycle States Product offerings follow a strict life cycle: * **In Draft:** Offering is being modeled and not available for ordering. * **Published:** Offering is active and available for orders. * **Retired:** Offering is removed from ordering but remains in operational tables as read-only; can be republished if needed. * **Archived:** Offering is removed from operational tables but not deleted permanently; only retired offerings can be archived. **Important:** To archive a published offering, first retire it. Retiring allows for reuse or version creation later, while archiving is for long-term removal from operations. As a product catalog manager, you can create and publish the product offering versions that list enhanced products and services that you can offer to your customers. ## Overview of product offering versions {#creating-publishing-product-offering-somt__section_ekj_14t_2tb} You create versions of product offerings by combining new versions of product, service, and resource specifications. Proper versioning enables your customer service agents to know what the latest versions of your product and service offering. This information enables you to sell more expensive, complementary, upgraded, or related products to your customers. ## Creating versions of product offerings {#creating-publishing-product-offering-somt__section_tq4_tl2_2tb} When you create a product offering version, complete these steps: 1. Create and assign a version number in each of the product, service, or resource specifications or product offering records that are affected by the changes. To reflect the engineering changes that were made to the physical product, edit the following data that is associated with the product offering version: * Characteristics * Characteristic options * Product specifications {#creating-publishing-product-offering-somt__ul_x35_mb5_2tb} 2. Create the required specification relationships, decomposition rules, and attribute mappings for each specification in the new version. To learn more, see [Creating and publishing specification versions](https://www.servicenow.com/docs/NK5MZA0sgxqJ_6UyjX6qAg "Create and publish the specification versions that list the improved products and services that you can offer to your customers in a technical product catalog."). 3. Create the product offering, and then publish it when you update your product catalog. 4. Retire or archive old or unused specifications, and product offerings. To learn more, see [Retiring and archiving versioned specifications](https://www.servicenow.com/docs/cc4LE5LaS4ylKxnMU4o4yw "When a published specification or product offering is no longer being used, you can retire it. A retired version stays in the operational tables, but you can't use it in a product offering or create specification versions from it. To remove a retired version from the operational tables, archive it. Archiving doesn't permanently delete the version."). To learn about the difference between retiring and archiving a product offering, see [Product offering life cycle states](https://www.servicenow.com/docs/s~79gPELTzWwjxRty66iBg#creating-publishing-product-offering-somt__section_po_lifecycle_somt). {#creating-publishing-product-offering-somt__ol_dsz_5k2_2tb} ## Updates and validations that are performed when you create and publish a product offering version {#creating-publishing-product-offering-somt__section_qw5_mmt_2tb} When you create a version for a published product offering, the ServiceNow AI Platform® copies the following data into, or populates, the new product offering record with the following data: 1. Copies the following fields with these basic product offering details: * Product Specification * Contract Term * Monthly Recurring Charges * Non Recurring Charges * Description * Offering Catalog * Distribution Channel * Start and End date * Product code and Product line * Cost to Company * Composite, Installation Required, and Location-specific indicators {#creating-publishing-product-offering-somt__ul_eql_v5t_2tb} 2. Populates the following fields with the detailed information that you enter for the new product offering version: * Version. The next incremental number appears. * Display Name. The display name is the system-assigned concatenation of the product offering name and its current version number. You can overwrite this field. * Initial Version. The name of the base version of the product offering appears but can't be changed. * Previous Version: The name of the product offering is as it was in the previous version. {#creating-publishing-product-offering-somt__ul_wxc_r53_ptb} {#creating-publishing-product-offering-somt__ol_kyt_kst_2tb} When you publish the updated product version, additional validations are performed on your edits. To learn more, see the Updating and validating copied rules for a new specification version section in [Create and publish a specification version](https://www.servicenow.com/docs/gzkLb6geOombkkNUhM~01w "Create and publish a version of an existing specification in a Published state so that you can offer an improved version of it to your customers in your product catalog."). ## Product offering life cycle states {#creating-publishing-product-offering-somt__section_po_lifecycle_somt} A product offering moves through its life cycle states in order. You can't skip a state. A retired offering can also be published again. Retiring and archiving differ in what happens to the offering afterward. A retired offering stays in the operational tables but isn't available for ordering. An archived offering is removed from the operational tables but isn't permanently deleted. {#creating-publishing-product-offering-somt__table_po_lifecycle_somt__entry__3} | State | Description | Next action | |-|-|-| | In Draft | The product offering is being modeled and isn't ready for ordering. This is the default state of a new product offering. You can't set the state when you create the offering. | Publish | | Published | The product offering is available for ordering, including new and MACD orders. | Retire | | Retired | The product offering remains in the operational tables but isn't available for ordering. The record is read-only, and the system never deletes it. Retire an offering that you might want to reuse later, for example, to create a new version from it. You can also publish a retired offering again. | Archive or Publish | | Archived | The product offering is removed from the operational tables but isn't permanently deleted. | None | [Table 1. Product offering life cycle states] {#creating-publishing-product-offering-somt__table_po_lifecycle_somt} Important: You can archive only a retired product offering. To archive a published offering, retire it first.