Manage vendor profiles, favourites and the pipeline

A vendor profile helps teams discover and recognise a company; a favourite marks workspace interest; a project pipeline state describes what is happening in one procurement. Keep those signals separate. A vendor can be a favourite without joining a project, and the same vendor can progress differently in two projects.

Before you start

• Decide whether you are recording workspace interest or a project-specific outcome.

• Use factual, reusable profile information and keep confidential project evidence on the project vendor page.

Step by step

1. Open the vendor profile

Search Vendors and open the company. Review identity, website, categories and capabilities before relying on the record for discovery.

2. Favourite useful vendors

Use Favourite to place a vendor in your workspace’s Favourites view. This is a private discovery shortcut; it neither contacts the vendor nor changes a project.

3. Manage private vendors

Use Your vendors for workspace-submitted records and Archived for records no longer active in normal discovery. Restore an archived record when it becomes relevant again.

4. Open the project relationship

Choose the relevant project or navigate to Projects → Vendors. Set the vendor’s pipeline state according to that project’s actual progress.

5. Keep evidence with the status

Record outreach, questionnaires, demos, meetings, proposals and decision notes in their dedicated project areas. Update the pipeline after the evidence changes, rather than using the status as the only record.

What happens next

• Use filters and favourites to maintain a useful discovery list without bloating active projects.

• When a vendor leaves consideration, choose whether elimination or removal best preserves the project history.

Troubleshooting

Favouriting did not add the vendor to a project

Favourites are workspace bookmarks. Open the target project and use Add vendor to create the project relationship.

A pipeline status differs between projects

This is expected and usually correct. Status belongs to each project-vendor relationship, not the directory company.

A profile cannot be edited

Curated directory data may be controlled centrally. Add project-specific information to the project vendor record or submit a correction through the available review path.

Related guides