Estimating for Sage 100
An emailed request for quote becomes a priced quote in your own sheet, every line mapped to Sage 100’s item record at your markups. Your estimator reviews it, sends it and enters it as a sales order quote in Sage 100.
Sales & estimatingUpdated Oct 202620 ERPs
See it work on Sage 100.
Click through the steps. Fictional data, in Sage 100’s terms; the real thing runs on Sage 100.
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 Sage 100.
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 Sage 100’s item record, 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 maintenance record, 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 record in Sage 100, 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 Sage 100, 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 sales order quote in Sage 100. Revisions are a new version, not a new file.
How it connects to Sage 100.
Lunica reads the item record and the customer maintenance record through Sage 100’s ODBC driver, under a user that can only read: current cost, the price level and markup each account carries, and the quotes already in Sage 100’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 Sage 100 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 Sage 100 as a Sage 100 import or Visual Integrator job where one exists, or keyed by your team from what Lunica prepared, and Lunica records the number afterwards so the pipeline and Sage 100 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 Sage 100?
No. Lunica reads Sage 100 and prepares the quote. A person enters it as a sales order quote in Sage 100, 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, beside the Sage 100 server, reading through Sage 100’s ODBC driver, under a user that can only read. The model sees the request, its attachments and the items it is matching, not the whole item record.
Does it need a server?
Lunica runs on one Windows server inside your network, beside the Sage 100 server, set up and maintained by Lunica. It reads Sage 100 through Sage 100’s ODBC driver, under a user that can only read. There is no inbound connection from outside your network.
What does Lunica read in Sage 100?
The customer maintenance record, open items and terms, purchase orders and receipts, the item record, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Sage 100?
Nothing lands in Sage 100 without a person. What belongs in Sage 100 goes back as a Sage 100 import or Visual Integrator job where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Paperless Office. 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 Sage 100 version.
See it on your Sage 100 data.
Thirty minutes. We walk the workflow on Sage 100 data, then map it to yours.