ZenotiHelp

Create pipeline stages and lead sources

ZTZenoti Docs Team Updated September 5, 2026 6 min readGuide

Pipeline stages define the steps in your sales workflow. Each opportunity moves through these stages, from initial contact to a closed deal. Lead sources track where your opportunities originate, such as walk-ins, referrals, or marketing campaigns. Together, these settings provide the structure for tracking and reporting on your sales pipeline.

Note: For conceptual background on the pipeline and how stages fit into the opportunity lifecycle, see Opportunities overview.


On this page


Before you begin

  • You must be in the organization-level view. Pipeline stages and lead sources are managed at the organization level and apply across all centers. The form and save controls are not available in center-level views.

  • You need the following permissions:

    Permission: Add (under OpportunityProperties in the Administrator section) — Required to create pipeline stages and lead sources. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Administrator > OpportunityProperties > Add

    Permission: Edit (under OpportunityProperties in the Administrator section) — Required to modify existing pipeline stages and lead sources. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Administrator > OpportunityProperties > Edit

  • Decide on your stage progression before creating stages. You can reorder stages later by changing the display order, but planning ahead reduces rework.

Steps

Follow the procedures below to create and manage pipeline stages and lead sources.

Create a pipeline stage

Worked example: A spa creates a "Qualification" stage with code QUAL, display order 10, and description "Initial contact made; assessing guest interest." This becomes the first stage in their membership upsell pipeline.

  1. At the organization level, navigate to Configuration > Opportunities > Stages.

  2. Click Add.

  3. Enter the stage details:

    Field Description
    Code A unique identifier for the stage. Required. Maximum 64 characters. Must be unique within the organization.
    Name The display name of the stage. Required. Maximum 64 characters. Must be unique within the organization.
    Description A brief description of what this stage represents. Optional. Maximum 256 characters.
    Order A numeric value that controls the position of this stage in the pipeline. Required. Lower numbers appear first.
    Active Select to make the stage available for opportunities.
  4. Click Finish.

The system validates that both the stage name and code are unique within your organization before saving. If a duplicate name or code is detected, an error message appears and the save is blocked.

Edit a pipeline stage

  1. At the organization level, navigate to Configuration > Opportunities > Stages.
  2. Click the stage name in the Opportunity Stage column to open the stage form.
  3. Modify the stage details as needed.
  4. Toggle the Active status to enable or disable the stage.
  5. Click Save.

Important: Deactivating a pipeline stage does not remove it from opportunities already assigned to that stage. It only prevents the stage from being selected for new opportunities.

Search and filter stages

The stages page displays a paginated, searchable grid with columns for Code, Opportunity Stage, Description, and Active status. Use the search box above the grid to find specific stages by name or code.

To export the stages list, use the export controls above the grid. Export options are available to users with Export under Export_Admin in the Administrator section of their security role.

Create a lead source

  1. At the organization level, navigate to Configuration > Opportunities > Source.

  2. Click Add.

  3. Enter the source details:

    Field Description
    Code A unique identifier for the lead source. Required. Maximum 64 characters. Must be unique within the organization.
    Name The display name of the lead source. Required. Maximum 64 characters. Must be unique within the organization.
    Description A brief description of this lead source. Optional. Maximum 256 characters.
    Active Toggle to enable or disable this lead source. Active sources appear in the lead source dropdown when creating opportunities.
    Custom field 1–4 Optional fields (maximum 4,000 characters each). The label for each field is configured in your organization's opportunity settings.
  4. Click Save.

The system validates that both the lead source name and code are unique within your organization before saving.

Note: The labels for the four optional custom fields are set at the organization level under Configuration > Opportunities. Labels support translation for multi-language organizations. If no custom labels have been configured, the fields display as generic optional fields.

Tip: Lead source codes can be used by external integrations to reference a lead source without needing its internal ID. When an external system creates an opportunity and provides a lead source code, Zenoti resolves the correct lead source automatically.

Edit a lead source

  1. At the organization level, navigate to Configuration > Opportunities > Source.
  2. Click the source name in the grid to open the lead source form.
  3. Modify the source details as needed.
  4. Click Save.

What to configure next

After creating pipeline stages and lead sources, complete the following configuration steps:

Step Required or optional Article
Create dispositions to classify opportunity outcomes Required for closing opportunities Create dispositions and custom fields
Configure sales stage rules to automate stage transitions Optional Configure sales stage rules
Set default pipeline stages for each opportunity type Recommended Configure opportunity settings

Tips

  • Define your pipeline stages before configuring sales stage rules or setting default stages in opportunity settings. Sales stage rules reference specific stages by name, so creating stages first prevents gaps in your configuration.
  • Both stage codes and names must be unique within the organization. The system validates uniqueness when you save. If you receive a duplicate error, check whether an inactive stage already uses that code or name.
  • Use meaningful codes that you can reference quickly in reports and integrations — for example, QUAL for Qualification or PROP for Proposal.
  • Order your stages logically by setting display order values with gaps (for example, 10, 20, 30) so you can insert new stages later without reordering all existing stages.
  • Deactivate lead sources you no longer use rather than leaving them active, so the lead source dropdown stays uncluttered while historical opportunity data remains intact.
  • Custom field labels for lead sources are configured at the organization level under Configuration > Opportunities. If your organization operates in multiple languages, configure translated labels to ensure staff see field names in their preferred language.
  • Lead source codes can be used by external integrations to reference sources without needing internal IDs. Choose codes that are stable and human-readable to simplify integration maintenance.

Troubleshooting

The Add button is not visible on the Stages or Source page. You are likely viewing the page in a center-level context rather than the organization-level view. Pipeline stages and lead sources can only be created and edited at the organization level. Switch to the organization-level view and reload the page. If the button is still not visible, confirm that your security role has Add under OpportunityProperties in the Administrator section.

Saving a stage or lead source returns a duplicate name or code error. The organization already has a stage or lead source — active or inactive — with the same name or code. Check the full list including inactive records. Either choose a different name or code, or reactivate and edit the existing record if it represents the same concept.

The custom field labels on the lead source form are blank or show generic placeholder text. The optional field labels have not been configured for your organization. An administrator needs to set the labels under Configuration > Opportunities. Until labels are configured, the fields are still functional but display without descriptive names.

The stages grid does not reflect a change I recently saved. Changes to pipeline stages apply immediately. If the grid appears stale, refresh the page. If the change still does not appear, verify that the save completed without an error message and that you are viewing the correct organization-level context.

Was this article helpful?
Your feedback helps us improve our documentation.