How to Deactivate a Product Without Losing History in EDGEBIC

To deactivate a product in EDGEBIC by User Solutions without losing history, edit the product and untick its active flag rather than deleting the record. The product disappears from the dropdowns used to create new orders and routings, while every historical manufacturing order, routing, and schedule row that references it stays exactly as it was. Deleting does the opposite: it cascades. For the wider list of catalog errors and their symptoms, read product setup mistakes in EDGEBIC.

Before you start

• Confirm the product is genuinely retired. Check whether any open manufacturing orders still reference it, because deactivation does not cancel them.
• Know which action you want. Deactivating hides the product from new work. Deleting removes the product, its routing configuration, and the schedule rows tied to it.
• Have the replacement part identified if this is a supersession, so planners have somewhere to go when the old identifier stops appearing.
• Note that you can reverse a deactivation at any time. You cannot reverse a deletion from inside the application.

Steps

1. Open the Product tab from the main navigation.
2. Find the product using the search panel above the grid.
3. Click the edit button in the row's Actions column to open the product dialog.
4. Untick the product's active flag.
5. Click Save.

The record stays in the database. What changes is where the product offers itself.

If your build's product form does not expose an active flag, the equivalent retirement practice is simply to leave the old product in place and stop ordering it. Old products cost nothing to keep, and that is a safer position than reaching for the delete button.

What changes when you save

Compare that with deleting the same product. The confirmation prompt spells out both consequences: the product's entire routing configuration goes with it, and the production schedule rows tied to the product are flushed. There is no undo path inside the application.

How to check it worked

1. Open the manufacturing order dialog and check the product dropdown. The deactivated product should not be listed.
2. Open the routing module's product selection and confirm the same.
3. Open a completed job that used the product and confirm it still displays correctly with its operations and dates. That is the history you were protecting.
4. Check the open order list for anything still referencing the product. Deactivation left those in place deliberately, so decide whether to complete or cancel them.

To bring the product back, filter the product grid to show inactive rows, open the record, tick the active flag, and save. It returns to every dropdown immediately with its routing and history untouched.

Common mistakes

Reaching for delete because the list is long. A long catalog is a filtering problem, not a deletion problem. Group or filter the grid instead, and leave retired products where they are.

Assuming deactivation cancels open work. It does not. Orders raised before the change keep running through the schedule. Handle them separately.

Deactivating a component that other products still consume. If the product appears as a material inside another product's routing, retiring it leaves that routing pointing at an item nobody will reorder. Check the routings that consume it before you retire it.

Deleting a product to clear a routing problem. If the goal is to fix a broken or duplicated routing, fix the routing. Deleting the product takes the routing and the schedule rows with it and solves nothing you could not have solved in the routing module.

Retiring products pairs naturally with a catalog audit: how to find which products have no routing is the check that usually surfaces the candidates. All the single-task recipes live in the EDGEBIC how-to library, and the EDGEBIC product page shows how clean master data feeds a finite capacity schedule.