SUPPLIER HUB
Campaigns, secure invites, and a real supplier portal.
Create supplier campaigns from published questionnaire templates (including the built-in VSME Basic and VSME Comprehensive supplier presets), send tokenised invites, and collect responses through the supplier portal—stored on the same project record as your evidence.
Quick fit check
See whether Supplier Hub matches how you collect supplier data. Free, no account required.
Do you need structured questionnaires, portal responses, and an audit trail from suppliers?
Indicative only; your workflows and governance choices still matter.
Free assessment. No account needed.
VSME supplier templates (built-in)
Each project automatically receives two published system templates when they are missing: “VSME Basic (supplier)” and “VSME Comprehensive (supplier)”. They map to the VSME disclosure presets used for supplier-facing requests—so buyers do not start from a blank page.
- Each project receives two system templates—VSME Basic (supplier) and VSME Comprehensive (supplier)—built from the same VSME disclosure preset code lists the product uses internally.
- Campaigns remember which template you chose and can snapshot the question list into the campaign so later template edits do not change what you already sent.
- Campaign metadata records whether the programme is CSRD-style value-chain disclosure or another due-diligence purpose—buyers pick this in the builder.
- The VSME package (basic, comprehensive, or broader catalog modes) is chosen explicitly in the guided request builder before anything is emailed.
Campaigns organise outbound supplier work
A campaign groups each wave of requests: name, deadline, draft or active status, and structured metadata for request type, VSME package, optional regulation add-ons, portal surface, and follow-up linkage.
- Creating or updating campaigns requires editor-or-above access on the buyer project—the server enforces roles, not just the UI.
- When a template snapshot exists, the question list is frozen at creation time so history stays defensible.
- Follow-up waves can reference a prior campaign with structured reasons and origin references for traceability.
- Native module flows (for example EUDR) can create companion campaigns with regulation-specific metadata automatically.
Invites: secure links and section targeting
Each invite stores a hashed token, respects expiry (including campaign deadlines), and carries metadata that tells the respond experience which questionnaire sections to surface.
- Suppliers open a dedicated respond URL with their token—no buyer-account login required for that path.
- When Smart Send picks sections explicitly, those codes are stored on the invite so the respond page does not second-guess your choice.
- If you do not pass explicit sections, the service can recommend sections from the supplier profile (NACE/EMTAK, country, headcount) using the smart questionnaire engine.
- PPWR supplier evidence flows use a PPWR-specific section allowlist—they do not fall back to unrelated CSDDD-style logic.
- Archived or blocked third parties are rejected before a fresh invite is issued.
Five orchestrated request types
The campaign builder stores a formal classification for every wave. Plain-language summary below matches what teams select in the product.
Baseline request
Structured VSME-aligned questionnaire packages (basic, comprehensive, or broader catalog modes) for value-chain disclosure programmes.
Add-on request
Optional modular blocks—e.g. EUDR, CBAM, PPWR, NIS2—layered on top of the baseline package when you need regulation-specific questions.
Evidence request
Targeted file or attestation collection (including PPWR-specific supplier evidence bridges) without a full questionnaire package.
Portal request
Workflows that expect the supplier to interact through the portal surface— including CBAM-specific portal intake when enabled.
Follow-up request
Structured re-requests tied to prior campaigns with explicit follow-up reasons and origin references for audit traceability.
Supplier portal & long-lived access
Beyond one-off respond links, suppliers can maintain their own portal accounts to view history, update profile data, and continue engagements—separate sign-in from the buyer workspace.
- Authenticated suppliers can pull invite history from dedicated portal APIs scoped to their organisation.
- After submitting a questionnaire, success flows can direct people back to portal login when ongoing access is useful.
- Supplier authentication is intentionally isolated from buyer SSO—different security posture, consistent data contracts.
- Responses still roll up to the buyer’s project so evidence and questionnaires stay in one system of record.
Smart Send & proportionality helpers
The Smart Send wizard analyses suppliers before email goes out: shortlist companies, review AI-assisted recommendations, choose sections, then bind that selection to the outgoing invites.
- Sections you confirm in the wizard are passed explicitly to the invite—no silent overwrite downstream.
- Value-chain ceiling helpers review SME profile inputs (for example headcount) and can flag when a request may exceed VSME-aligned limits—software guidance, not legal advice.
- Campaign metadata records whether proportionality / Omnibus helper notes were shown, supporting governance reviews.
VSME value-chain ceiling (product guardrail)
Regtrue includes helpers aligned with the anticipated VSME value-chain disclosure ceiling (employee thresholds, datapoint counts). Results depend on accurate supplier profile data—use them as proportionality support inside the product, not as a substitute for legal counsel on your facts.
See the full supplier orchestration flow
We will show campaigns, Smart Send, and portal history on a demo project.