Overview
Before SMOOT, purchase requests, orders, payments, and supporting documents were spread across fairly manual processes. The procurement team had to piece together status updates and approval history to see where a request stood. This made day to day tracking, report preparation, and tracing decisions for audits harder. SMOOT brings purchasing data into one place so those tasks are easier to manage.
My contribution
Contributed to SMOOT's serverless backend: request and approval APIs, order workflow, payment records, document handling, notifications, audit trail, search, vendor master, and reporting.
Key capabilities
- Role based access for requester, approver, and admin
- Purchase requests and approvals
- Order and payment records
- Supporting documents and notifications
- Audit trail, search, and vendor master
- Reporting and Excel / CSV export
Implementation considerations
The backend needed to keep requests, approvals, orders, payment records, and supporting documents connected throughout the process. Requesters, approvers, and admins have different permissions and actions, while status changes and user activity need a traceable history. The APIs also had to support notifications, useful search and filters, and data for reporting without adding manual work.
Delivery
SMOOT centralizes purchasing data and makes request and order statuses easier to track. Approval and activity history is more organized for audits and reporting.