difference in service catalog and request management

[major li]

Hi Community, in my organization, we separate the responsibility of service catalog and request management. But from the description, i found it is so hard to tell the difference and they are under different domain illustrated in the capabilities map. Could you help me to understand what is difference and what is the day-to-day activities? Thank you Community.

[Ankur Bawiskar]

@major li 

did you check these links?

Platform: Request Management & Service Catalogs || Knowledge & Troubleshooting Resources 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[major li]

 hi @Ankur Bawiskar ,

i did. but I am still confused about what activities should be done for 2 items. 

[Ankur Bawiskar]

@major li 

My thoughts

Service Catalog -> What can be requested

Request Management -> How requests are processed and fulfilled

Service Catalog

Purpose: Digital menu of offerings users can request (hardware, software, services).

Day-to-Day: Create, organize, update catalog items and categories; ensure accurate descriptions and a great user experience.

Request Management

Purpose: Oversees the full process after a request is submitted—approvals, fulfillment, tracking, completion.

Day-to-Day: Process incoming requests, assign tasks, manage approvals/fulfillment, communicate status to users, monitor SLAs, and resolve issues.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[major li]

hi @Ankur Bawiskar ,

thank you for the reply. As a developer, my daily work focuses much on the form creation. 

From your POV, does my work belong to service catalog? 

If I need to migrate multiple catalog items from one instance to another, does it belong to service catalog?