Service management deep-dive · Lesson

Service catalog

Quick answer

The Service Catalog is the "shop" where users request things, a laptop, access, a new-hire setup, through a friendly, structured front end instead of a free-text ticket. Structured requests mean predictable fulfilment, approvals and automation.

Key takeaways

The building blocks
Request → item → task
Catalog item vs record producer
Where users see it
Common mistakes

The Service Catalog is the "shop" where users request things, a laptop, access, a new-hire setup, through a friendly, structured front end instead of a free-text ticket. Structured requests mean predictable fulfilment, approvals and automation.

The building blocks

Catalog item

The thing you can request.

Variables

The questions on the order form (which model? how much RAM?).

Variable set

A reusable group of variables shared across items.

Record producer

A catalog-style form that creates a record on any table (e.g. an incident).

Order guide

Bundles several items into one request (new-hire onboarding).

Catalog / Category

Organise items into browsable groups.

Request → item → task

Submitting builds a three-level hierarchy that fulfilment teams work against:

REQ  (the order / request)
 +- RITM  (one requested item: "MacBook Pro 16")
     +- approval  --> manager
     +- SCTASK    --> fulfilment team (procure, image, deliver)

Fulfilment is orchestrated by Flow Designer, approvals first, then tasks routed to the right groups, with the request closing when all items complete.

Catalog item vs record producer

Both present a friendly form. A catalog item creates a request/RITM and runs a fulfilment workflow, use it for things people order. A record producer creates a record on a target table directly, use it for a friendly "Report an issue" form that opens an incident. Choosing the wrong one is a classic design error.

Where users see it

The catalog is surfaced through the Service Portal / Employee Center, the consumer-grade experience most requesters use, with search, categories and a shopping-cart flow.

Common mistakes

Using a record producer where a catalog item is needed (or vice versa).
Duplicating variables instead of a shared variable set.
Hard-coding approvals in the item instead of a reusable flow.
One giant item with 40 variables instead of an order guide.

Want to learn this properly?

Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

Ordering a catalog item creates which parent record?
- A. An incident
- B. A Request (REQ)
- C. A problem
Show answer
B. A Request (REQ)
A REQ is created, with a RITM per requested item.
What bundles several items into one guided flow?
- A. Order guide
- B. Business rule
- C. SLA
Show answer
A. Order guide
Order guides package multiple items, e.g. for onboarding.
A record producer lets a catalog form:
- A. Only order laptops
- B. Create any type of record
- C. Delete records
Show answer
B. Create any type of record
Record producers can create records on any table.

Frequently asked questions

What does the term Service catalog refer to in ServiceNow?

What is worth remembering about Service catalog in practice?

The catalog is surfaced through the Service Portal / Employee Center, the consumer-grade experience most requesters use, with search, categories and a shopping-cart flow.

What tends to go wrong with Service catalog?

Using a record producer where a catalog item is needed (or vice versa). Duplicating variables instead of a shared variable set. Hard-coding approvals in the item instead of a reusable flow.