Best IT service catalog software 2026: tools compared for IT teams

We compared catalog features using each vendor's own documentation and pricing pages, plus G2 or Capterra ratings, all checked on 8 Oct 2026. No vendor reviewed or paid for this article. We did not run hands-on tests.

The best IT service catalog software is the one whose forms, approvals and fulfillment tasks match how your requests actually get done. ServiceNow suits deep, multi-team catalogs. Jira Service Management and Freshservice suit teams that want a catalog running quickly, and ManageEngine, BMC Helix, Ivanti, SolarWinds, HaloITSM, SysAid and TOPdesk each fit a specific budget or stack. This guide compares how each IT service catalog handles request forms, approvals, fulfillment and plan gating, using vendor docs. It is written for service owners building or rebuilding a request catalog. It also covers what happens to catalog items and past requests when you change platforms.

Key takeaways

• ServiceNow records each catalog order as a Request, Requested Item and Catalog Task, with form answers on the Requested Item (ServiceNow docs, as of 8 Oct 2026).
• Freshservice includes the service catalog from Growth ($49 per agent/month, billed annually), not Starter (Freshservice pricing page, as of 8 Oct 2026).
• ManageEngine ServiceDesk Plus sells the catalog as a US$1,195 annual add-on below Enterprise (ManageEngine pricing page, as of 8 Oct 2026).
• Jira Service Management's Free plan, for up to 3 agents, includes request types, dynamic forms and a portal (Atlassian pricing page, as of 8 Oct 2026).
• In a migration, catalog definitions are rebuilt and request history moves: Freshservice says catalog items can't be exported from the catalog (Freshservice docs, as of 8 Oct 2026).

What an IT service catalog is

An IT service catalog is the published list of IT services and items employees can request, with a form, an approval path and a fulfillment process behind each one. The catalog is what is live and orderable today, such as a laptop, software access or a new starter bundle.

Every catalog item has three working parts:

• The form: the questions a requester answers. ServiceNow calls them variables, Freshservice uses custom fields on service items, and Jira Service Management uses fields and forms on a request type.
• The approval path: who must say yes, and in what order.
• The fulfillment work: the tasks, child tickets or flows that deliver the item.

Behind each order sit records. ServiceNow's Request Management architecture page names three tables: Request [sc_request], Request Item [sc_req_item] and Catalog Task [sc_task] (as of 8 Oct 2026). Other tools use fewer levels, which matters when you report on requests or move them.

What to look for in IT service catalog software

Judge each tool on the parts of the catalog your service owners will touch every week:

1. Form logic. Conditional fields, reusable question sets and lookups cut bad requests at the source.
2. Approvals. Multi-stage approvals, approvers preset per item, and approval history kept on the request.
3. Fulfillment. Tasks or child tickets per team, dependencies between tasks, and an SLA per item.
4. Portal and entitlements. Control over who sees which item, by group, department or location.
5. Plan gating. The plan where the catalog first appears, and any add-on fee.
6. Data access. Whether you can export item definitions and the answers on past requests. This decides how painful your next platform change will be.

IT service catalog tools compared

Prices come from each vendor's pricing page and ratings from G2, or from Capterra where G2 shows fewer than 50 reviews. All were checked on 8 Oct 2026.

The 10 service catalog software options

1. ServiceNow Service Catalog

ServiceNow lists "Service Catalog and Request Management" in ITSM Foundation, so Advanced and Prime include it too. Prices are by custom quote (ServiceNow ITSM pricing page, as of 8 Oct 2026).

• Catalog capability: items collect answers through variables. Variable sets are reusable across items and order guides and carry their own catalog client scripts and UI policies; multi-row variable sets let one request cover several servers (ServiceNow docs). Record producers create task records such as incidents from a catalog form. Fulfillment runs on Flow Designer flows, workflows or linear execution plans.
• What to watch: answers are stored apart from the request, in the Options [sc_item_option] and Variable Ownership [sc_item_option_mtom] tables, so reports and exports need joins.

2. Jira Service Management

