Estimating for Epicor Eagle
A request for quote becomes a priced quote in the house sheet, lines mapped to Eagle’s item file and costed from it, priced by your markup policy. Your estimator reviews and sends; nothing is written to Eagle.
Sales & estimatingUpdated Oct 202620 ERPs
See it work on Eagle.
Click through the steps. Fictional data, in Eagle’s terms; the real thing runs on Eagle.
Attached material list for the detached garage at Lot 14 Birchwood. Need pricing by Friday.
Customer, project, due date and the material list, from the estimating mailbox.
The problem, as it happens in Eagle.
The estimating desk on Eagle lives in two places: the quote in Excel, because that’s the sheet customers know, and the estimate or bid keyed into Eagle afterwards so the yard can convert it. The material list arrives as an email attachment, and every line gets found in the item file by hand.
A thousand quotes a year, a revision on many of them, and the desk’s time goes into reading and retyping instead of into the margin decisions that win the job.
How it works.
- 1
The request becomes a card
Forwarded into the estimating mailbox or opened by hand: customer matched to the customer file, project, due date, attachments. The estimator sees it on the desk with the due date on it.
- 2
Lines are read and mapped
Items read out of the material list or taken off the drawings, mapped to the item file in Eagle, with the matches a person should check flagged. A drawing is measured into regions the estimator confirms before anything is priced.
- 3
Costed and priced
Cost from Eagle, price from your versioned markup policy by customer and category. Supplier quotes you hold are priced from where you have them. The estimator sees the margin per line, not just the total.
- 4
The quote, in your sheet
The house Excel sheet and its PDF, versioned. The estimator reviews, downloads and sends from their own mailbox, and enters it as an estimate in Eagle. Revisions are a new version, not a new file.
How it connects to Eagle.
Lunica reads Eagle’s item file for cost and description, and estimates, bids and orders from order history, read-only through the Eagle data warehouse, so hit rate and quote history are real. Each line from the material list or the drawing is mapped to an Eagle item; uncertain matches are flagged for a person.
Nothing is written to Eagle. The quote is built in your Excel sheet and its PDF, versioned; the estimator downloads it and sends it from their own mailbox. A stock-only quote keyed into Eagle afterwards is recorded by its estimate number. Writing to the file share stays off unless you switch it on.
What a week looks like.
- Reading and retyping stop being the job.
- Every quote priced on the same markup policy, with the version that priced it.
- Supplier quotes on file, with validity dates, priced from where you have them.
- Pipeline, hit rate and expiring quotes in one view.
Questions
Does it key the estimate into Eagle?
No. A person does, if the job needs an Eagle estimate; Lunica records the estimate number against the quote.
Does it send the quote?
No. It tells the estimator a quote is ready. The estimator sends it from their own mailbox.
Will it use our sheet?
Yes. The output is the house Excel sheet and its PDF, not a Lunica template.
What about drawings?
Measured into regions a person confirms before anything is priced.
Where does cost come from?
From Eagle’s item file, read when the quote is built.
The same workflow, on another ERP.
Estimating is written for every system on the list. You’re reading the Eagle version.
See it on your Eagle data.
Thirty minutes. We walk the workflow on Eagle data, then map it to yours.