Supplier Management · Onboarding

Supplier Onboarding

ESS Hub provides a structured supplier onboarding process for bringing new suppliers into the collaboration platform.

Buyers can invite suppliers, define the relevant process scope, request onboarding documents and review supplier submissions. Suppliers can register from their invitation, submit the required information and documents, respond to review feedback and complete onboarding before participating in the enabled supplier processes.

Scope

Supplier Onboarding in ESS Hub should not be confused with Supplier Qualification. The current onboarding process focuses on supplier access, required documentation and process enablement.

Process

Supplier onboarding process

The onboarding process as it exists in ESS Hub today, from the buyer's invitation to the activated supplier. Each step is a record with a status; there are no qualification stages.

Invitation and registration
01BuyerInvites the supplier by e-mail
02Supplier invitationCompany, country, registration link
03Supplier registrationAccount created from the invitation
04Onboarding requirementsDocuments requested from the supplier
Documents and completion
01Document submissionSupplier uploads each requested document
02Buyer reviewView file · approve · reject with reason
03Approved / RejectedStatus per document
04Re-upload if requiredRejected documents resubmitted
05Onboarding completeAll required documents approved · supplier activated
Process as implemented in ESS HubSupplier steps in navy

Invitations

Supplier invitations

Buyers invite suppliers into ESS Hub by e-mail. The invitation is the first onboarding record: its status shows, at account level, whether the supplier has already registered. The two invitation entry points share the same lifecycle — Invited, then Accepted or Revoked; “pending” is the count of invitations still in Invited.

Who invites
Authorized enterprise users, from Supplier Onboarding (documents-based onboarding) or from New Supplier for Logistics (logistics workspace).
Invitation data
E-mail address, company name and country; a logistics invitation adds contact name, plant codes, the process scope and an optional message.
Delivery
An invitation e-mail with a link to register and access the workspace; the invitation link can also be copied and a reminder resent.
Invited
The invitation has been sent and is still open — shown under pending invitations.
Accepted
The supplier has joined; the invitation is marked as accepted.
Revoked
The invitation was withdrawn by the buyer.
Onboarding view
Counters for invited suppliers, suppliers in onboarding and completed onboardings.

Scope

Process-specific onboarding

A logistics invitation is associated with the process scope in which the supplier will collaborate with the customer, and with the plant codes it will serve. Onboarding therefore reflects how the supplier will actually work with the customer rather than a generic portal account. The scope describes the collaboration; which application permissions a supplier user has follows from the roles assigned in the supplier's team and the modules enabled in the implementation.

Logistics invitation · process scope
ASN / ShipmentsAdvance shipping notices
Call-offs & demandsScheduling agreements and call-offs
Packaging (PDS)Packaging data sheets
ReturnablesReturnable packaging accounts
Traditional EDIEDI connection onboarding
Supplier workspaceThe supplier collaborates in the processes it was invited to, for the plants named in the invitation
Scopes offered by the logistics invitation in ESS Hub todayRoles and modules per implementation

Registration

Supplier self-registration

Registration is self-service, but only from a valid invitation. The supplier enters a contact name, sets a password of at least eight characters and chooses the portal language (English, German or Chinese); ESS Hub creates the account for the invited e-mail address, and an invitation link that is invalid or incomplete shows a message to contact the buyer for a new invitation. No further identity or company verification takes place in the current product, and no supplier master record is created automatically in the customer's ERP.

01Supplier receives the invitationE-mail with the registration link
02Supplier follows the linkInvitation checked by ESS Hub
03Supplier registers the accountContact name · password · portal language
04Account readySign-in with the invited e-mail address
05Onboarding checklistRequested documents in the supplier workspace
Registration as implemented in ESS HubSupplier steps in navy

Documents

Onboarding documents

Buyers can request documents from suppliers as part of onboarding — the documents required for activation, such as quality certificates, banking details or a code of conduct, depending on the customer's process. Each requested document is a record with a title, a document type and a status: Requested → Submitted → Approved / Rejected. Which documents are required is defined on the customer side per implementation; ESS Hub keeps the submission, the status and the review note, and does not itself verify the content of a document.

