Purchase request management template
A purchase request tracker for operations and procurement teams. Create a department request, assign a reviewer, and record the amount, needed-by label, status, and decision notes.
What is this procurement template?
Approve opens with a decision queue for requests that still need judgment and a department breakdown that makes demand visible. Staff can open the searchable request list, create a request for an existing department, and update reviewer, manually recorded status, requested USD amount, needed-by label and notes. It coordinates decisions without claiming to enforce approval permissions.
- Screens
- 2 connected pages
- Data source
- ToolJet Database
- Language
- English
- Appearance
- Light + dark
Built for Operations coordinators and procurement teams recording purchase requests before an order is placed.
From a purchase request to a recorded decision.
Keep the proposed purchase and review context visible before ordering outside the app.
- Overview
Review the purchase queue
See the current purchase requests and their department context. Use the overview to identify the next request to review.
- Requests
Record the purchase request
Create a request linked to an existing department, with its purchase and supplier context, requested USD amount, and needed-by label.
- Requests
Record the review decision
Assign a reviewer and update the manually recorded status and notes while keeping the original request context visible.
What does the template cover?
A purchase request overview
A compact violet workspace presents the purchase queue with clear department context and a focused review hierarchy.
Requests linked to departments
Create a purchase-and-supplier description linked to an existing department, with the amount and timing context needed for review.
Reviewer and decision tracking
Record a reviewer and a status of Draft, In review, Approved, Declined, or Ordered. These are editable records, not server-enforced approval permissions.
Amounts and context together
Keep the requested USD amount, manual needed-by label, and latest notes together. The tracker does not place orders, reserve budgets, or retain a versioned decision trail.
ToolJet Database with sample data
The pilot uses 2 tables with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Departments | 4 sample departments | Department reference, name, and purchasing context. |
| Purchase requests | 8 sample requests | Department, purchase and supplier, reviewer, status, requested USD amount, needed-by label, and notes. |
The overview lists the first three In review requests; its totals include the complete bounded review queue. The department summary excludes Declined requests. Approval states are manually recorded. Server-enforced reviewer roles, budgets, policy routing, segregation of duties, and a versioned audit trail are not configured. Purchase orders, invoices, ERP integration, and payments are not included. USD only; needed-by values are manual labels. The English desktop pilot reads up to 1,000 rows per table and blocks writes above that limit. Export and clean installation remain unverified.
Make it yours with AI.
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.
How to use this template.
Add it to your workspace
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance once the template is released.
Start with the included database
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Make it work your way
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.
Template FAQs
What does this purchase request template include?
Approve includes a purchase overview and a request page. Staff can create department requests and update reviewer, status, amount, needed-by label, and notes.
Does the app enforce approval permissions?
No. Approval statuses are manually recorded by workspace users. Reviewer roles, amount thresholds, segregation of duties, and server-enforced approval policies must be implemented before using it as an approval system.
Does Approved place an order or authorize payment?
No. Approved and Ordered are recorded statuses. The app does not place purchase orders, authorize payment, or connect to an ERP.
Does it track budgets or multiple currencies?
The pilot stores requested amounts in USD. Budget controls, foreign exchange, and multicurrency accounting are not included.
Can I customize the design and review workflow with AI?
Yes. Use the starter prompt for your branding and layout, or the approval-policy prompt to request additional rules. Any permission-sensitive workflow needs implementation and testing with separate user roles.
Is there a decision audit trail?
The current request stores its status and latest note. It does not retain a timestamped, immutable history of every decision or edit.
Which database, languages, and download options are included?
The built pilot uses ToolJet Database and English sample data. Other languages can be requested with AI. Deploy and download remain unavailable while the package and clean database setup are validated.
Expense reimbursement
Receive individual expense claims, review receipt references against saved per-expense limits, and record approval or reimbursement.
Security exception management
Track time-limited security exceptions with a risk owner, compensating controls, recorded assessment and remediation evidence.
Employee probation reviews
Coordinate employee probation reviews using role-specific periods, manager feedback, competency scores and documented confirmation or extension decisions.