When users order catalog items, someone needs to fulfill those requests — but only if the tasks land with the right team. This guide shows you how to set the fulfillment group so catalog tasks automatically assign to the people who can actually complete the work.
Why fulfillment group assignment matters
Without a fulfillment group configured, catalog item tasks land in limbo — created but unassigned, sitting in queues nobody monitors. This breaks the entire service catalog experience for end users who submit requests and hear nothing back. The people who feel this pain are service desk managers watching SLA breaches, fulfillment teams who miss requests they never knew existed, and platform teams fielding complaints about 'broken' catalog items that are technically working but organizationally useless.
How catalog task assignment works
ServiceNow creates an sc_task record for each catalog item ordered, and that task needs an Assignment Group to route properly. The fulfillment group on the catalog item serves as the fallback assignment — if no workflow or flow overrides it, that's where the task goes. Most catalog items start with this simple approach: set the fulfillment group directly on the item definition. More complex scenarios layer on workflows or flows that dynamically assign based on user location, requested quantity, or approval outcomes, but those still depend on the item-level fulfillment group as a safety net.
Building robust assignment logic
A basic catalog item with a fulfillment group gets you working assignments immediately. Production improvements include adding location-based routing (mobile devices go to different teams per site), approval-driven assignment (expensive requests route to procurement after approval), and escalation paths (tasks reassign if not touched within SLA thresholds). The key insight: always set the item-level fulfillment group even when using dynamic assignment. When workflows break or flows have logic gaps, that fallback assignment prevents requests from disappearing.
Before you start
- •catalog_admin or admin role
- •Assignment groups already created for fulfillment teams
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
Navigate to your catalog item
Go to Service Catalog > Catalog Definitions > Maintain Items. Search for and open the catalog item you want to configure. If you're creating a new item, you'll set this during the creation process.
Use the name or item number in the search — the list view can be slow with large catalogs.
Open the Process Engine tab
Click the Process Engine tab on the catalog item form. This tab contains the fulfillment settings that control task assignment and workflow execution. You'll see fields for Fulfillment Group, Workflow, and other process-related settings.
Set the fulfillment group
In the Fulfillment Group field, select the assignment group that should handle tasks for this catalog item. Use the reference lookup to find the correct group by name. This group will receive all sc_task records created when users order this item, unless a workflow or flow overrides the assignment.
Configure workflow if needed
If you want dynamic assignment logic, set the Workflow field to point to a custom workflow that handles routing. The workflow can examine request details and assign tasks to different groups based on criteria like location or cost. Leave this blank if simple fulfillment group assignment meets your needs.
Set task assignment fields
Review the Task Assignment fields section for additional routing options. You can set a specific Assigned To user if individual assignment makes more sense than group assignment. Most scenarios use group assignment for workload distribution.
Save and test the configuration
Click Update to save your changes. Test by ordering the catalog item and verifying that the resulting sc_task record has the correct Assignment Group populated. Check that the task appears in the target group's queue as expected.
Best practices
Set a fulfillment group directly on the catalog item even when using workflows or flows — if the automation breaks, requests won't vanish into limbo.
Choose assignment groups that actively monitor their ServiceNow queues, not email aliases or groups that only exist on paper.
Test assignment logic with real user accounts, not admin accounts — permissions and scoping can affect which groups appear in workflows.
Document your fulfillment group choices in the catalog item description so future admins understand the routing logic.
Use consistent naming patterns for fulfillment groups across catalog items to make reporting and maintenance easier.
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