Request types are the catalog. Atlassian's documentation says each request type is based on an issue type (a work type in Cloud) and follows its workflow. Fields can be renamed for customers or hidden with preset values, forms can show or hide fields with conditional logic, and approvers can be preset per request type. Atlassian recommends portal groups once you have seven or more request types.

• Pricing: Free for up to 3 agents with request types, dynamic forms and a portal; Standard $20 and Premium $51.42 per agent/month (Atlassian Service Collection pricing page, as of 8 Oct 2026).
• What to watch: each request is one work item shaped by its request type, with no requested-item layer like ServiceNow's. Multi-team fulfillment is designed in the workflow and automation rules, so plan those before you add many request types.

3. Freshservice

The catalog supports three levels of categories. Service items carry custom fields, including lookups for dependent choices, can show cost and delivery time in the portal, can be limited to requester groups, and can create child requests per item, each with its own SLA (Freshservice catalog article, modified 17 Sep 2026). Approvals run through the Workflow Automator, listed with "multi-approval workflows" on every plan.

• Pricing: catalog from Growth at $49; Pro $99 per agent/month, billed annually (Freshservice pricing page, as of 8 Oct 2026).
• What to watch: Freshservice says items can't be exported from the catalog directly and points to the API. Its ticket export article says service request item fields are not included in standard ticket exports.

4. ManageEngine ServiceDesk Plus

ManageEngine describes a template per service, a five-stage approval process, tasks with dependencies, SLAs per service and cost fields (ManageEngine service catalog page, as of 8 Oct 2026). It runs on premises or in the cloud.

• Pricing: from $13 Standard, $27 Professional and $67 Enterprise per technician/month on the on-premises view. The service catalog is a US$1,195 annual add-on on Standard and Professional and comes out of the box in Enterprise (ManageEngine pricing page, as of 8 Oct 2026).
• What to watch: the add-on changes the math on lower editions. Price Enterprise against Professional plus add-ons.

5. BMC Helix Digital Workplace Catalog

BMC Helix runs its catalog in BMC Helix Digital Workplace: service request definitions, workflows, entitlements and questionnaires, with services from IT, HR, Facilities and other units. Fulfillment happens in BMC Helix ITSM or BMC Helix Business Workflows (BMC Helix docs, as of 8 Oct 2026).

• Pricing: not published; the product page offers "Request Pricing".
• What to watch: the docs mark enhanced catalog features, such as bundles, workflows and questionnaires, as Advanced license capabilities. Confirm your license level before designing items.

6. Ivanti Neurons for ITSM

Service owners build request offerings and publish them to the Service Catalog. The Form Designer supports expressions for conditional controls, and the Workflow Designer handles multi-step fulfillment with approval blocks (Ivanti help, 2025 release). Deployment can be cloud, on-premises or hybrid.

• Pricing: not published; the product page offers "Contact Sales" (as of 8 Oct 2026).
• What to watch: Ivanti's docs say you can only publish offerings to organizational units you belong to, plus their parent and child units. Settle the org structure first.

7. SolarWinds Service Desk

SolarWinds includes the Service Catalog and Service Portal in Essentials. Its catalog page describes custom forms with dynamic form rules and approval processes per service.

• Pricing: Essentials $39, Advanced $99, Premier $124 per technician/month, billed annually (SolarWinds pricing page, as of 8 Oct 2026).
• What to watch: the pricing page places Advanced Automations in Advanced. Check which catalog automations you need before settling on Essentials.

8. HaloITSM

Each service in Halo's catalogue has request buttons that log a ticket type, a template or a custom URL. Custom fields sit on the ticket type, approval processes are added to a workflow, and templates can log linked child tickets (Halo guides, as of 8 Oct 2026).

• Pricing: £66 per agent/month, billed annually, with "No tiers, no bolt-ons" (Halo pricing page, as of 8 Oct 2026).
• What to watch: the same page lists Service Requests as included as standard but shows the Service Catalogue under optional features in its trial setup list. Confirm with Halo.

9. SysAid

