Window and Door Quotes for NetSuite
A window or door manufacturer’s quote read line by line into cost and drafted as an estimate in NetSuite’s terms, with options and lead times carried over. Your salesperson reviews it and enters it.
Sales & estimatingUpdated Oct 202620 ERPs
See it work on NetSuite.
Click through the steps. Fictional data, in NetSuite’s terms; the real thing runs on NetSuite.
Received Oct 20 from Cascade Millwork · 14 units · 15 lines with options · Lead time 4 to 5 weeks · valid through Nov 19
Totals check: $18,432.60 on the PDF, $18,432.60 read
Units: 9 double-hung, 3 casement, 2 fixed
Options: low-E, grilles between glass, white interior
Freight: $340.00, listed as its own line
A model reads the PDF twice and checks its totals against the document.
The problem, as it happens in NetSuite.
A window package comes back from the manufacturer as a forty-page PDF: every unit with its options, a price, a lead time. The salesperson retypes it into an estimate in NetSuite line by line, applies the markup from memory, and tries to keep the grille pattern and the jamb depth straight between the two documents.
A missed line is a window that never gets ordered. A markup applied to the wrong column is a job sold at cost. The revision that comes back two days later starts the whole thing over, and nobody compares it to the first.
How it works.
- 1
The manufacturer’s quote is read
The PDF from the window, door or millwork manufacturer, forwarded in or dropped on the desk. A model reads it twice: unit, size, options, unit price, extended price, lead time. Totals are checked against the document before the salesperson sees anything.
- 2
Cost becomes price under your rules
Each line is marked up under the dealer’s rules for that manufacturer, product line and customer: a margin, a floor, freight as its own line, whatever you wrote down. Options are carried over as options, not folded into a description.
- 3
The customer’s quote is drafted
A draft in NetSuite’s terms, lines in the manufacturer’s order, lead times and the manufacturer’s quote number on it, the job and the customer record matched. A revised PDF is compared to the first and the differences are listed for the salesperson.
- 4
The salesperson reviews and enters
Every line beside its source line. Adjust a markup, drop a line, confirm. Then the salesperson enters it as an estimate in NetSuite, and the customer gets it when the salesperson sends it.
How it connects to NetSuite.
Lunica reads the customer record, the item record and quote history through SuiteQL and the REST API, under a role that can only read: the markup rules and price level on the account, the special-order items you use for millwork, and the quotes already entered against the job. The manufacturer’s PDF is read from the mailbox or share where you keep it.
Nothing lands in NetSuite without a person and nothing is sent on its own. The customer’s quote goes back as a NetSuite API call or CSV import where one exists, or keyed by your team from what Lunica prepared, line by line, after the salesperson has reviewed it. The quote to the customer is a draft until the salesperson sends it.
What a week looks like.
- Every manufacturer quote read into cost the day it arrives.
- The markup applied the same way on every line, under rules you can read.
- Options and lead times on the customer’s quote, not lost between documents.
- A revision compared to the original, with the differences named.
Questions
Does it write to NetSuite?
No. It drafts the quote; the salesperson enters it as an estimate in NetSuite, or imports the file where NetSuite takes one.
Which manufacturers?
Any whose quote arrives as a PDF or a spreadsheet. A new layout is read the same way; the totals check catches what it misreads.
How are markups set?
In a spec your sales manager edits in plain English: by manufacturer, product line, customer or job, with a margin floor. History and revert.
What about options and accessories?
Carried over as separate lines or as options on the unit, whichever your quote format uses. Nothing is folded into a description where it can’t be checked.
What if the manufacturer revises the quote?
The new PDF is read and compared to the first. Added, dropped and repriced lines are listed before the customer’s quote is redrafted.
What does the model see?
The manufacturer’s quote being read, the markup rules that apply, and the customer and items it is matching. Not the whole quote file.
Does it need a server?
Lunica runs on one server inside your network that connects out to your NetSuite account, set up and maintained by Lunica. It reads NetSuite through SuiteQL and the REST API, under a role that can only read. There is no inbound connection from outside your network.
What does Lunica read in NetSuite?
The customer 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 NetSuite?
Nothing lands in NetSuite without a person. What belongs in NetSuite goes back as a NetSuite API call or CSV import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in the File Cabinet. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Window and Door Quotes is written for every system on the list. You’re reading the NetSuite version.
See it on your NetSuite data.
Thirty minutes. We walk the workflow on NetSuite data, then map it to yours.