01BuyerDocuments required for activation
02Document requestedStatus Requested in the supplier's checklist
03SupplierUploads the file (up to 15 MB)
04Document submittedStatus Submitted · submission date
05Buyer reviewView file · approve or reject
06Approved / RejectedStatus per document · reviewer note on rejection
Document states as implemented in ESS HubSupplier steps in navy

Review

Buyer review

Authorized enterprise users review submitted onboarding documents in the Supplier Onboarding area:

  • Suppliers in onboarding are listed with the number of approved documents against the number required
  • opening a supplier shows each document with its type, status, submission date or “not submitted yet”, and any review note
  • for a submitted document the buyer can view the file, approve it or reject it
  • a rejection requires a reason, which is shown to the supplier as the reviewer note
  • when all required documents are approved, the supplier is shown as activated

This is document review within the onboarding process. It is not a supplier qualification decision, and ESS Hub does not score or rank the supplier on it.

Feedback loop

Rejected documents and re-upload

A rejected document is not a dead end. The supplier sees the reviewer note next to the document and re-uploads a new file, which returns to Submitted for review. The current record keeps the latest file, its status, the submission and review dates and the note; ESS Hub does not present a version history of earlier files.

01Document submittedSupplier upload
02Buyer reviewEnterprise user
03RejectedStatus Rejected
04Review noteReason shown to the supplier
05Supplier re-uploadNew file · status back to Submitted
06Buyer reviewApprove or reject again
Feedback loop as implemented in ESS HubSupplier steps in navy

Supplier view

Supplier onboarding visibility

On the supplier side, onboarding is visible in the Onboarding Checklist: it lists the onboarding documents required from the supplier — “Your onboarding documents” — with the status of each, the reviewer note for rejected documents and the upload or re-upload action. The page heading counts how many documents are approved out of those requested.

When every required document has been approved, the checklist shows “All documents approved — Your onboarding is complete.” A pending indicator in the navigation points the supplier to open onboarding tasks until then.

Separately, the supplier's cockpit shows a Getting started list of first steps in the workspace — confirm the pending packaging data sheet, read and confirm open supplier letters and required documents, review the contact matrix — with a count of completed steps. It is a checklist, not a scoring of the supplier.

Enablement

From onboarding to supplier collaboration

After onboarding, the supplier works in its ESS Hub workspace. What it can do there depends on the modules and processes enabled for that supplier and customer implementation — for example scheduling agreements and call-offs, ASN and shipments, packaging, quality or finance — and on the roles of its users. Onboarding does not automatically enable every ESS Hub module. Supplier Portal · Procurement · Supplier Quality

01Supplier onboardingInvitation · registration · documents approved
02Supplier accessSupplier workspace and roles
03Enabled processesModules and process scope per implementation
04Procurement · Logistics · Quality · FinanceOperational collaboration
Enablement per implementationESS Hub in navy

Mixed landscape

Onboarding EDI and non-EDI suppliers

Supplier onboarding in ESS Hub exists in a mixed supplier landscape. Suppliers without EDI are onboarded into the web portal; EDI-capable suppliers can be invited with the Traditional EDI scope and use the EDI connection self-onboarding area — choice of format (VDA 4987 Global DESADV or ANSI X12 856), test parameters and a browser-side check of a sample message. The technical EDI connection and its configuration remain part of the customer's integration landscape; ESS Hub does not replace that setup. Automotive WebEDI · Connecting non-EDI suppliers to SAP

Portal supplier
01Portal supplierInvited and registered
02ESS HubOnboarding documents · supplier workspace
03Enterprise processCustomer's SAP / ERP landscape
EDI supplier
01EDI supplierInvited with the Traditional EDI scope
02EDI connection onboardingFormat · test parameters · sample check
03Existing EDICustomer's integration layer
04Enterprise processCustomer's SAP / ERP landscape
Two supplier channels, one enterprise processESS Hub in navy

Distinction

Supplier onboarding vs Supplier Qualification

