There is a moment in most made-to-order businesses where somebody says "surely there is software for this already". There is. It is very good. It is also built on an assumption that does not hold for you, and the gap does not show up during the demo — it shows up eighteen months later, when a customer comes back.
The assumption
Conventional production software is organised around a specification that exists before the order. There is a part, the part has a number, the number has a bill of materials, and an order is a request for some quantity of that part. Everything downstream — planning, purchasing, costing, quality — hangs off that stable identity.
Made-to-order inverts it. The specification does not exist before the order; it is created during the order, usually in a room with the customer, from measurements taken that day. There is no part number because there is no part until somebody is measured. Quantity is one, forever.
You can force this into a catalogue-shaped system. Most businesses do, by creating a generic product code and putting the real information in a notes field. It works for about a year, and then someone needs to answer a question that the notes field cannot answer.
The question that breaks it
A customer returns and something is wrong. Maybe it does not fit any more. Maybe it never quite did.
To respond you need to know what you measured, when, what you made from those measurements, and what has changed since. That is not an order history. It is a chain of records where each link has to still say what it said at the time.
Here is the subtle part, and it is the thing we spend the most design effort on in platforms like this: the customer record and the measurement record want to behave differently. The customer record should be current — their latest weight, their latest size, their current phone number. The measurement record must be frozen — what was true on the day, even if everything about them has changed since.
If your system has one of these, you have a problem. If it has both, someone had to decide, field by field, which is which, and what happens when a new measurement updates the customer but must not update last year's file.
What else quietly does not fit
Rework is not an exception. In made-to-order a percentage of items come back for adjustment or remake, and it is a normal, costed part of the process rather than a quality failure. Your system needs remakes as first-class objects that inherit from the original — and an explicit answer about what they deliberately do not inherit.
The floor is not always online. Measuring happens in consulting rooms, at partner sites, in places with thick walls. If a member of staff cannot start an appointment because the connection dropped, the software has failed at the only moment that mattered.
Who may see what is not a job title. In a business with branches, brands and more than one legal entity, access is a combination of dimensions rather than a role, and personal or medical data usually needs its own separate permission on top.
So do you build?
Not automatically. If your volume is low and your process is stable, a spreadsheet and a good filing habit genuinely beat a system nobody has time to maintain. We have said so to people who arrived expecting a quote.
The point at which custom starts to pay is usually one of these: you have more than one location and they have started keeping different records, rework is costing real money and you cannot say why, or somebody has asked a question about history that you cannot answer from what you have.
If you recognise one of those, describe your process to us — not your feature wishlist, your process. What comes back will be a range with the assumptions attached, and an honest opinion on whether an off-the-shelf system would serve you better.