Service catalog items give users a clean self-service way to request things from IT and other teams. This guide walks you through building one from scratch and getting it live.
Why catalog items replace email requests
Before service catalogs, users emailed IT for everything — software, hardware, access requests. Those emails got lost, requirements were unclear, and nobody knew who was supposed to fulfill what. Teams wasted time clarifying requests and tracking status manually. Service catalog items solve this by giving users structured forms that collect the right information upfront and route requests to the right fulfillment team automatically.
How catalog items work
A catalog item is a structured form that users fill out to make requests. When they submit it, ServiceNow creates a request record (RITM) and routes it to a fulfillment group. The basic version is just a form that creates a ticket someone works manually. The production version adds variables to collect specific information, workflows or flows to automate fulfillment, and approval processes when needed. Categories organize items in the catalog, and the active/inactive state controls whether users can see and request the item.
Taking it beyond basic requests
Once your basic item works, the common improvements are: adding variables to collect structured data instead of free-text descriptions, building flows to automate fulfillment tasks, setting up approval workflows for expensive or sensitive requests, and creating multiple catalog items that share variables through variable sets. Well-designed catalogs group related items logically and use consistent variable naming so reporting across items actually works.
Before you start
- •catalog_admin or admin role
- •At least one fulfillment group configured in your instance
Sourdough: ServiceNow Monitoring and Analytics
A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.
Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.
Step by step
Create the catalog item record
Navigate to Service Catalog > Catalog Definitions > Maintain Items and click New. Fill in Name (what users see in the catalog), Short description (appears under the name in catalog views), and Description (the full description users see on the item page). Set Table to 'Service Catalog Item' unless you're building something specialized.
Configure basic item settings
Set Active to false for now — you'll flip this true after testing. Choose your Category (creates the catalog structure users navigate). Set Type to 'Item' for standard requests. Fill in Order (controls sort position within the category) — start with 100 so you can insert other items later.
Leave Workflow blank initially — most new items work fine with just fulfillment groups until you need complex automation.
Set the fulfillment group
In the Fulfillment section, set Assigned to (fulfillment group) to the team that will work these requests. This determines who sees the resulting tickets in their queue. Set Assignment group to the same value unless you have a specific reason to route differently. Don't leave this blank — requests without fulfillment groups disappear into limbo.
Set both Assigned to and Assignment group even if they seem redundant — different parts of ServiceNow check different fields.
Configure availability and access
In the Availability section, leave Available for to 'Everyone' unless you need to restrict access. Set Roles if only specific roles should see this item. Most items should be available on both Service Portal and Classic UI unless your organization uses only one interface.
Test with inactive state
Save the record and test it while Active is still false. Navigate to Service Catalog > Catalog Home and append '?sysparm_catalog_view=admin' to the URL — this shows inactive items for testing. Find your item and submit a test request to verify the fulfillment routing works.
Publish the item
After testing works correctly, edit your catalog item and set Active to true, then save. The item now appears in the standard catalog views for users to request. Check both Service Portal and Classic UI to confirm it displays properly in your chosen category.
Best practices
Set a fulfillment group directly on the catalog item even when using flows — if the flow breaks, requests won't vanish into limbo.
Use Order values in increments of 100 so you can insert items later without renumbering everything.
Test catalog items in inactive state first — once you set Active to true, users can immediately start submitting requests.
Keep Short description under 100 characters — longer descriptions get truncated in mobile views and catalog tiles.
Don't use workflows for new catalog items unless you have a specific automation need — fulfillment groups handle most scenarios better.
Test Your Knowledge
Quick 3-question quiz — see how your ServiceNow skills stack up.
A list view on a table with millions of records is slow. Best fix?
Select an answer to continue