Compare make-to-order software by following a revised order through materials, assembly and completion, then assess the wider costing and implementation scope.
A customer approves a different component after assembly has started. The production team now has to establish which units the change covers, what to do with materials already committed and which instructions the floor should follow. A revised quotation leaves those production decisions unresolved.
If you are a production director replacing a spreadsheet-led process for configurable assemblies, use that situation to compare make-to-order software. Ask each supplier to follow an order through normal production, then revise it after partial completion. The demonstration should show how the system preserves completed work and applies the approved change to the remaining units. Assess that evidence alongside the engineering, planning and costing requirements of your operation.
What the software has to carry into production
Make-to-order means producing or finishing goods in response to an order. It can include components or earlier production stages made for stock. Configure-to-order describes choosing a variant from an established set of options; engineer-to-order involves designing the product for the order. A manufacturer can combine these approaches, so describe which choices your customers make and which require engineering work.
An agreed specification establishes what the customer will receive. For an assembly, the bill of materials identifies its components and quantities, while the work sequence describes how to make it. Planning establishes the material and production requirements. Purchasing obtains what is needed, and reservations assign available material to the work. Releasing a production order makes its instructions available for execution under the business’s release rules.
In a straightforward assembly order, the team then follows those instructions and records what it completes. The required checks establish whether the assemblies are acceptable for delivery. Completion records need to identify the specification followed, so the business can compare what it agreed to supply with what it made. Dispatch and delivery need their own records: finishing assembly does not establish that the goods have left the factory or reached the customer.
Before material is committed or work begins, a specification change may only require a revised plan. Once purchasing or assembly is under way, the old plan has physical and commercial consequences. Parts may already be on order, and completed units contain the components the team was instructed to use. The software needs a controlled way to decide what changes and what remains valid.
Revise an order after part of it is complete
In this illustrative example, a confirmed order is for 40 assemblies using component A. Materials for all 40 are reserved. The team completes 10 assemblies, then the customer approves component B for the remaining 30. The first 10 remain acceptable as built.
The order now needs to describe two accepted specifications with different scopes. The completed 10 must retain their record of using A. The remaining 30 need instructions that require B. The supplier may represent this through separate jobs, order lines or another supported structure; ask it to show how each quantity retains the correct specification. Changing A to B on the original record without preserving that distinction would make the history describe something the team did not build.
Material decisions must follow the same scope. The unused A reservations for the remaining 30 can be released once the responsible person approves that treatment. That releases an allocation; it does not undo a supplier purchase or remove stock from the building. If material has already been ordered, purchasing still needs to decide what happens to that commitment. The A used in the completed 10 remains part of their production record.
For the remaining 30, the planner needs to establish B’s availability and the work still required before confirming the revised delivery commitment. A new date entered on the sales order does not establish that those components will be ready. Ask the supplier to show the material requirement and the basis for the remaining production dates, including any decision that needs to happen outside its software.
Then attempt to complete one of the remaining assemblies using an instruction issued before the change. The system should hold that attempted completion for a defined decision. The responsible person needs to establish what was actually built and whether it can be accepted or needs further work. Silently accepting the old instruction would let the order appear to satisfy the change while an affected unit still follows A.
After the revised work is complete, the records should account for all 40: 10 accepted under the original specification and 30 under the revised one. They should also show the instruction applied and the required completion evidence. An order history that merely says someone edited the component cannot establish those facts.
Compare suppliers on the same evidence
Give each shortlisted supplier the same starting order and the same change. Agree the expected result before the demonstration, including who approves the change. Follow it through the planner’s view, the operator’s instruction and the completion record using these criteria.
Criterion | What to test | Evidence to expect |
|---|---|---|
Revision scope | Apply B to the remaining 30. | The completed 10 retain A; each quantity has an identifiable specification. |
Material commitments | Approve the revised allocation. | Unused A reservations are released, purchases remain accounted for and B’s availability informs the remaining dates. |
Remaining work | Open a remaining job and attempt completion against its old instruction. | The revised instruction requires B; an old-instruction attempt waits for a defined decision. |
Completion evidence | Trace a finished quantity back to its work. | The applied specification and required check results remain available. |
Maintenance responsibility | Ask how a later approval-rule change would reach the floor. | A named owner, agreed handover/support scope and a way to test the changed process. |
Record the product version, demonstration date and relevant dated documentation. For each requirement, distinguish existing configuration, a supported extension and work that needs a separate implementation. Include who will build and test that work in the proposal. Keep promised behaviour separate from what the supplier has demonstrated, with unresolved questions available for follow-up.
Keep the wider purchase in scope
Your shortlist also needs to reflect whether you configure existing products or design new ones, how you plan material supply and how you schedule the required people and equipment. If a manufacturing suite already represents these requirements and your revision rules, its established workflows may be a good fit.
Have the people responsible for costing assess how a changed specification affects the quotation and the comparison between estimated cost and work actually performed. The completed assemblies must retain their original production record; unused material or additional work needs an agreed cost treatment. Establish where the customer’s price agreement is recorded and how production information reaches the accounting system.
Compare the full delivery scope and cost of each proposal, including system connections, moving data and open orders, testing and training. Include ongoing charges and the cost of later changes. Licence prices alone may describe different amounts of delivered work, so assess the proposal against the responsibilities recorded during the evaluation.
Running the agreed production process in Keel
Keel is an operations platform shaped around how your team works. For assembly production, that could mean opening a released job to find the applicable specification, the next work to do and the checks needed to finish it. As the team records its work, the production director can see what is complete and what still awaits action. The business’s own release and completion rules determine when a job can move on.
Applied to our example, that process would keep the completed assemblies’ history intact and guide the remaining work through the approved change to B. The team would see which instructions apply and whether a decision is still needed before continuing. You can also improve how revisions reach the floor: reshape the approval steps and job view together, so operators receive the new instructions and completion follows the revised rules.
Keel leads the work to shape and test that process, connect retained systems and agree customer handover. The revision behaviour is implemented for your operation; agree which material-planning, engineering, costing and accounting functions the project will cover and which will remain elsewhere. Our guide to what Keel supplies and what the implementation builds explains those responsibilities.
To discuss whether that approach fits your requirements, bring an order revision to Keel, including its production consequences and the systems you expect to retain.
