What the Customer Actually Receives From an EDGEBIC Quote

The Send action on the quote grid produces the quote summary for the rows you have checked, and that summary is the only thing that reaches the customer. In EDGEBIC by User Solutions, everything else on the quote stays inside the building: the internal notes, the cost breakdown behind the price, and the reasoning behind the promised date. Knowing exactly which fields cross that line is what keeps a quote both honest to the customer and useful to the shop, and it is also why the status does not move itself when you press Send.

The line between inside and outside

A quote carries two audiences at once. The customer needs a number, a date, and terms. The shop needs to know how that number and date were reached, and why anyone chose them.

EDGEBIC keeps both on the same record and separates them by field rather than by document. The fields you fill when you create the quote fall into three groups:

The rule to remember is simple: customer notes print on the quote, and internal notes never leave the building. There is no accidental leak path between the two, so the split is worth using properly rather than dumping everything into one field.

Why the customer reference matters more than the quote number

Two identifiers sit near the top of a quote, and they point in opposite directions.

The quote number is yours. Leave it blank and EDGEBIC generates one; type your own when you need an external reference the customer will quote back at you. It matters downstream too, because when the quote converts, the manufacturing order is named from it, which is what lets anyone trace a job on the floor back to the enquiry that started it. That conversion path is covered in how a quote becomes an order.

The customer reference is theirs: the purchase order or enquiry number they will use when they reply. It is required, and for good reason. A quote that comes back accepted with no customer reference is a matching exercise nobody enjoys. The customer and sales order links behind it are covered in linking a quote to a customer and sales order.

The contact person and contact email are required as well, because a quote with no named recipient is not a quote yet, it is a draft estimate.

What Send does, and what it deliberately does not do

Send packages the summary for the rows you checked. If you check nothing, it covers every row in the current filter, which is convenient for a batch and worth being careful about.

What it does not do is more interesting:

• It does not change the status. A quote you just sent still reads Draft until you set it to Submitted yourself.
• It does not re-run the simulation. Whatever dates and costs are stored on the quote are what go out, current or stale.
• It does not touch the production schedule. No capacity is set aside because the summary left the building.

The first of those catches people out most often, and the fix is a habit rather than a setting: press Send, then set the status. Otherwise your grid fills with sent quotes that still read Draft, and the pipeline view stops telling you anything. The status meanings and the one status the system sets for you are in the quote lifecycle.

A send ritual worth keeping

Because Send happily packages a stale quote, the discipline belongs in front of it, not behind it. Four checks, in order:

1. Is the simulation current? Estimated dates and costs are a point-in-time picture of your shop load. If rates or capacity have moved since, the quote view says so and asks you to refresh and re-run. Do that first. See re-simulating a quote after a change.
2. Does the margin clear your floor? Read profit and margin before the number leaves, not after the customer accepts. See reading quote margin and profit.
3. Is the expiry date honest? The default window is short on purpose, because a capacity snapshot ages. See quote expiry dates.
4. Are the notes in the right fields? Anything you would not read aloud in a customer meeting belongs in internal notes.

Then send, then set the status.

A worked example

An estimator prepares a 200-unit quote for a customer whose purchase order number is already known. The quote number is typed by hand so the customer can quote it back. The contact person and email are the buyer who asked. Customer notes carry two lines: what the price includes, and that the date assumes material on hand at start. Internal notes carry one line nobody outside will ever read: that the plan assumes the larger mill, and that if that machine is claimed the date moves.

The simulation is fresh from this morning, so the dates and the cost still reflect today's load. Margin is comfortable. The estimator checks that single row, presses Send, then reopens the quote and sets the status to Submitted.

Two weeks later the customer accepts and quotes the reference back. The quote is found in seconds, the status goes to Approved, and one conversion turns it into an order named from the quote number. Nobody re-typed a quantity, a price, or a date, and the internal note about the mill is still there for whoever schedules it.

The takeaway

What the customer receives from an EDGEBIC quote is the summary Send produces for the rows you checked, built from the identification, commercial, and result fields you filled in, plus the customer notes. Internal notes stay inside. Send is a packaging step, not a workflow step: it will not refresh a stale simulation and it will not move the status, so re-simulate first and set the status to Submitted yourself. Get those two habits right and the quote grid stays an honest picture of your pipeline. Walk the whole workflow in the EDGEBIC quoting guide, see how the record hands off to production in how a quote becomes an order, see the platform on the EDGEBIC overview, and if you are coming from Resource Manager DB, start with the RMDB to EDGEBIC path.