How to Rename a Product in EDGEBIC

To rename a product in EDGEBIC by User Solutions, edit the product, change the identifier, and answer the update related references prompt with yes so the new name reaches routings, the Gantt, and work center views. That prompt is the whole task. The rename itself is a text edit; the answer decides whether the shop floor and the office are reading the same label tomorrow.

The prompt appears only when the product is already in use, which is exactly when it matters. A product nobody has routed or scheduled renames silently and nothing else needs to happen.

Before You Start

• Be sure a rename is the right move. A genuinely different part should be a new product, not a renamed one, because renaming rewrites the label on the old part's history.
• Know which field you are changing. The identifier is what planners read on the Gantt and in every grid. The secondary name is where formal part numbers usually live, and it must be unique.
• Agree the new value first. Renaming twice doubles the cleanup.
• Check for import masks. A mask that maps a file column to the old value needs updating separately.

Step 1: Open the Product

Open the Product tab, find the product, and click the edit control on its row. The Product Configuration dialog opens.

Step 2: Change the Right Field

Two fields carry names, and they do different jobs:

If the goal is that the schedule reads correctly, the identifier is the field to change. If your organization runs formal part numbers alongside a short shop name, put the formal number in the secondary name and leave the identifier alone.

Type the new value.

Step 3: Save and Read the Prompt Carefully

Click Save.

If routings or scheduled jobs already use this product, an Update Related References? prompt appears with three answers:

• Yes. Propagate the new name everywhere it is stored alongside the product: the routing, the Gantt, and work center detail views. This is the answer you want in almost every case.
• No. Update only the product record. Everything else keeps showing the old text, deliberately.
• Cancel. Do not save at all. The product stays exactly as it was.

Answer Yes unless you have a specific reason not to.

Step 4: Check the Surfaces That Matter

Do not take the prompt's word for it. Look at the three places the old name lived:

1. The routing. Open the product's routing and confirm the end product node and any material references read correctly.
2. The Gantt. Open a scheduled job for this product and read the bar labels.
3. A work center detail view. Open a machine that runs the product and confirm its detail list shows the new name.

Step 5: Update Anything Outside the Application

A rename inside the system does not reach the things that feed it.

• Import masks. A mask that maps a spreadsheet column to the old product value will stop matching, and depending on the mask it may create a new product rather than update the existing one.
• Documents and travelers printed before the change still carry the old label.
• The shop floor. Tell people. A part with two names in circulation is a mispick waiting to happen, and no software change prevents that.

How to Check It Worked

1. The grid shows the new name in the product list.
2. The pickers offer the new name when creating an order or a quote.
3. A scheduled job reads correctly on the Gantt without a refresh trick.
4. The routing agrees. Open the routing and confirm no node still shows the previous text.
5. A re-run import still matches. If a mask feeds this product, run a small test file before the next full load.

Common Mistakes

Answering no and moving on. The most common cause of a stale name on the Gantt. The fix is a re-save with yes, and it costs nothing except the time between the mistake and noticing it.

Renaming instead of creating a new product for a new revision. History for the old revision gets relabeled as the new one, and the two stop being separable in reporting.

Changing the identifier for cosmetic reasons. It is the label planners read on the schedule and the value import masks match on. Stability is worth more than tidiness.

Forgetting the import mask. A rename inside the application and a file that still carries the old value is how a duplicate product appears on the next import.

Renaming mid-week on a busy part. Do it when the floor can be told, not while three jobs for it are running.

Next Steps

If a product is being retired rather than renamed, how to deactivate a product without losing history in EDGEBIC is the safe route. The equivalent job on the resource side has its own quirks: how to rename a work center in EDGEBIC covers the routing references that follow a machine's identifier. More task guides live on the EDGEBIC how-to hub, and the EDGEBIC product page shows how product master data feeds the schedule.