How to Set a Product Cost in EDGEBIC

To set a product cost in EDGEBIC by User Solutions, open the Product tab, click the edit button on the product's row, enter the new Rollup Cost and Sale Price, and click Save. Both fields sit on the Product Configuration dialog and both feed quoting immediately. Existing quotes keep their original figures. This post covers the single task of changing the numbers. For what every product field does, read how to set up products in EDGEBIC.

Before you start

• The product exists in the catalog. If not, see how to add a new product.
• You know which number you are changing. Rollup Cost is the per-unit cost including materials and labor. Sale Price is the per-unit revenue.
• You have the source figure to hand: the supplier quote, the revised standard cost, or the new price list.
• If the change spans more than about twenty products, plan an import instead of a series of dialogs.

Steps

1. Open the Product tab from the main navigation.
2. Find the product using the search panel above the grid, or the toolbar's Category filter.
3. Note the current values in the Cost and Sale Price columns before editing, so you can confirm the change afterwards.
4. Click the edit button in the row's Actions column. The Edit Product dialog opens.
5. Enter the new Rollup Cost per unit.
6. Enter the new Sale Price per unit if the revenue side is changing too.
7. Click Save.

If the price you entered is below the cost, expect the warning "Unit price is less than unit cost. You may be selling at a loss." It is a check, not a block. Confirm the numbers and save if the loss is intentional.

What changes when you save

The important boundary is the second and third rows. A quote is a document you sent a customer, so it holds the figures it was built with. Anything you simulate after the save uses the new values. That split is what keeps historical margin reporting honest.

Cost also does not feed the scheduling engine. Changing a price never moves a job. Cost belongs to quoting and reporting, and the scheduler ignores it entirely, which is why a price revision is one of the safest master-data edits you can make mid-week.

How to check it worked

1. Confirm the new figures in the Cost and Sale Price columns of the product grid.
2. Build a quote for the product, or re-run the simulation on a draft quote, and expand the cost breakdown. The material and unit figures should reflect the new rollup cost.
3. Check the margin percentage on the simulated quote. If it barely moved on a large cost change, the quote is probably an existing one holding historical figures rather than a fresh simulation.
4. If the product is routed through a work center whose rate recently changed, review the labor cost stored on those routing steps too. That value is inherited at step creation and does not follow later rate changes.

Common mistakes

Expecting sent quotes to update. They will not, by design. Re-simulate or re-quote if the customer needs the revised number.

Leaving rollup cost blank on a quoted product. A blank cost makes the margin look excellent and is the single easiest way to quote a job at a loss. Keep the number current on anything you quote.

Editing 200 products by hand. A plant-wide revision belongs in an export, a spreadsheet edit, and a re-import with a preview step. The dialog is for the trickle.

Forgetting the labor side. The product's rollup cost is per unit. Work center hourly rates drive the labor component of the rollup, so a rate change can leave stored routing values stale even when the product record is perfect.

Once costs are current, keep the rest of the record in step: how to change a product's lead time covers the field that changes promise dates. More single-task recipes are indexed in the EDGEBIC how-to library, and the EDGEBIC product page shows how quoting and finite capacity scheduling share the same data.