Supplier OnboardingSupplier Qualification
PurposeBring the supplier into the operational collaboration processEvaluate whether a supplier meets defined qualification criteria
Question answeredCan this supplier work with us in ESS Hub, with the required documents in place?Does this supplier meet our business, quality or other requirements?
Current ESS Hub capabilityYes — invitations, registration, required documents, document submission, document review, approval / rejection, re-upload, onboarding completionNot currently documented as a completed ESS Hub capability

The two concepts are related but different. Approving an onboarding document confirms that a required document has been provided; it is not a statement that the supplier has been qualified against criteria. ESS Hub's supplier quality capabilities — APQP, PPAP, 8D, Supplier Scorecards, certificates and audits — are also distinct processes and are not qualification either.

Documents

Onboarding documents vs supplier certificates

Onboarding documents and supplier certificates are related but different records in ESS Hub.

Onboarding documents
Requested by the buyer during onboarding; one file per requirement; statuses Requested, Submitted, Approved, Rejected; approval of all required documents activates the supplier.
Certificates
Ongoing management of the supplier's quality certificates in the quality workspace: certificate type, valid-until date and the statuses Valid, Expiring, Expired; the supplier uploads a renewal with the renewal document.
Relationship
A quality certificate may be one of the documents requested at onboarding; afterwards, certificate validity is followed in Certificates, not in the onboarding checklist.

Audits

Audits and onboarding

Supplier Audits are a separate supplier-quality capability and should not be confused with the onboarding document workflow. Audits in ESS Hub cover planned audits, findings and audit evidence in the supplier's quality workspace; they are not an onboarding gate, and completing onboarding does not depend on an audit in the current product. Supplier Quality in ESS Hub

Access

Security and access

Supplier onboarding creates access to the ESS Hub collaboration environment according to the implemented access model: the account is created from the invitation for the invited e-mail address; the supplier is activated on the enterprise side once its required documents are approved; supplier users have business roles — administrator, logistics, quality, finance — and a permission matrix defines what each role can see and do; the supplier's administrator invites colleagues and manages their roles; each supplier sees only its own organization's data. Reviewing onboarding documents and inviting suppliers are enterprise permissions. Authentication, session and infrastructure controls are described on the Security page. Security & Architecture

Product evidence

Supplier Onboarding in ESS Hub

app.esshub.ai · Supplier Onboarding
ESS Hub Supplier Onboarding, enterprise view: invited, in-onboarding and completed counters; pending invitations with company, country, invitation date, status and resend action; suppliers in onboarding with document progress and a review action.
Supplier Onboarding (enterprise view): invitations, suppliers in onboarding with document progress and review.Demo data
app.esshub.ai · Onboarding Checklist
ESS Hub Onboarding Checklist, supplier view: four required documents with approved, submitted and requested states and an upload action for the outstanding document.
Onboarding Checklist (supplier view): required documents with requested, submitted and approved states and upload.Demo data
app.esshub.ai · Supplier Onboarding · Review
ESS Hub onboarding review panel for one supplier: required documents (bank account confirmation, fiscal registration certificate, ISO 9001 / IATF 16949 certificate, signed NDA) with requested, submitted and approved states and approve or reject actions.
Review panel: approve or reject each submitted onboarding document.Demo data
app.esshub.ai · Onboarding Checklist
ESS Hub Onboarding Checklist, supplier view: all four documents approved and onboarding marked complete.
Onboarding complete: all required documents approved.Demo data

Traceability

Onboarding status and traceability

What ESS Hub records about onboarding today: statuses and dates on the invitation and on each document, and the reviewer note for a rejected document. Platform-wide, enterprise administrators have an audit trail of status changes in the portal.

Invitation
Invited → Accepted or Revoked; date sent; e-mail, company and country.
Supplier in onboarding
Approved documents against required documents; activated when all are approved.
Document
Requested → Submitted → Approved / Rejected; document type; submission date; review date; reviewer note on rejection.
Supplier side
The same document statuses and notes in the Onboarding Checklist; completion message when all documents are approved.
Not in the current product
A version history of earlier uploads, an onboarding-specific audit log or a percentage score of the supplier.

Lifecycle

