- Home
- Blog
- EDGEBIC How-To
- How to Add an ECN Number to a Product in EDGEBIC
To add an ECN number to a product in EDGEBIC by User Solutions, open the Products tab, select the product, click Edit, and enter the number in the ECN Number field. The same editor carries a Notes field for change detail and Manufacturer Part Number and Manufacturer Name fields for sourcing. These are reference fields for traceability: they record the change context against the product without affecting how it schedules.
An ECN number on the product record is the pointer that lets the shop trace a part back to the released change. It is deliberately lightweight, a label and a note, not a change-control system in its own right.
Before You Start
- The product exists.
- You have the ECN reference and a short description of what changed.
- You understand these fields are text, not versioned change control.
Step 1: Open the Product for Editing
Open the Products tab, select the product, and click Edit.
Step 2: Enter the ECN Number
Type the engineering change notice reference into the ECN Number field. This is the traceability pointer back to the released change.
Step 3: Add a Short Note
Use the Notes field for a brief description of what changed, for example Revised wall thickness per ECN. Keep it to a current-state summary, because this field is plain text with no version history and a new save overwrites the old text.
Step 4: Update the Manufacturer Detail If It Changed
If the revision came with new sourcing, update Manufacturer Part Number and Manufacturer Name. Then click Update to save all the fields.
What Changes When You Save
The ECN number, notes, and manufacturer fields are stored on the product and shown in its detail pane. Nothing about scheduling changes: routing, cost, and shift assignment are untouched. These fields are reference text, so the product plans exactly as before but now carries the change context anyone can read.
How to Check It Worked
- Reopen the product detail and confirm the ECN Number field shows the reference.
- Confirm the Notes field shows your short description and the manufacturer fields, if you changed them, are correct.
- If the change actually alters how the part is made, confirm you also updated the routing or cost, since the ECN field alone does not.
Common Mistakes
Expecting version history in Notes. The field is plain text and a new save overwrites it. Keep the authoritative change record in document control and reference it from the ECN field.
Assuming the ECN drives behavior. It is a traceability label. A change that alters how the part is built must be reflected in the routing or cost fields, not just the ECN number.
Confusing the product ECN with a routing note. The ECN and Notes fields sit on the product. A note about a specific operation belongs on the routing step instead.
Next
An ECN number on the product is the traceability pointer to a released change, and keeping the full history in document control keeps the record clean. For a note attached to a specific operation instead, read how to add a note to a routing step. To label products for quick filtering, read how to tag a product for search, and for the product setup itself, how to set up products. More single-task recipes are in the EDGEBIC how-to hub, and the platform overview is at /edgebic.
Expert Q&A: Deep Dive
Q: Engineering just released a revision on a part we build. What is the minimum I should capture on the product?
A: Put the ECN number in the ECN Number field so anyone on the product can trace back to the released change, and add a short line in Notes describing what changed at a glance, for example Revised wall thickness per ECN. If the revision came with a new manufacturer part number, update the Manufacturer Part Number and Manufacturer Name too. Save. This gives the shop a clear pointer to the current revision without turning the product record into a full change-history document, which belongs in document control.
Q: Two people edited the Notes field and one set of notes disappeared. How do I avoid that?
A: The Notes field is plain text with no version history, so the last save wins and earlier text in that field is overwritten. To avoid losing detail, keep the authoritative change record in your document control system and use the product's ECN Number field to reference the controlled document rather than pasting long histories into Notes. Reserve Notes for a short current-state summary. That way an overwrite loses at most a one-line summary, not the real change record.
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.
