- Home
- Blog
- EDGEBIC How-To
- How to Delete a Product in EDGEBIC (and What the C…
How to Delete a Product in EDGEBIC (and What the Cascade Takes With It)
To delete a product in EDGEBIC by User Solutions, open the Product tab, click the trash Remove button in the product's Actions column, and read the Confirm Delete prompt before you accept it. The delete is not blocked by references. It cascades, taking the product's entire Bill of Routing with it and flushing any production schedule rows tied to it.
That behavior is what makes this task worth thinking about for a minute. Deleting a work center is refused while anything still points at it, so the system stops you. Deleting a product does not stop you. It tells you what it is about to remove and then removes it, and there is no undo.
Before You Start
- Decide whether delete is really what you want. Delete is for records created in error. A product that has been built, quoted, or shipped has history hanging off it.
- Read the BOR column on the row first. It tells you whether a routing is part of the cascade.
- Check whether the product is used as a component elsewhere. A product can appear as a material step inside another product's routing. The confirmation names this product's own routing and schedule rows, not other routings that consume it.
- Have a database backup if the product has any history at all. Restoring from backup is the only route back.
Step 1: Open the Product Management Grid
Open the Product tab from the main navigation. The Product Management page lists your catalog with S.#, Product Id, BOR, Product Name, Unit, Lead Time, Size, Sale Price, Cost, Procured, Category, and an Actions column holding Edit and Remove.
The toolbar above carries the Category: filter, Manage Categories, Import, Delete Selected, and Add Product. The grid is grouped by category by default, and the search panel filters every column at once, which is the fastest way to find a part number you only half remember.
Step 2: Read the BOR Column Before You Click Anything
The BOR cell tells you what the cascade will take:
| Cell text | What it means for the delete |
|---|---|
| Active BOR | A routing exists and goes with the product |
| No BOR | Nothing routing-related to lose |
| ⚠️ 2 BORs (Legacy) in red | Legacy data left more than one routing on this product, and all of them go |
A red legacy row is usually a cleanup task rather than a delete candidate. Consolidating to a single routing is covered in how to find which products have no routing, which also explains how to filter the column to find every offender at once.
Step 3: Delete One Product
Click the trash Remove button in the product's row. The Confirm Delete prompt appears and spells out the consequences: if the product has a routing, deleting it also deletes its entire Bill of Routing configuration, and if it has been scheduled, the prompt names how many production schedule rows will be flushed.
Read those numbers. They are the clearest signal you will get about whether you are removing a stray test record or a working part of the plant.
Step 4: Delete Several at Once
Tick the checkbox on each row you want gone, then click Delete Selected in the toolbar. Confirm when prompted. This is the right path for a batch of test records created during setup, and the wrong path for anything you have not individually looked at, because a multi-row confirmation is easy to accept without reading.
Step 5: Or Leave the Record Alone
If the confirmation names a routing you use or schedule rows you recognize, stop. EDGEBIC's own guidance is that old products left in the list are harmless and cost nothing, so the ordinary answer for a discontinued item is to leave it and move it into an obsolete category so it drops out of your working view. For the full retire-without-deleting route, see how to deactivate a product without losing history.
What Changes When You Save
| Situation | Immediate effect | What goes with it |
|---|---|---|
| Product with No BOR, never scheduled | Row disappears | Nothing else |
| Product with Active BOR | Row disappears | Its entire routing configuration |
| Product that has been scheduled | Row disappears | Its routing plus the production schedule rows tied to it |
| You leave the record in place | Nothing | Nothing. Every reference stays readable |
The product also vanishes from every product dropdown across the application at once, including the order dialog and the routing pickers. This is the mirror image of how a customer delete behaves, where the orders survive and are simply unlinked, as how to delete a customer covers. Products do not work that way. Their dependents go too.
How to Check It Worked
- The product is gone from the Product Management grid. Clear the Category: filter with the ✕ button and search the Product Id to be certain you are not just filtered away from it.
- Open the BOR tab and confirm the product no longer appears in the routing selector.
- Check any routing that used the product as a material step. A component row pointing at a product that no longer exists is the one thing worth verifying by eye.
- Open the order dialog on Drive Schedule and confirm the product is absent from the Product (BOR) list.
Common Mistakes
- Accepting the confirmation without reading it. The prompt is the only place the cascade is spelled out, and it names real counts rather than generic warnings.
- Deleting to tidy the list. Category filtering does the same job with none of the loss.
- Deleting a product that is a component of something else. Check the routings that consume it before you remove it, not after.
- Assuming you can rebuild it. Recreating the product record is easy. Recreating its routing, and the schedule and cost history that referenced it, is not.
- Using Delete Selected on rows you have not individually inspected. Read each row's BOR cell first.
Where to Go Next
If the product is staying and only needs correcting, the field reference behind the editor is in how to add a new product, and the three values the BOR column can show are explained in what the BOR status buckets mean. Every task is indexed at the EDGEBIC How-To Library, and the product overview is at EDGEBIC.
Open the Product tab, find the row on the Product Management grid, and click the trash Remove button in its Actions column. To remove several at once, tick the checkbox on each row and click Delete Selected in the toolbar. A Confirm Delete prompt appears first. Read it before you accept, because it names what the delete will take with the product.
Yes. The confirmation says so directly: deleting the product also deletes its entire Bill of Routing configuration. It also flushes any production schedule rows tied to the product. Unlike a work center delete, which is refused while references exist, a product delete goes ahead and removes the dependent records with it. There is no undo.
Leave it in almost every case. An unused product record costs nothing, and keeping it means the routing, the finished jobs, and the cost history that reference it stay readable. Delete only when the product was created in error and has no history worth keeping. Moving retired items into an obsolete category keeps the working list tidy without throwing anything away.
Expert Q&A: Deep Dive
Q: We have about forty part numbers from a product line we discontinued two years ago. Clear them out or leave them?
A: Leave them. Forty rows cost you nothing but a slightly longer grid, and each one is the reason two years of finished jobs, cost rollups, and delivery history still make sense when someone reads them back. If the clutter genuinely bothers your planners, create a category called Obsolete or Discontinued, assign those forty products to it, and filter it out of the working view with the toolbar Category dropdown. You get a clean list and keep every record. Deleting them would take forty routings with it and flush whatever schedule rows survive, and none of that comes back.
Q: I created three test products while learning the system and want them gone before we go live. Anything to watch for?
A: That is exactly the case delete exists for. Records created in error with no history worth keeping are the clean scenario. Two things to check first. Look at the BOR column on each row so you know whether a throwaway routing goes with it, which is fine for test data and is the point of reading the confirmation. Then check whether any of the three appears as a material step inside a routing you actually intend to keep, because the confirmation names the product's own routing and schedule rows and does not speak to other products' routings that reference it as a component. Open those routings and check the material rows yourself. Once that is clear, tick all three and use Delete Selected.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
How to Create a Watched-File Integration in EDGEBIC
Create a watched-file integration in EDGEBIC: point it at the file your ERP drops, pick the target entity and import mask, set the debounce, and let a new file trigger the run.
How to Rehearse an Integration With the EDGEBIC Simulator
Use the built-in Simulator to provision demo data, watch real integration runs happen, and prove the mechanism before you point anything at a live ERP. Includes the tear-down rule.
How to Run an Integration Now and Pause All Schedules in EDGEBIC
Force one integration to run with Run Now, cancel a run in progress, disable a single definition, or tick Pause all schedules to stop every automatic sync for the session.
