How to Copy a Quote for a Similar Job in EDGEBIC

To copy a quote for a similar job in EDGEBIC by User Solutions you use the original as a template and re-key a new quote, because the current interface has no one-click duplicate command. You open the original to read its values, create a fresh quote with the add-quote action, re-enter the same product, customer, and quantity under a new unique number, and simulate it. This is the reliable way to get a second, independent quote without overwriting the first.

For the field-by-field creation walkthrough this builds on, read how to build and price a quote. This task is documented behavior of EDGEBIC, and the full task library is in the how-to hub. The base creation task is how to create a quote.

Before You Start

• An existing quote you want to reuse as a starting point.
• A new unique quote number for the copy, or you accept an auto-generated one.
• The product still has a valid routing, especially if you plan to re-simulate.

Step 1: Read the Original

In the Quote grid, find the original and open it with the ✏️ (Edit) action, or simply read its values in the grid columns: product, customer, quantity, unit price, markup, and dates. Do not change and save it here, because saving updates the original rather than making a copy.

Step 2: Create a New Quote from Those Values

Close the original without saving. Click ➕ Quote to open a blank Quote Configuration dialog. Re-enter the same Product (BOR):, Customer Id:, and Quantity: (or a new quantity for a tiered option). Set the pricing and dates to match, or adjust them for the new job.

Step 3: Give It a New Number and Save

Enter a new, unique quote number, or leave the field blank for an auto-generated Q####. Click Save. The copy lands in the grid as a Draft, fully independent of the original.

Step 4: Simulate the Copy

The copy carries only the preliminary routing estimate. Run the simulation on it (tick the row and click ▶️ Simulate) so it gets its own capacity-aware dates and cost.

Worked Example: Three Tiered Quotes for One Customer

The most common reason to copy a quote is tiered pricing: showing a customer 50, 100, and 250 units of the same product so they can pick a quantity. Here is the clean sequence.

Create the first quote normally with Quantity: 50 for Widget-A and save it, say as QUO-2026-020. Click ➕ Quote again, re-enter Widget-A and the same customer, set Quantity: to 100, give it a distinct number like QUO-2026-021, and save. Repeat once more at Quantity: 250 as QUO-2026-022. You now have three independent quotes.

Simulate all three. You can tick each row, or leave every checkbox unticked and click ▶️ Simulate to run every not-yet-simulated quote in the current filter. Then compare their Est. Hours, Est. Cost, and Margin % across the three rows. Note that the estimates will not scale in a perfectly straight line: the preliminary routing estimate does scale linearly with quantity, but the capacity-aware simulation can shift because the larger job sits differently against existing shop load and may push into busier days. That non-linearity is exactly the information tiered pricing exists to surface, so read the simulated numbers, not the preliminary ones, before you present the options.

What Changes When You Save

Saving creates one new quote row, separate from the original. Both quotes now exist and can be simulated, priced, and converted independently. Nothing on the production schedule changes. The original is untouched, which is the whole point of re-keying rather than editing.

Why Editing the Original Is Not Copying

It is worth being precise about why re-keying is the reliable path. When you open a quote, change its number and dates, and save, the system treats that as an update to the same record, because the record's identity is unchanged. There is no clone step. So "editing last year's quote to re-quote it" overwrites last year's quote, and its history is gone. The interface has no one-click duplicate command that would spin off an independent copy, so the safe workflow is to read the original for its values and build a fresh quote beside it.

One consequence to plan for: because you are re-entering the fields, nothing carries automatically. You retype the product, customer, quantity, pricing, and dates. That is more typing than a true duplicate would need, but it is also a chance to change exactly what should differ (a new quantity, a new requested date) while leaving the rest matching. And whatever you copy, the new quote carries no simulation of its own until you run one. If you later change the product on a copy that was already simulated, its stored hours and cost become stale for the new product, so always re-simulate after a product change.

How to Check It Worked

Confirm two rows now exist: the original and the copy, with different quote numbers. Both should carry the shared product and customer. After simulating the copy, confirm its own Start Date, End Date, and Est. Cost columns are populated rather than showing the original's numbers.

Common Mistakes and Gotchas

• Editing is not copying. Changing the number and dates on the original and saving overwrites the original. Always build the copy with the add-quote action so the first quote survives.
• A duplicate number is rejected. The copy needs its own unique number. Reuse of the original's number fails on save.
• The copy is not simulated. A fresh quote shows only the preliminary estimate until you simulate it. Do not read the original's dates onto the copy.
• Different quantity, different result. The preliminary estimate scales linearly with quantity, but the capacity-aware simulation can shift non-linearly because shop load moves. Simulate each tier separately.
• Contact fields do not follow the customer master. Per-quote contact person, email, and phone are copied from the customer when you pick them, then edited independently. Re-keying a quote copies whatever the customer record holds now, not what the original quote stored, so verify the contact on the copy if the customer's details changed since.

A note on the alternative some planners reach for: exporting quote data to a spreadsheet and re-importing does exist for bulk work, and the underlying interface can serve quote data programmatically, but for one or two similar quotes the re-key workflow above is faster and less error-prone than any export round trip. Reserve bulk methods for genuinely large batches where retyping is impractical.

Tiered quantity quotes are the most common reason to copy. Once all the copies are simulated, see the cost breakdown on each to compare where the hours and cost land at every quantity.