ServiceNow Service Catalog

The Service Catalog is ServiceNow's self-service menu for employees. Instead of calling the help desk or sending emails to request IT services, employees browse a catalog — similar to an online shopping site — and submit their needs through a structured form. The catalog standardizes requests, reduces manual work for IT teams, and gives employees visibility into the status of their requests.

The Service Catalog Concept

Without Service Catalog:
  Employee: "I need a new laptop, email me at support@company.com"
  → Email goes to a shared inbox
  → Someone reads it eventually
  → Manual follow-up begins
  → No visibility on progress
  → Weeks pass

With Service Catalog:
  Employee: Opens catalog → Clicks "New Laptop Request" → Fills form
  → Request created automatically (RITM number assigned)
  → Routes to the right team instantly
  → Auto-notifications sent at each stage
  → Employee tracks status live
  → Resolved in days

Catalog Structure: Categories, Items, and Variables

Catalog Items

A catalog item is one specific requestable service. "Request a New Laptop," "Reset My VPN Password," and "Add Software License" are catalog items. Each item has a description, an image, and a form for the user to fill in.

Variables

Variables are the input fields on a catalog item's request form. When an employee requests a new laptop, variables capture details like preferred model, operating system, delivery address, and justification. Variables determine exactly what information the fulfillment team receives.

Catalog Item: "New Laptop Request"
┌────────────────────────────────────────────┐
│ Which model do you need?                   │
│ ○ Standard Business    ○ Developer Spec    │
│                                            │
│ Operating System:  [Windows 11  ▼]         │
│                                            │
│ Delivery Location: [Building A, Desk 204]  │
│                                            │
│ Business Justification: [____________]     │
│                                            │
│ [Add to Cart]                              │
└────────────────────────────────────────────┘

Variable Types in the Service Catalog

Single Line Text: Short text input (name, phone number)
Multi Line Text: Longer text (description, justification)
Select Box: A dropdown with fixed options
Check Box: A yes/no toggle
Reference: Links to a record in another table (e.g., select a user)
Date: A date picker
Attachment: Lets the user upload a file

The Request and RITM Structure

When an employee submits a catalog item, ServiceNow creates two records:

REQ0001234 (Request - the shopping cart)
  └── RITM0001235 (Requested Item - one specific catalog item)
  └── RITM0001236 (Requested Item - if they added a second item)

The REQ (Request) is like an order. The RITM (Requested Item) is each individual item in that order. If an employee requests a laptop and also requests software access in the same submission, one REQ gets created with two RITMs — one per catalog item.

Fulfillment Workflows

Each catalog item connects to a fulfillment workflow or flow. This automation runs when the RITM is created and handles the approval and fulfillment steps without manual intervention. A software license request might automatically:

Route to the employee's manager for approval
After approval, route to the IT provisioning team
After provisioning, notify the employee that access is ready
Auto-close the RITM after the employee confirms

Approval in the Service Catalog

Many catalog items require approval before fulfillment begins. ServiceNow creates an Approval record and notifies the approver by email. The approver clicks "Approve" or "Reject" from the email link or directly from ServiceNow. Multiple approval levels are supported — for example, manager approval followed by IT security approval before a privileged access request proceeds.

Catalog Item vs. Record Producer

A catalog item creates a Requested Item (RITM). A Record Producer is a type of catalog item that creates a record in any table instead — an incident, a problem, or a custom table record. Record producers let administrators use the catalog's friendly UI to guide users through creating complex records without exposing the backend form directly.

Designing Good Catalog Items

Well-designed catalog items share these qualities:

Clear, plain-language names that employees understand without technical knowledge
Only the variables the fulfillment team actually needs — no unnecessary fields
Helper text on each variable explaining what to enter and why
Logical variable ordering that guides the user through the request naturally
Accurate descriptions of what the user will receive and how long it typically takes

Previous lesson

Back to course

Next lesson