Part of the wider supplier lifecycle

Onboarding is the entry point into a supplier relationship that ESS Hub then supports across procurement, logistics, quality and finance, with supplier performance made visible in Supplier Scorecards. Not every module is enabled automatically, and qualification is not a stage of this lifecycle in the current product.

01Supplier invitationBuyer
02OnboardingRegistration · documents · activation
03Operational collaborationEnabled processes
04Procurement · Logistics · Quality · FinanceModules per implementation
05Supplier performanceSupplier Scorecards
Conceptual lifecycle · modules per implementationESS Hub in navy

FAQ

Frequently asked questions

Does ESS Hub support Supplier Onboarding?

Yes. ESS Hub provides a structured supplier onboarding process: the buyer invites the supplier, the supplier registers from the invitation, the buyer requests the onboarding documents, the supplier submits them, the buyer reviews and approves or rejects each document, and the supplier is activated once all required documents are approved.

Can buyers invite suppliers to ESS Hub?

Yes. Authorized enterprise users invite a supplier by e-mail with the company name and country; the invitation carries the link to register. Logistics invitations can also carry the process scope and the plants the supplier will serve.

Can suppliers register from an invitation?

Yes. The supplier follows the invitation link, enters a contact name, sets a password and chooses the portal language; ESS Hub creates the account for the invited e-mail address and the supplier signs in with it.

Can onboarding be configured for different supplier processes?

Yes. A logistics invitation is associated with the process scope the supplier will collaborate in — ASN / Shipments, Call-offs & demands, Packaging (PDS), Returnables, Traditional EDI — and with plant codes. Which modules the supplier then sees follows the modules and process scopes enabled in the implementation.

What onboarding scopes does ESS Hub support?

The logistics invitation in the current product offers ASN / Shipments, Call-offs & demands, Packaging (PDS), Returnables and Traditional EDI. Further process areas — procurement, quality, finance — are enabled through the supplier's roles and the implementation scope rather than through the invitation.

Can buyers request onboarding documents?

Yes. The documents required for activation are requested per supplier and appear in the supplier's onboarding checklist with the status Requested; which documents are required is defined on the customer side per implementation.

Can suppliers upload onboarding documents?

Yes. In the Onboarding Checklist the supplier uploads one file per requested document (up to 15 MB); the document moves to Submitted with the submission date.

Can buyers approve or reject supplier documents?

Yes. In Supplier Onboarding the buyer opens the supplier, views the submitted file and approves it or rejects it with a reason. The reason is shown to the supplier.

Can suppliers re-upload rejected documents?

Yes. A rejected document shows the reviewer note and a Re-upload action; the new file goes back to Submitted for review.

Can suppliers see when onboarding is complete?

Yes. The Onboarding Checklist shows how many documents are approved and, once all required documents are approved, the message “Your onboarding is complete”. On the enterprise side the supplier is shown as activated.

Can EDI suppliers be included in the onboarding process?

Yes. Traditional EDI is one of the invitation scopes, and EDI-capable suppliers have an EDI connection self-onboarding area in ESS Hub — format choice, test parameters and a check of a sample message. The technical EDI connection itself is set up in the customer's integration landscape.

Is Supplier Onboarding the same as Supplier Qualification?

No. Supplier onboarding brings the supplier into the operational collaboration process — access, required documents, process enablement. Supplier qualification evaluates whether a supplier meets defined qualification criteria; it is a different process with different questions.

Does ESS Hub currently support Supplier Qualification?

Supplier Qualification is not currently documented as a completed ESS Hub capability. ESS Hub currently provides structured Supplier Onboarding, document review, Supplier Scorecards, APQP, PPAP, supplier audits, certificates and 8D-related supplier quality capabilities.

Does ESS Hub support Supplier Assessment?

A supplier self-assessment area (“My Profile & Assessment”) exists in the supplier workspace, but it is not currently documented as a completed ESS Hub capability and should not be read as a completed supplier-assessment or supplier-qualification function. The documented supplier-quality capabilities are APQP, PPAP, complaints and 8D, Supplier Scorecards, certificates and audits.