SysAid's Service Catalog is a widget in the Self-Service Portal. Items can open a service request form with a predefined template, and visibility can be limited by group (SysAid documentation). Service request management with templates and approval workflows is on both plans.

• Pricing: Professional $89 per agent/month, with no billing period stated; Enterprise is custom from 20 agents (SysAid pricing page, as of 8 Oct 2026).
• What to watch: the catalog is a navigation layer. Form logic and approvals live in the templates and workflows behind it.

10. TOPdesk

TOPdesk includes the service catalogue and Self-Service Portal in all three plans, including facility services. Portal forms take questions and memo fields, appear as tiles or link to a service, and create a Call or Change card on submission (TOPdesk docs, as of 8 Oct 2026).

• Pricing: Essential £51, Engaged £72, Excellent £101 per agent/month; 50+ agents need a quote (TOPdesk pricing page, as of 8 Oct 2026).
• What to watch: the pricing page does not state billing terms. Ask before comparing it with annual-billed tools.

Which service catalog tool fits your team

Service catalog vs self-service portal

The portal is the storefront and the catalog is what is on the shelves. A self-service portal is where people sign in, search knowledge and track requests; the service catalog is the set of orderable items and the process behind each one.

The vendor docs show the split. SysAid switches its Service Catalog on as a widget inside the Self-Service Portal settings, and Jira Service Management groups request types into portal groups.

Changing a portal's look changes nothing about fulfillment. Changing a catalog item changes who approves, which team works and which SLA applies. When you switch platforms both are rebuilt, but the catalog takes the design work.

Catalog items in a migration

Catalog definitions are configuration and get rebuilt; past requests are records and move. Treat them as two workstreams from day one.

Four things go wrong most often, based on the vendor docs:

Answers sit apart from the request. ServiceNow associates variables only with the Requested Item and stores values in separate option tables. Freshservice says service request item fields are not in standard ticket exports, and its API has a separate endpoint for requested items. Export only the tickets and you lose what people asked for.

Definitions don't travel between vendors. ServiceNow's docs say update sets carry catalog item definitions, variables and variable choices, but not submitted orders or catalog tasks. That helps between ServiceNow instances, not when leaving ServiceNow.

Hierarchies don't match. ServiceNow has three levels, Freshservice has parent and child requests, and Jira Service Management has one work item per request. Decide how each Requested Item and Catalog Task maps before you test.

Imports can break the portal and SLAs. Atlassian's knowledge base says CSV imports should set the request type by ID, or request types may not map and portal visibility suffers. It also says closed issues imported by CSV can keep counting against SLAs, and gives two fixes (as of 8 Oct 2026).

What switching involves

Switching IT service catalog software means moving records and rebuilding logic. Records, history, attachments and links between records move. Workflows, automations, business rules, SLA definitions, catalog forms and running SLA timers are rebuilt on the target.

A controlled move runs in six phases:

1. Discover. List every active catalog item with its questions, approvers and fulfillment teams, and decide how much request history audit and reporting need.
2. Map. Map item to item, question to field, and the source hierarchy to the target's, including where old answers land when no field matches.
3. Test migration. Move a sample with multi-item orders, rejected approvals and attachments, then check it in the target portal and agent view.
4. Cutover with delta sync. Freeze catalog changes, run the main load, then sync requests created or updated during the window. Source APIs page results, for example ServiceNow's Table API returns 10,000 records per request by default (ServiceNow Table API docs, as of 8 Oct 2026).
5. Reconcile. Compare counts per catalog item, answers, approvals and attachments between source and target.
6. Hypercare. Watch the first new orders flow through the rebuilt approvals and tasks, and fix gaps fast.

FAQ

Methodology

We built the shortlist from tools whose vendors document a service catalog or request catalog feature. Features, plan gating and prices come from each vendor's own documentation and pricing pages, and ratings from G2, or from Capterra where G2 shows fewer than 50 reviews, all checked on 8 Oct 2026. We did not run hands-on tests, and prices can change after that date. Disclosure: MigrateX, the publisher of this article, runs ITSM data migrations, including between platforms named here. No vendor reviewed or paid for this article.