What is the Service Catalog in ServiceNow?

Why Interviewers Ask This

The Service Catalog is one of the most visible parts of ServiceNow for end users. Interviewers want to see that you understand the full request lifecycle — not just the front-end form.

What Is the Service Catalog?

The Service Catalog is a self-service portal where employees can browse and request services or products — like an internal shopping site. Instead of sending emails or calling the help desk, users find what they need, fill out a form, and submit.

Catalog vs Incident — The Key Difference

• Incident: Something is BROKEN. Reactive. 'My laptop won't turn on.' The goal is to fix it fast.
• Service Request (Catalog): The user WANTS something. Proactive. 'I need a new laptop.' The goal is to fulfill the order through a defined process.

The Components

• Catalog Item: A requestable service or product. 'Request a Laptop', 'VPN Access', 'New Hire Onboarding Package'.
• Variables: The form fields specific to that item. Laptop model dropdown, justification text field, delivery date picker.
• Variable Sets: Reusable groups of variables shared across multiple catalog items. A 'Delivery Address' variable set used by laptop, monitor, and phone requests.
• Workflow / Flow: The backend process that handles approval and fulfillment.

What Happens When a User Submits

// User clicks 'Order Now' on 'Request a Laptop'
//
// 1. REQUEST created (sc_request) — REQ0010001
//    The overall 'order' record
//
// 2. REQUESTED ITEM created (sc_req_item) — RITM0010001
//    The specific line item (one per catalog item ordered)
//    Contains all the variable values (laptop model, etc.)
//
// 3. APPROVAL triggered
//    Flow/Workflow checks: Does this need manager approval?
//    If cost > $500, route to manager → If approved, continue
//
// 4. CATALOG TASKS created (sc_task)
//    SCTASK0010001: 'Procurement: Order laptop from vendor'
//    SCTASK0010002: 'IT: Configure laptop and install software'
//    SCTASK0010003: 'Facilities: Ship to employee's desk'
//
// 5. Each task assigned to the relevant team
//    Teams work their tasks independently
//
// 6. All tasks complete → RITM auto-closes → REQ auto-closes
//    User gets a notification: 'Your laptop is on its way!'