What Is a Product Id? EDGEBIC Master Data Definition

A product id is the short, stable identifier that stands for an item everywhere it appears: on routings, on manufacturing orders, on quotes, on the schedule and on every report. It is the one required field on a product record in EDGEBIC by User Solutions, and it is deliberately separate from the descriptive product name, which holds a longer label or a formal part number.

This entry is part of the EDGEBIC glossary series introduced on the platform overview; the broader vocabulary index sits in the manufacturing glossary. It sits beside the other reference fields on a product, including the unit of measure.

How a Product Id Works

A stock ticker makes the split obvious. AAPL is four characters, never changes, and is what every screen prints because a screen full of prices has no room for "Apple Inc." and no need for it. The full company name exists too, and it is the right label on a contract. Neither one replaces the other, and nobody is confused about which is which because the roles are clearly different.

Product identity in a manufacturing system needs the same two roles, and for a very practical reason: a Gantt bar is a rectangle a few centimeters wide. Whatever you put in the identifier field is what a planner reads there, in every grid row, on every report line, and on the shop paperwork. Long structured part numbers turn a schedule into a wall of near-identical strings that must be read character by character.

So the two fields divide the work:

• Product Id is required and short. Widget-A, Frame-S. It is what the schedule, the grids and the routing all display.
• Product Name is optional, unique when set, and auto-generated by default. Edit it to hold your own part number, WGT-A-001, or a longer descriptive label.

Everything else on the product record, the unit of measure, sale price, size, description, weight, country of origin, lead time, rollup cost and category, is attribute rather than identity. Those describe the item. The id names it.

Because the id is what every other record points at in the reader's eyes, stability matters more than precision. An id chosen to be readable and then left alone is worth more than one that is perfectly systematic and gets revised twice a year.

A Concrete Example

A fabricator sells a standard bracket that their customer's drawings call BRK-4471-02-A.

Setting the product id to that string would be defensible and would make the schedule hard to read. Three similar brackets would appear on the Gantt as BRK-4471-02-A, BRK-4471-02-B and BRK-4471-07-A, which a planner has to parse rather than recognize.

The better arrangement:

Now the schedule reads Bracket-A, Bracket-B and Bracket-C at a glance, and the formal number is one click away on the product record whenever it needs to match a drawing, a customer order or an ERP export.

Six months later the shop decides Bracket-A should read Bracket-STD. Because the product is already used by a routing and by scheduled jobs, saving the change raises the Update Related References prompt. Answering Yes propagates the new label through the routing, the Gantt and the work center details in one move. Answering No would leave the product record saying one thing and the routing saying another, which is the state nobody wants to inherit.

How EDGEBIC Uses the Product Id

The id is the label the planner-facing surfaces are designed around, and a few product behaviors follow from that:

• A new product appears immediately in every product dropdown across the application once saved, so the id is chosen before it is used rather than after.
• Several report panes head their column "Product Id" explicitly. That relabeling was made because the column shows the identifier, not a descriptive name, and planners were reading it as a description. On the Sales Order Progress report the neighboring column is headed "End Product (BOR)", which names the end product of the routing rather than repeating the identifier.
• Deactivating beats deleting. The standard master data rule applies here as everywhere else: unticking active hides an item from new-order and quote pickers while every historical link and every report row stays intact.

For the full product form and the planning attributes that sit beside the identity fields, see products and planning attributes explained, and for the walkthrough of creating one, how to add a new product. Where a product is the finished article a job is raised against rather than a component, the term to know is the end item, and for the grouping that organizes the catalog for filtering and reporting, see what is a product category in manufacturing software.