Estimating for Epicor Prophet 21
An emailed request for quote becomes a priced quote in your own sheet, every line mapped to Prophet 21’s item master at your markups. Your estimator reviews it, sends it and enters it as a quote in Prophet 21.
Sales & estimatingUpdated Oct 202620 ERPs
See it work on Prophet 21.
Click through the steps. Fictional data, in Prophet 21’s terms; the real thing runs on Prophet 21.
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 Prophet 21.
A request for quote is an email with a material list or a set of drawings attached. The estimator reads it, finds each item in Prophet 21’s item master, checks cost, applies the house markup for that customer, and builds the quote in the same Excel sheet the yard has used for years. Then a revision comes in.
The desk writes over a thousand quotes a year. Most of the time goes into reading and retyping, not into the pricing 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 master, 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 master in Prophet 21, 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 Prophet 21, 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 a quote in Prophet 21. Revisions are a new version, not a new file.
How it connects to Prophet 21.
Lunica reads the item master and the customer master through a read-only login to the Prophet 21 SQL Server database: current cost, the price level and markup each account carries, and the quotes already in Prophet 21’s history, so a revision is priced against what went out last time. Supplier quotes you hold are read from the share or mailbox where you keep them.
Nothing lands in Prophet 21 without a person and nothing is sent on its own. The quote is written into your own sheet and PDF; the estimator sends it from their own mailbox. It goes into Prophet 21 as a Prophet 21 import or API call where one exists, or keyed by your team from what Lunica prepared, and Lunica records the number afterwards so the pipeline and Prophet 21 agree.
What a week looks like.
- Reading and retyping stop being the job.
- Every quote is priced on the same policy.
- Revisions keep their history.
- Pipeline, hit rate and expiring quotes in one view.
Questions
Does it send the quote?
No. It tells the estimator a quote is ready. The estimator sends it from their own mailbox.
Does it write to Prophet 21?
No. Lunica reads Prophet 21 and prepares the quote. A person enters it as a quote in Prophet 21, and Lunica records the number afterwards.
What about takeoffs from drawings?
Drawings are measured into regions a person confirms before anything is priced.
Will it match our sheet?
It writes your sheet, not ours. The output is the Excel file your customers already recognise, plus a PDF.
Pass-through quotes from a manufacturer?
Attached and priced from the supplier’s quote on file, with its validity date tracked.
Where does it run, and what does the model see?
On one Windows server inside your network, or beside your hosted Prophet 21, reading through a read-only login to the Prophet 21 SQL Server database. The model sees the request, its attachments and the items it is matching, not the whole item master.
Does it need a server?
Lunica runs on one Windows server inside your network, or beside your hosted Prophet 21, set up and maintained by Lunica. It reads Epicor Prophet 21 through a read-only login to the Prophet 21 SQL Server database. There is no inbound connection from outside your network.
What does Lunica read in Prophet 21?
The customer master, open items and terms, purchase orders and receipts, the item master, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Prophet 21?
Nothing lands in Prophet 21 without a person. What belongs in Prophet 21 goes back as a Prophet 21 import or API call where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Document Link. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Estimating is written for every system on the list. You’re reading the Prophet 21 version.
Lumber and building materials
Wholesale distribution
- Epicor Prophet 21
- Epicor Eclipse
- Infor CloudSuite Distribution
General business
Another system? Tell us which →
See it on your Prophet 21 data.
Thirty minutes. We walk the workflow on Prophet 21 data, then map it to yours.