- Timeline
- Apr 2026 – Jul 2026
- Status
- Completed
- Platform
- Web
Overview
Raphe runs its procurement as tickets. A requester raises a ticket for the items a project needs, and it moves through approval by the requesting department, procurement, finance and management until a purchase order is raised, then on to delivery and payment.
Every user gets a task center: a focus queue of high-priority tickets, priorities from ASAP to within a week, an on-time-in-full (OTIF) score and an execution streak. Analytics cover tickets, supplier payments and the delivery schedule, and a cashflow view tracks every payment due.
I worked on it at Heizen with Next.js, NestJS and PostgreSQL, including automating ticket assignment. Development is complete, and it runs on Raphe's own servers.
Built forRequesters, buyers, finance and management teams at Raphe mPhibr.
What it does
- A ticket for every purchase, with approvals from the requesting department, procurement, finance and management, plus stages and amendments.
- Automatic ticket assignment, and stages that can move on their own.
- A personal task center with a focus queue, priorities from ASAP to within a week, OTIF tracking and an execution streak.
- Analytics for tickets and supplier payables, and a delivery schedule with partial receipts.
- A cashflow view of payment schedules by ticket and supplier, with bulk clearance.
- Master data for items, suppliers, segments, payment terms, units, currencies and warehouses, with supplier onboarding, import, export and ERP sync.
How it's built
- Interface
- Next.js
- API
- NestJS
- Data
- PostgreSQL
- Hosting
- On-premise servers