Back to Blog
Blog

Can a new vendor intake process coexist with an established Salesforce portal?

Can a new vendor intake process coexist with an established Salesforce portal?

A new vendor intake process can usually coexist with an established Salesforce portal, and in most cases it should, since replacing a portal that…

A new vendor intake process can usually coexist with an established Salesforce portal, and in most cases it should, since replacing a portal that vendors and internal teams already use creates more disruption than it is worth. Vendors have accounts, bookmarks and habits built around the existing portal, and internal teams often have reports, approvals and other processes connected to it, so pulling it out to make room for a new intake tool puts all of that at risk for very little gain.

The new process can sit behind or alongside the existing portal, handling the document review and assessment while the portal stays the place vendors go. In practice a vendor uploads their documents through the portal as they always have, those documents are passed to the review process, and the results of the assessment come back to the portal so the vendor and the internal team can see where things stand.

What matters is that vendor records and statuses stay in sync between the two, so nobody has to check two systems to know where a vendor stands. If a buyer sees a vendor as approved in Salesforce while the HSE assessment shows an expired certificate, the whole point of the assessment is lost, so status changes need to flow between the systems quickly and in a way that can be checked when something looks wrong.

Agreeing early on which system owns which information, such as contact details in one and assessment results in the other, avoids most of the problems later. Ownership means that only one system is allowed to change a given field and the other reads it, which stops two teams from updating the same address or status in different places and ending up with two versions of the vendor that never quite match.

A sensible rollout starts with a small group of vendors and a limited set of fields moving between the systems, then expands once the sync has proven reliable and the internal teams trust what they see. It is also worth deciding up front how vendors already in the portal will be brought into the new assessment, since a backlog of existing vendors with no assessment record is a common surprise once the new process goes live.