A vendor onboarding app for procurement teams. Add suppliers, review required evidence, and record activation, suspension, or a return to qualification.

Accord gives each new vendor a qualification record with an owner, target date, and a copy of the selected requirement profile. Reviewers record evidence references, expiry dates, and notes before an activation decision. Missing or expired required evidence blocks activation. Profile changes affect future intakes while existing vendor reviews retain their progress. This built pilot uses ToolJet Database and fictional data; deployment and download await package and clean-install validation.
Built for Procurement and operations coordinators qualifying technology, professional services, facilities, and logistics suppliers.
Give every requirement an owner, a review outcome, and enough context for the next decision.
Review the qualification pipeline and the next suppliers approaching their target date. Open the vendor directory for the complete bounded list.
Add the vendor name, contact, unique contact email, owner, category, country, target activation date, and qualification profile. The profile becomes an individual set of requirements for that vendor.
Record requirement owners, references, expiry dates, review notes, and outcomes. Activate only when requirements are accepted with current evidence; suspend or return to Qualifying with a decision reason.
Create and edit named profiles with a description and one requirement per line. New intakes receive the revised requirements; existing vendor review records keep their own copy.
Pipeline stages separate Qualifying, Active, and Suspended vendors. Target dates and review progress help coordinators choose which supplier needs attention next.
Create a vendor and their requirement copy together. A unique contact email helps prevent duplicate intake, and a named internal owner keeps responsibility visible.
Track Missing, Submitted, Changes requested, and Accepted outcomes. Submitted or accepted work needs an evidence reference; accepted evidence with an expiry date must be current before activation.
Create reusable profiles for different supplier types. Edits apply to future vendor intakes, preserving the evidence and review progress already attached to existing suppliers.
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Qualification profiles | 3 sample profiles | Named requirement lists for standard suppliers, technology partners, and site services. |
| Vendors | 6 sample vendors | Contacts, owners, target dates, individual requirement reviews, status, and decision history. |
Evidence is stored as a reference or document location; the app does not upload documents, verify certifications externally, run background checks, send messages, or approve a legal contract. Role-based access policies are not configured. This English desktop pilot reads up to 1,000 rows per table; larger deployments need pagination. After reloading a detail page, reopen the vendor from the directory. Package export and clean installation remain unverified.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance once the template is released.
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.
Accord includes supplier intake, qualification profiles, requirement reviews, and activation or suspension decisions across four pages. It stores the evidence reference and decision context with the vendor.
Every requirement must be Accepted with an evidence reference. If an expiry date is present, it must not be in the past. The coordinator then records an activation decision and reason.
No. The pilot stores a document location or other evidence reference. File storage, certification checks, background checks, and external verification are not included.
Yes. Create or edit reusable profiles on the Requirements page. Changes apply to future vendor intakes; existing vendor records retain their original review requirements.
Yes. Record a decision to return the vendor to Qualifying, then update requirement reviews. Suspension and status decisions retain a reason in the activity history.
Yes. Use the starter prompt or ask for your logo, colors, preferred layout, fields, and review steps. Suggested prompts describe document uploads, evidence renewal, and Arabic translation as extensions to build and test.
The app uses ToolJet Database with three fictional qualification profiles and six vendors. It is in English with light and dark appearances; translations and right-to-left layouts need implementation and testing.
Public deployment and download remain disabled until the exported package and clean installation have been validated.