Chapter 1
Invite the supplier
Sofia Alvarez opens an onboarding case for Ridgeway Motion Controls, a fictional supplier. The invitation explains the Northstar Industrial Systems category, why the information is requested, and which documents are in scope. The supplier receives a clear response path. The dashboard shows only fictional, non-sensitive data. An invitation is not an approval, a contract, or permission to transact.
- Evidence visible
- Invitation purpose · Category · Requested information · Requested documents · Owner · Response status
- Human action
- Sofia reviews and sends the invitation.
- Policy or system boundary
- An invitation begins evidence collection; it does not approve the supplier.
- Accessible alternative
- Chapter 1 shows Sofia sending a fictional supplier an onboarding invitation that identifies the category, information requested, document scope, and response path. The status is Invitation sent, not approved.
Read the complete walkthrough
Invite the supplier
Sofia Alvarez opens an onboarding case for Ridgeway Motion Controls, a fictional supplier. The invitation explains the Northstar Industrial Systems category, why the information is requested, and which documents are in scope. The supplier receives a clear response path. The dashboard shows only fictional, non-sensitive data. An invitation is not an approval, a contract, or permission to transact.
Collect structured information
Ridgeway Motion Controls submits organization details, operating locations, relevant certifications, insurance evidence, and category experience. Each field identifies the supplier as its source. Configured required-field checks distinguish complete from missing information, but completion does not establish accuracy or compliance. Sofia can request clarification without losing the original response.
Review qualification evidence
Sofia compares submitted evidence with Northstar Industrial Systems' fictional qualification requirements. Financial, operational, compliance, and category criteria remain separate so one status does not mask another. A certification record needs clarification because its scope does not clearly cover the proposed site. Sofia records the question and routes it back to the supplier. The platform organizes the evidence; it does not certify the supplier or eliminate reviewer judgment.
Segment and assess risk
Once the clarification arrives, Sofia reviews criticality, substitutability, operational dependency, document status, and other approved risk dimensions. The illustration places Ridgeway in a critical-supplier segment because the component affects a maintenance window and qualified alternatives are limited. The rationale and source evidence are visible. This is a fictional Northstar Industrial Systems policy example, not a universal risk score.
Approve with conditions
Sofia submits the case to the configured supplier-approval path. The authorized reviewers approve Ridgeway for the defined category and site, subject to document-expiry monitoring and a scheduled performance review. The approval scope is explicit. Approval does not mean the supplier is universally approved, compliant in every jurisdiction, or guaranteed to perform. The decision, conditions, and reviewer notes remain attached to the case.
Prepare governed handoff
The onboarding case now separates approved supplier master fields from supporting evidence and review notes. Customer-specific mappings determine which approved objects can move to the ERP framework. The ERP remains the financial system of record for agreed records and postings. Sofia retains ownership of document expiry and periodic review. The trace shows invitation, supplier response, clarification, assessment, approval, and handoff readiness.