White Friday: up to 30% off your subscription 0days 0hrs 0min
Intagya
Pricing Blog Try free
← All articles

How do I change a product's components without losing the old version or mixing up orders?

| Intagya ERP Expert Team

How do I change a product's components without losing the old version or mixing up orders?
The short answer

In Intagya ERP, open the product components and press Request a change. Write the reason and what is added, removed or changes quantity, then Send for approval. A manufacturing manager approves, then presses Apply: the system makes a new version of the components and archives the old one. Open manufacturing orders on the old version are listed, and for each he chooses Update or Leave as is.

An iron door factory. The supplier raised the price of hinges, so the engineer found another supplier with a cheaper, slightly heavier hinge. He opened the product components and changed it, and changed the panel thickness with it to carry the weight.

Two weeks later a shipment came back from a customer. Half the doors had the new hinge with the old panel. Nobody knows exactly when the components changed, or why, or which orders were built with which version.

Why does editing product components cause trouble in production?

Because a direct edit erases what came before. The components become the new ones at once, with no trace of the old ones or of the reason.

Worse are the orders already on their way. A manufacturing order confirmed a week ago: is it built with the old or the new? If the system decides alone, or each supervisor decides alone, you get that shipment.

How do I request a change to a product's components?

Open Manufacturing, then Products, then the product components, and open the components of the product. At the top is a Request a change button, beside the reference a Version field, and a Changes button with the number of change requests on it.

Product components: the Request a change button, the Version field and the Changes button.
Product components: the Request a change button, the Version field and the Changes button. (Arabic interface, sample data)

In the change request you write the reason first, such as a cheaper supplier, a quality problem or a new design. Then the Components tab has one line per change: Add a component with its quantity, Remove a component, or Change quantity from the current one to the new one. When work steps are on, their tab lets you add a step, remove it or change its time.

The change request: the reason, one line per component added, removed or changing quantity, and the effective date.
The change request: the reason, one line per component added, removed or changing quantity, and the effective date. (Arabic interface, sample data)

The Effective date is optional. Fill it and the change applies from that day; leave it empty and it applies right after approval.

Who approves the change, and can it go through an approval path?

A manufacturing user writes the request and presses Send for approval. The state becomes To approve and the manufacturing managers get an activity to review it. The manager presses Approve or Refuse, and Back to draft returns the request for editing. Once sent, the request cannot be edited, so nothing changes behind the manager's back.

If you want each request to pass more than one person, such as the quality manager and then the finance manager, switch on the Product change path in the Approvals settings. It starts switched off; once on, every request goes through the path before it is approved.

What happens to the old version and to open manufacturing orders?

After approval a manufacturing manager presses Apply. The system makes a new version of the components with the next version number, archives the old one, and links both to the request. A New version button shows on the request, with a note of what was added, removed and changed.

Then an Open manufacturing orders tab shows the draft and confirmed orders that were on the old version. For each one the manager chooses Update to move it to the new version, or Leave as is. An order already in production keeps the version it started with, so nothing changes halfway down the line.

Do not update every order out of habit. An order for a customer who signed off a written specification may need to stay as it is, even if the new version is better.

How do I know who changed a product, when and why?

Open Manufacturing, then Products, then Product changes. One row per request with its number, the product, the version, the new version, who asked, the effective date and the state.

The product change history: each request with its old and new version, who asked and its state.
The product change history: each request with its old and new version, who asked and its state. (Arabic interface, sample data)

That history is what the door factory was missing. When a shipment comes back, you know which version it was built with, who changed it and for what reason.

Tomorrow, set one rule in the factory: nobody edits product components directly. Every change, however small, starts from Request a change. In a month the history will tell the story of every product.

FAQ

Is the old version of the components deleted?

No. It is archived and stays linked to the change request with the new version.

Do open manufacturing orders change by themselves?

No. A manufacturing manager chooses Update or Leave as is for each one, and an order already in production keeps its version.

Can I edit a request after sending it for approval?

No. Use Back to draft if it needs editing.

Who can approve a change?

A manufacturing manager, or the Product change path in the Approvals app once you switch it on.

Want to see IntagyaERP on your own workflow?

Book a demo, tell us how your business runs, and watch the system handle a real scenario from your company.

Book a demo