Finding One Quote in a Long List in EDGEBIC

Three controls narrow the EDGEBIC quote grid: a status filter, a customer selector, and a sales order selector, and a reset clears all three at once. In EDGEBIC by User Solutions they combine rather than replace each other, so the fastest way to find one quote among hundreds is usually two filters at a time. There is a second reason to care about which filter is active: the grid's bulk actions work on the current filter when no rows are checked, so the filter is also the boundary of what those buttons will touch.

The grid is a pipeline, until it is an archive

Early on, the quote list is short enough to read. Then a year passes, and the same grid holds every enquiry the shop ever priced, won or lost. The controls above it are what keep it usable.

They stack. Pick a customer and then drafts only, and you have that account's live shortlist. Pick a customer and then converted only, and you have their order history as it came through quoting.

The two identifiers, pointing in opposite directions

Filtering gets you to a handful of rows. Identifying the right one comes down to two fields that are easy to confuse.

The quote number is yours. Leave it blank when creating the quote and EDGEBIC generates one; type your own when the customer needs an external reference. It also names the manufacturing order at conversion, which is what lets a job on the floor be traced back to the enquiry that produced it.

The customer reference is theirs: the purchase order or enquiry number they will quote back at you. It is a required field, and this is exactly why. When a customer replies six weeks later with nothing but their own PO number, the reference is the only identifier you both hold. Filter to the customer, scan the reference column, done. The wider relationship between quotes, customers, and sales orders is in linking a quote to a customer and sales order.

Why the filter is also a blast radius

Here is the part worth internalizing. The grid's bulk actions follow a single rule: with rows checked they act on the checked rows, and with nothing checked they act on the eligible rows in the current filter.

That is deliberate and often exactly what you want. Filter to one customer's drafts, press one button, and the whole shortlist refreshes against today's shop load. The batch path is covered in how to simulate multiple quotes at once.

It becomes a problem only when the active filter is a leftover from a different task. The two habits that prevent it:

• Read the filter before you press a toolbar button. Especially conversion, which is one-way.
• Check the rows when you mean specific rows. Explicit beats implicit whenever the action writes something.

A stray simulation is harmless because simulating writes nothing to the production schedule. A stray conversion is not, because a converted quote cannot be converted again. See how a quote becomes an order for what conversion commits.

Filters only work if the statuses are honest

The status filter is the most useful of the three and the first to become useless, because it depends entirely on discipline elsewhere.

If quotes are created as drafts and never moved, every row reads Draft and the filter separates nothing. The pool of things genuinely still being prepared is indistinguishable from two years of dead enquiries. At that point people stop filtering and start scrolling.

The fix is not a feature, it is a habit: set the status when the state changes. Sent means Submitted, declined means Rejected, past its validity window means expired. Do that and Draft stays the short live list it is meant to be. The statuses and their meanings are in the quote lifecycle, and the reason quotes age at all is in quote expiry dates.

A worked example

A buyer calls about a quote from last month. All they have is their own purchase order number and the name of the part.

Set the customer selector to their account. The grid drops from several hundred rows to fourteen. Leave status on all, because the point of the call is unknown yet: the quote might still be a draft, or it might already be converted and the buyer is chasing the job rather than the price.

Scan the customer reference column, find the purchase order number, and open that row. Its status reads Submitted, the estimated dates and cost are from a simulation run five weeks ago, and the validity window has passed.

That is now a re-simulation job rather than a lookup job, because a five-week-old promise date is a picture of a shop that has moved on. Re-simulate against today's load, check the margin, then answer the buyer with a date you can defend. See re-simulating a quote after a change.

Before moving on, press reset. The next person to touch the grid, or you in twenty minutes, should not inherit a customer filter nobody set on purpose.

The takeaway

Finding one quote among hundreds in EDGEBIC comes down to three combining controls, status, customer, and sales order, plus a reset that clears them, and two identifiers that point in opposite directions: your quote number and the customer's reference. The filter does double duty as the boundary of any bulk action taken with no rows checked, so read it before pressing anything and check rows when you mean specific rows. And remember that the status filter is only as useful as the statuses are honest, which makes setting the status part of the job rather than an afterthought. Walk the whole workflow in the EDGEBIC quoting guide, see the status meanings in the quote lifecycle, see the platform on the EDGEBIC overview, and if you are coming from Resource Manager DB, start with the RMDB to EDGEBIC path.