Fulfillment Teams

A team is a named group of staff members responsible for a specific step in the fulfillment pipeline. When an order reaches a pipeline stage assigned to a team, all tasks for that stage appear in that team's queue. Teams can be scoped to a specific location or shared across all locations.

Creating a Team

1. Go to Settings → Teams.
2. Click Add Team.
3. Enter a name for the team — for example, Packing, QC, Cutting, or Dispatch.
4. Optionally assign the team to a specific location. Leave location blank to make the team org-wide (available to all locations).
5. Save the team, then add members by selecting from your organization's staff list.

Org-Wide vs Location-Scoped Teams

• Org-wide team: no location is set. The team can be assigned to pipeline stages in any pipeline regardless of which location uses it. Suitable for central specialist teams such as a QC team that handles all locations.
• Location-scoped team: the team is tied to one location. Only that location's fulfillments flow into the team's queue. Suitable when staff at different locations should only see their own tasks.

Assigning Teams to Pipeline Stages

Each stage in a fulfillment pipeline can have one team assigned. When a fulfillment enters that stage, all team members can see and claim the task.

1. Open Settings → Fulfillment Pipelines and select a pipeline.
2. Click on a stage to edit it.
3. Select the team responsible for this stage from the team dropdown.
4. Save and publish the pipeline.

If no team is assigned to a stage, any staff member can see and act on tasks at that stage.

How Task Assignment Works

When a fulfillment task is queued for a stage:

• If the stage has a team, the task appears in every team member's task queue.
• Any team member can claim the task (move it to in_progress). The assignee field on the task is then set to that member.
• Only the assignee can mark it done or failed. A supervisor can reassign if needed.
• If no team is set on the stage, the task is unassigned and visible to all staff with fulfillment access.

Common Blockers

• Staff member not seeing tasks: check that the staff member is in the team assigned to that pipeline stage and that the pipeline version is current.
• Wrong team seeing tasks: check the pipeline stage's team assignment. Editing the pipeline creates a new version — confirm the new version is published and in use on new orders.
• Team not appearing in pipeline stage dropdown: make sure the team is active. Inactive teams are not shown in the assignment list.

Related Docs

• Fulfillment Pipelines
• Locations
• Order Lifecycle