What is Sales CRM
ServiceNow Sales CRM manages the whole product sales life cycle on one platform: pre-sales leads and opportunities, quotes, order capture and fulfilment, order and invoice cases, and post-sales changes and renewals. Front, middle and back-office work from the same data, so there is no hand-off between a separate CRM, CPQ and order system.
Companies have long run these steps across separate stacks: a CRM for selling, a CPQ tool for quoting, an order manager for fulfilment and back-office systems for billing and service. Each hand-off means re-keying or syncing data, and every sync is a place where orders fail. Sales CRM replaces those hand-offs with one data model, so an accepted quote becomes an order directly and its terms, prices and configuration carry through to fulfilment.
Its applications fall into seven stages — sales automation; configure, price and quote (CPQ); order management; order operations; post-sales engagement; partner relationship management; and B2B self-service — all resting on a shared lead-to-cash foundation of Product Catalog Management and Lead to Cash Core. Industry editions, such as the one for telecommunications (SOMT) covered below, extend this same core.
The whole Sales CRM product view
Sales CRM is one flow from lead to renewal: each stage hands its record to the next, and all of them read the same catalog and CRM Core.
Leads mature into opportunities, which feed forecasting and quoting. Quotes are configured and priced, then routed through approvals; won deals become agreements or contracts and convert to orders. Order and invoice issues become order operations cases, and changes after the sale run through life cycle workflows. Partners and B2B customers enter the same flow through partner management and the Business Portal.
Sales CRM module guide
In the Australia release, ServiceNow documents 24 Sales CRM applications across eight groups.
Stage | Application | What it does |
Sales automation | Captures prospects and develops them into opportunities | |
Sales automation | Combines automated and manual outreach across channels | |
Sales automation | Tracks the customer stakeholders involved in a product-family purchase | |
Sales automation | Identifies and tracks potential sales from customer needs | |
Sales automation | Projects sales and revenue from opportunity and pipeline data | |
Sales automation | Divides accounts, leads, opportunities and consumers into territories | |
Sales automation | Plans, records and tracks calls, meetings and demos | |
CPQ | Configures and prices customizable products in Sales CRM transactions | |
CPQ | Embedded interface for configuring complex products in opportunities, quotes and orders | |
CPQ | Suggests upsell and cross-sell products during quoting | |
CPQ | Price lists, price controls and external pricing | |
CPQ | Creates, prices, approves and completes quotes in one place | |
CPQ | Approval workflows for quotes and other records | |
CPQ | Contracts and entitlements from offer to finalization | |
CPQ | Turns quote scope and terms into buyer–seller agreements | |
Order management | Orders from capture through fulfilment , with automation and a unified workspace | |
Order operations | Cases for customer orders and invoices | |
Order operations | Consolidated view of key sales data and activities | |
Order operations | Returns, replacements and repairs for installed items | |
Post-sales engagement | Move, add, change and disconnect workflows for sold products | |
Partners | Recruits and manages channel partners | |
Lead-to-cash foundation | Organizes product offerings into catalog and categories | |
Lead-to-cash foundation | Configures Sales CRM workflows and entity metadata | |
Business Portal | B2B customers create and manage orders, invoices and quote requests |
The rest of this article zooms into the foundation layer — Product Catalog Management — starting with how it works in the telecom edition, SOMT.
Sales CRM for telecom: SOMT
SOMT — Sales and Order Management for Telecommunications, documented today as Sales CRM for Telecommunications — is the industry edition of Sales CRM for telecom, media and technology providers. It keeps the same lead-to-cash flow and adds what complex network services need:
- PSR catalog — product, service and resource specifications modelled on the TM Forum SID standard.
- Catalog-driven decomposition — a customer order is split into product, service and resource domain orders and routed to fulfilment, provisioning or field operations.
- Product inventory — records of what each customer owns, created from catalog definitions and updated as orders progress.
- In-flight changes — upgrade, downgrade, suspend, resume and disconnect orders.
- TM Forum Open APIs — TMF620 (catalog), TMF622 (product order), TMF641 (service order) and TMF637 (product inventory).
Where Product Catalog Management fits
Product Catalog Management is the foundation layer of SOMT: it sells nothing itself, but every sale and fulfilment step reads from it.
On the sales side, leads, opportunities and quotes pull offerings, prices, eligibility and recommendations from the catalog. Once an order is placed, Order Management reads the specification relationships to decompose it, and product inventory is created from the same catalog definitions.
Underneath, the catalog follows TM Forum's SID layering, called the PSR (product, service, resource) model:
- Product offering — the customer-facing, priced item; can be a bundle.
- Product specification — what the product is; links one service specification and one or more resource specifications.
- Customer-facing service specification (CFSS) — the service the customer buys, independent of technology.
- Resource-facing service specification (RFSS) — how that service is realized technically, for example DSL, VPN or MPLS.
- Resource specification — templates for network and physical resources, such as routers or SIM cards.
Why we need it
Without a governed catalog, every downstream SOMT process guesses: sales sells things fulfilment cannot build, quotes carry prices nobody approved, and orders fall out because a product has no mapping to a service or resource. Product Catalog Management removes the guesswork by defining each product once and letting every process read that one definition.
- One source of truth. Offerings, specifications, characteristics and prices live in one catalog that leads, opportunities, quotes, orders, inventory and contracts all reference.
- Faster launches. Product managers model a new offer by reusing published specifications, families and bundles, so launching a new plan becomes configuration rather than code.
- Sell only what can be delivered. Eligibility rules filter what each account, location or contract can see, and compatibility rules block invalid combinations before the quote is sent.
- Fulfilment that follows the catalog. Specification relationships and decomposition rules tell Order Management how to split a customer order into service and resource orders — the basis of catalog-driven orchestration and fewer fallouts.
- Safe change over time. Versioning and lifecycle states let you change a product without breaking quotes, orders or inventory already built on the old version, with a full audit trail.
- Smarter selling. Needs analysis, upsell and cross-sell recommendations and AI search help sellers and B2B customers find the right offer faster.
- Open integration. The TMF620 Product Catalog API lets external channels and legacy catalogs read and sync the same catalog.
Feature tour
Product Catalog Management covers 12 feature areas, from the data model to the open API.
Feature | What it does |
Layers commercial offerings over product, service (CFSS/RFSS) and resource specifications, following TM Forum SID | |
Defines what a product is: type (Goods, Network, Service), characteristics and options, composite and transient flags | |
Groups sellable, configurable offerings into hierarchical catalog and categories, with keyword and AI search in the catalog UI | |
Product offering families | Multi-level parent-child groups that apply attributes and rules to many offerings at once |
Bundling | Builds bundle offerings from offer hierarchies and relationship groups, referencing specifications at any level |
Pricing | Offering prices, price lists and pricing matrices |
Eligibility and compatibility | Filters catalog, categories and offerings by account, location or contract; compatibility rules set allowed combinations |
Draft, Published, Retired and Archived states; new versions instead of in-place edits | |
Needs analysis and recommendations | Selection questionnaires for leads and opportunities; upsell and cross-sell on quote lines |
Configurator and Business Portal | Configures offerings in quotes and orders; B2B customers order from the catalog (Yokohama release onward) |
Catalog-driven decomposition | Specification relationships and decomposition rules split customer orders into domain orders |
Exposes catalog, offerings, prices and specifications to external systems (Product Catalog Advanced app) |
How a product moves through the catalog
A product goes from idea to order in six steps, and only published versions ever reach a seller or customer.
- Model the technical building blocks. Define resource and service specifications (CFSS and RFSS), then the product specification that links them.
- Describe the product. Add characteristics and options (speed, data allowance, contract term) and how each option is fulfilled.
- Publish the specifications. Publishing moves a spec from Draft to Published; it is then locked, and changes need a new version.
- Package it for sale. Create the product offering on the spec, add prices, place it in catalog and categories, and group it into families or bundles.
- Control who sees it. Apply eligibility and compatibility rules, and set up needs analysis and recommendations.
- Sell, order and fulfil. Sellers and portal users pick the offering in quotes and orders; Order Management decomposes it using the catalog’ s relationships. When the product is no longer sold, retire or archive it.
To get started, activate the Product Catalog Management Core plugin and assign the product catalog manager role) to the people who will own the catalog.
Licensing and commercials
ServiceNow does not publish list prices for Sales CRM; packaging and pricing come through ServiceNow or a partner. These official pages are the starting points:
- Sales CRM solution overview — the Sales Force Automation, CPQ and Order Management offerings
- CPQ pricing — request a quote or demo for CPQ
- Sales and Order Management for Technology Providers — the edition for technology providers
- Sales CRM for Telecommunications (SOMT) documentation — the telecom edition and its release notes
Check your entitlements with your ServiceNow account team before planning an implementation, as some features (for example Product Catalog Advanced and the TMF Open APIs) depend on the edition you subscribe to.
Sources
- Product Catalog Management — ServiceNow docs
- Unified sales and order management (SOMT) — ServiceNow docs
- Sales CRM for Telecommunications (SOMT) — ServiceNow docs
- Create and publish product specifications — ServiceNow docs
- Retiring or archiving versioned specifications and product offerings — ServiceNow docs
- Product Catalog Open API (TMF620) — ServiceNow docs
- Sales and Order Management for Technology Providers — ServiceNow
- Introduction to ServiceNow SOM — ServiceNow Community
- Exploring Sales Customer Relationship Management — ServiceNow docs
- Autonomous CRM for Sales — ServiceNow
Thank you!
Thank you for reading this first article in the series. I hope it gives you a clear map of ServiceNow Sales CRM and where Product Catalog Management fits in it.
If you found this useful, please like, share and subscribe, and follow me so you don't miss what's next. I'd love to hear your questions and experiences in the comments.
