Production MRP System

Category: Manufacturing
Platform: Web App
Year: 2026; Built
Developer: Jake
Stat: 190+; API routes
Stat: 43; database tables
Stat: 36; dashboard screens

Preview

Web · Desktop & Mobile

Client project under NDA. Real screens, blurred to keep the client's name and data private; the last one shows how it's built.

An internal MRP system for a food manufacturer, in production and used by its own staff: recipes, material batches with expiry dates, production, purchasing and costing in one place. It works out what a production run needs and tracks each batch from receiving to the finished product.

What's Included

Materials and products with categories and suppliers
Recipes (bill of materials) and an MRP calculator
Production orders with material requirements
Purchase suggestions, purchase orders and goods receiving
Material batches with expiry tracking
Stock in and out, adjustments and a movement log
Retail packages, packaging orders and package sales
Expenses, revenue and cost of goods sold
Financial and production reports exported to CSV
Three roles with 123 permissions, plus activity logs

The Problem

A food manufacturer buys materials that expire, turns them into products by recipe and sells them in packages. It needed to know what to buy for a production run, use the oldest stock first, and see what each product really cost.

By the Numbers

190+
API routes
43
database tables
36
dashboard screens
6
CSV reports

Under the Hood

Highlight 01
First expired, first out
I wrote the batch consumption service. Production takes materials from the batch that expires first, shows the pick before committing it, and records the cost of each batch it used.
Highlight 02
Cost that traces to the batch
Because every consumption records its batch and unit cost, cost of goods sold is built from the batches a run actually used.
Highlight 03
From plan to purchase order
The MRP calculator turns a production plan into material requirements. Shortfalls become purchase suggestions, then purchase orders, then dated batches on receiving.
Highlight 04
Six reports
I wrote the report endpoints: daily production, production cost, stock movement, inventory valuation, profit and loss, and COGS, each exported to CSV.
Highlight 05
A rename across the stack
I renamed ingredients to materials and packages to retail packages across the API, the database and the dashboard: 216 files, moved with migrations.

Information