Job-stage tracking for small manufacturers: what we built for a jewellery workshop

Every make-to-order workshop we have worked with tracks jobs the same way: a whiteboard, a WhatsApp group, and one person who knows where everything is. It works until it doesn't, and it stops working at exactly the point the business starts to grow.

We built a production ERP for a jewellery manufacturer that had hit that point. This post is about what they had, what we built, and what we would tell any small manufacturer who is asking whether they need the same.

What the whiteboard is actually doing

In a job shop, every order moves through stages: design, customer approval, casting or fabrication, finishing, quality check, dispatch. The whiteboard answers one question: where is job 1042 right now?

The problems start with the questions it cannot answer:

• Which jobs have been in the same stage for more than three days?
• What is the customer waiting on from us, and what are we waiting on from them?
• How many jobs did we finish last month, and how long did each take?
• If the office manager is off sick, who knows what was promised to whom?

And the quiet one: how many hours a week does the owner spend answering "where is my order" on the phone?

For the jewellery business this was the daily reality. Design requests came in by email and WhatsApp. Customers approved designs on a phone screen. Production status lived with the workshop lead. Nobody was doing anything wrong; the information was simply spread across people instead of a system.

What we built

A custom ERP for the full production flow, from CAD design request through to dispatch. The pieces that mattered:

Six role-based dashboards. Admin, office staff, designers and customers each log into the same system and see a different screen. The designer sees a queue of requests and a place to upload CAD files. The office sees every job by stage with the ones that are late at the top. The customer sees only their own jobs and the approval that is waiting on them. Same data, rendered for the person looking at it.

QR-based job-stage tracking. Every job ticket carries a QR code. When a job moves from casting to finishing, the person doing the work scans it with their phone and picks the next stage. That one action updates the office dashboard, the customer's view and the job's history in real time. It takes less time than writing on the whiteboard, which is the only reason it gets done.

Design request, review and approval flows. A customer submits a request, the designer uploads a design, an internal reviewer checks it, the customer approves or asks for changes, all inside the system with the history kept. No more "which version did they say yes to?"

Mobile from design to dispatch. The workshop floor is not a desk. Everything the shop floor needs to do works from a phone.

The result for the owner is one screen that shows where every job is, what is late and why, without asking anyone.

What we would tell another workshop

You probably do not need an ERP. You need job tracking. The word ERP makes people think of six-month SAP projects. What most 10-to-50 person manufacturers need is a job-stage tracker with roles and a customer view. That is a much smaller thing.

Start with the stages, not the software. Before any build, we write down every stage a job passes through, who moves it, and what "done" means for each. Most workshops have never written this down, and the act of doing it usually removes two stages that only existed because of a person who left.

The scanning step is the whole project. If updating the system takes longer than the whiteboard, the workshop will go back to the whiteboard inside a fortnight. The QR scan works because it is faster than the alternative. Whatever you build, the update has to be a single action from the floor.

Give customers a window. The customer portal did more for the owner's time than anything else, because "where is my order" stopped being a phone call.

Off-the-shelf first, if it fits. There are good job-tracking tools for standard workflows. We build custom when the process does not fit any of them, which in jewellery (design approvals, metal and stone tracking, bespoke work) was the case. The honest test: if you can describe your process on a standard tool's demo without saying "except for", buy the tool.

What it costs and how long it takes

A focused job-tracking system for one workflow and two or three roles is an eight-to-twelve week build. A multi-role platform with design approvals, a customer portal and mobile, like the jewellery ERP, runs four to seven months. We scope it as a fixed-price pilot first: one process, end to end, in two to four weeks, so you see it running on the floor before committing to the rest.

The first step is a Process Audit, where we map the stages with you and come back with a written teardown and a fixed quote.

If your workshop still runs on a whiteboard and a WhatsApp group, you already know which job is late this week. The question is whether you want to be the only person who does.