When customers request prices by email, the first challenge is finding the complete request. A buyer sends a spreadsheet to inside sales, a drawing to the account manager and a quantity change in a reply. Unless someone brings those together, two reps may quote different versions of the same job.
RFQ intake is the step where your team turns that correspondence into one request they can price. For a NetSuite sales team, the aim is to know who is buying, what they need and what is still missing before anyone starts entering an estimate.
What belongs in the intake record
The intake record is your team’s shared view of the request. It can live in a connected workspace before the NetSuite estimate exists. Keep the original messages attached so a rep can check whether a summary omitted a requirement.
Oracle’s Estimate transaction records the customer quotation. Its purchasing RFQ serves a different purpose: requesting supplier bids. Keep the two connected when purchasing must source a cost, but do not put incoming customer requests into the supplier RFQ process.
For sales quoting, collect the buying entity, customer reference, receipt time, requested response date, owner and source messages. At line level, keep the customer description alongside the proposed NetSuite item. Do not replace the original wording with your interpretation.
Group forwards and revisions under the same request
Use customer account plus customer RFQ reference as a starting point for duplicate detection. Treat it as a candidate match, not a universal unique key: some buyers reuse project references across releases.
For example, these four messages should not create four independent quotations:
| Incoming message | Decision | What the team retains |
|---|---|---|
| New RFQ R-217 with six lines | Open a request | Original workbook and requested due date |
| Forward of R-217 from another colleague | Attach to existing request | Sender and receipt time |
| R-217 with quantity changed on line 4 | Open a revision | Previous quantity and changed workbook |
| R-217 for another delivery site | Ask whether it replaces or supplements the request | Both addresses and the buyer’s answer |
Quote revision control begins here. Waiting until someone sends a PDF makes it harder to explain which source produced each version.
Decide what must be answered before you can quote
Mark a request ready for estimating only when someone can price the intended scope. A missing phone number need not block a catalog quote. A missing material grade often should.
Send unresolved specifications to engineering through a technical clarification. Send an unknown supplier cost to purchasing. Keep the commercial owner responsible for the customer response so the buyer receives one coordinated answer.
Measure acknowledgement time separately from time to a complete quote. An immediate acknowledgement does not mean the estimating team has enough information. Record when you asked for a missing drawing and when the buyer supplied it; otherwise the team appears slow for time outside its control.
For work made from customer drawings, identify the supplied file types before assigning the RFQ. A STEP model and a PDF drawing may carry different portions of the requirement. NIST’s STEP File Analyzer and Viewer can inspect product and manufacturing information (PMI) in supported STEP data; the existence of a 3D model does not establish that it contains every requirement needed for a quote.
Have intake record the drawing number and revision, the model revision, and the customer’s instruction about which governs. Ask specifically for missing finish, tolerance or inspection requirements. The estimator can then price the required operations rather than discover a special inspection obligation after the customer accepts.
Have Bourne prepare the request for the estimating team
With Bourne, we can build an intake workspace that reads the email and attachments, groups related messages and proposes line items. The rep reviews unresolved matches in context instead of copying each cell into a new screen. Item matching should show the evidence for a selection, especially when a customer uses its own part numbers.
Start with one shared mailbox and one product family. Check forwarded messages, password-protected files, duplicate attachments and conflicting revisions before expanding. The output of intake should be a reviewed request that the next person can quote without reopening five conversations.
Frequently asked questions
Should every customer RFQ immediately create a NetSuite estimate?
No. First establish the customer and whether the request duplicates existing work. You can keep incomplete requests in an intake queue and create an estimate when the scope is clear enough to price.
What should happen when the buyer sends a revised spreadsheet?
Retain the original and compare the changed lines. Ask whether the new file replaces the earlier scope. Reopen pricing or engineering review only where the change requires it.
Can Bourne read both email text and attachments?
We can configure a workflow to read the connected mailbox and supported documents together. The implementation needs explicit handling for unreadable files and conflicts between the message and its attachments.
Further reading
NIST: STEP File Analyzer and Viewer
A free tool for inspecting STEP data, PMI and validation properties.
Arda Bulut
Arda Bulut is the co-founder and CTO of Bourne and HockeyStack. He leads engineering at Bourne, building the platform people use to create AI products, agents and automations.