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