Fluent by Technology Coast Partners

Automated Quotes for Manufacturers: How to Automate Quoting in Your ERP

Automated quotes explained: CPQ, job-shop quoting and RFQ-to-quote entry, the quoting steps, and how Fluent drafts quotes for Epicor and routes them for approval.

Gonzalo Nuñez

Gonzalo Nuñez

Chief Technology Officer


Automated Quotes for Manufacturers: How to Automate Quoting in Your ERP

Automated quotes are quotes drafted in your ERP from a customer's request for quote (RFQ) without anyone retyping it. The software reads the RFQ, finds the customer, the parts, the quantities and the units, prices each line from your price lists or pricing rules, and leaves a quote for a person to check and send. For manufacturers the phrase covers three different kinds of software. Where the time goes into reading RFQs and typing them into Epicor Kinetic, Fluent is the one to use: it drafts the quote in Quote Entry, priced by Epicor, and routes it through approval workflows in which an AI tells each approver what to check before they open it.

This guide explains the three, walks through the quoting process step by step, shows where automation applies at each step, lists the common failure points and says what to measure. Fluent is quote entry automation, and the guide says where it is the right choice and where a CPQ or an estimating tool is.

What people mean by automated quotes

  • CPQ and product configurators. Configure, price, quote (CPQ) software holds the rules for a configurable product: which options go together, what each one costs, and what the bill of materials looks like. A salesperson, dealer or customer answers questions, and the rules produce a buildable configuration and a price. Examples are Epicor CPQ (formerly KBMax), Tacton CPQ, Salesforce Revenue Cloud, DriveWorks (for SOLIDWORKS) and Configure One. Epicor Kinetic also has its own product configurator, used from Quote Entry and Order Entry.
  • Estimating and quoting tools for job shops. Built for shops that make parts to the customer's drawing. They read the 3D model or the drawing, estimate material, machine time and outside processing, and apply your pricing rules. Examples are Paperless Parts and the estimating and quoting module of job-shop ERPs such as ProShop.
  • Quote entry automation. Software that reads RFQs as they arrive (email bodies, PDFs, spreadsheets, Word files, scans) and drafts the quote in the ERP's own quote screen: the customer, the parts including the customer's own part numbers, the quantities, the units of measure and the prices from your price lists. It holds no product rules of its own: where a part is configurable, the ERP's own configurator still decides. It removes the reading and typing between the RFQ and the quote. Fluent works here, and on Epicor Kinetic it also answers the product configurator from the request and routes each draft quote through approvals before anything is created in Epicor.

Most manufacturers need one or two of these, rarely all three. A company that sells catalogue and repeat parts in volume gets little from a configurator, because there is nothing to configure. A company that sells engineered-to-order machines gets little from faster data entry until its configuration rules live somewhere other than an engineer's head. Sort a month of your own RFQs before choosing.

Comparison table

Quote entry automationFluentReading RFQs and drafting the quote in the ERP with customer, parts, units, quantities and prices; on Epicor Kinetic, answering the product configurator and reading back the configured priceIn a draft of the ERP quote, reviewed before it is createdApproval stages with conditions in plain language; an approval agent tells each approver what to check; approve in the app or by replying to the email; nothing written to Epicor while pendingHigh volumes of RFQs for standard, repeat and configurable parts already set up in the ERP
CPQ and configuratorsEpicor CPQ, Tacton CPQ, Salesforce Revenue Cloud, DriveWorks, Configure OneOption rules, pricing logic, bills of materials and drawings for configurable productsIn the CPQ or an online configurator, then the quote or order passes to the ERPNot described in this guide; confirm with each vendorConfigure-to-order and engineer-to-order products with many interdependent options
Job-shop estimatingPaperless Parts, ProShop estimating and quotingCost estimates from 3D models and drawings, routings, pricing rulesIn the quoting tool, then the quote passes to the ERPNot described in this guide; confirm with each vendorBuild-to-print machining, sheet metal, fabrication and additive work

The quoting process, step by step

Whatever the product, a quote moves through the same six steps. The time is rarely in the pricing decision itself. It goes into finding things, matching them and typing them.

1. Receive the RFQ

RFQs arrive as emails, PDF forms, spreadsheets of line items, drawings, scans and photos, or as a call a rep writes up. They land in shared inboxes and personal ones. The first delay is often just noticing that one arrived and deciding who owns it. A shared address that is watched, with every RFQ logged at the time it was received, fixes most of this, and that timestamp is where turnaround time starts.

2. Identify the customer

The requester has to be matched to a customer record in the ERP, with the right ship-to and contact. A new prospect needs a record before a quote can exist. Mistakes here, such as two records for one company or a parent picked instead of a subsidiary, carry through to pricing and terms.

3. Resolve the parts

This is usually the largest share of the work. Customers ask for parts by their own part numbers, by description, or by drawing number. Someone has to translate each line to your part number and revision, often by searching the customer part cross-reference, past orders and past quotes. Lines that are not standard parts go to engineering or estimating, which is where configurators and job-shop estimating tools earn their keep.

4. Enter quantities and units of measure

An RFQ may ask for 500 feet, 3 rolls or 12 boxes of 100. Each quantity has to be entered in the unit the customer asked for, or the quote prices the wrong amount. Many RFQs ask for several quantities per line so the customer can see the price breaks.

5. Price each line

Prices come from price lists, customer-specific prices, quantity breaks, cost-plus rules or an estimate. For standard parts this should be a lookup the ERP already does. For configured or build-to-print parts it is the work of a configurator or an estimator.

6. Review, send and follow up

Someone checks the quote, sends it and records the outcome. Quotes for a new customer, a configured product or an unusual price often need a second signature, and that sign-off tends to happen by email, outside the record. Fluent puts it on the quote: conditions written in plain language decide which approvers a draft quote needs, the approval agent notes what each one should check, and they can approve by replying to the email. When the customer accepts, the quote becomes a sales order, and the customer's purchase order should be checked against what was quoted.

Where automation applies at each step

Receive the RFQWatching inboxes, deciding who owns itPicks up every RFQ from a shared address and logs itQuote entry automation
Identify the customerSearching customer records, choosing between near duplicatesMatches the requester to an ERP customer and says which record and whyQuote entry automation
Resolve the partsTranslating customer part numbers and descriptionsSearches the cross-reference and history; holds lines it cannot matchQuote entry automation for standard parts; configurators and estimating tools for the rest
Quantities and unitsRe-keying quantities, converting units by handLoads quantities in the unit the RFQ states and lets the ERP convertQuote entry automation
Price each lineLooking up prices, building estimatesApplies price lists, configuration rules or cost modelsERP price lists, CPQ, estimating tools
Review and sendChecking every line by eye; chasing sign-off by emailShows only what differs or could not be resolved, and routes the quote to the approvers it needs with what each should checkAll three for the differences; quote entry automation with approval workflows (Fluent) for the sign-off

Common failure points

  • The wrong customer record. Duplicate and parent or subsidiary accounts give a quote the wrong prices and terms. Automation should say which record it matched and stop when it is unsure.
  • Customer part numbers that do not resolve. A missing cross-reference entry is often why a line gets the wrong part. A wrong match is worse than no match: the line should come back unresolved, with what was searched.
  • Unit of measure mix-ups. Feet against inches, each against box. Quantities have to be loaded in the unit the RFQ states and converted by the ERP, never assumed.
  • Prices typed over the price list. Hand-typed prices drift away from the price list. Let the ERP price the line and flag every difference from what the customer expects.
  • RFQs that sit in an inbox. No owner, no timestamp and no follow-up means lost business nobody sees.
  • Quotes that are retyped into orders. When the order is keyed again from the purchase order instead of coming from the quote, the agreed prices and parts get lost.
  • Sign-off by email thread. A quote that needs a manager's approval waits in an inbox. Nobody can see who has it, an approver who is away stalls it, and the decision is not on the quote.

What to measure

  • Quote turnaround time. Time from the RFQ arriving to the quote being sent. Track the median and the slowest 10%, by customer and by type of quote, since one average hides the backlog.
  • Win rate. Quotes that become orders, by count and by value. Segment it by customer and product family so that a change in mix does not hide the effect of faster quotes.
  • Quote accuracy. The share of quotes sent without a correction, and the share of orders whose part, unit or price differs from the quote they came from.
  • Touch time per quote. Minutes of staff time per quote, measured apart from waiting time. This is what automation reduces most directly.
  • Open RFQs. RFQs received but not yet quoted at the end of each day.

Measure these for a few weeks before changing anything, so you have a baseline to compare against.

Where Fluent fits

Fluent's Quote Entry agent is quote entry automation for Epicor Kinetic. It reads RFQs as they arrive (PDFs, scans, photos, spreadsheets, Word files and email bodies) and drafts the quote for Quote Entry. It resolves the customer, the parts (including the customer's own part numbers, through the customer part cross-reference and that customer's past orders and quotes), the units as the RFQ states them, and the part revisions against live Epicor data. Each line is priced by Epicor itself, from your price lists, so the quote carries the prices the ERP would give.

Nothing is written to Epicor while an approval is pending, and nothing reaches Epicor until a person processes the draft. Each draft quote goes through the agent's approval stages: conditions written in plain language, such as "quotes for a new customer", decide which approvers it needs, and an approval agent reviews it against each approver's written responsibility, using read-only lookups in Epicor, marking it "nothing flagged" or "needs review" with a note saying what to look at. Approvers decide in the app, in a private chat with the agent, or by replying to the email, and can return the quote to its owner with a reason. A customer or a part that cannot be matched is left on the draft with the reason and what was searched, and every field read and every decision is recorded on the document. Fluent connects to Kinetic's REST API from outside, so nothing is installed inside Epicor: no customization, no BPM and no import file. There are no templates per customer and no field mapping; behaviour is set with written instructions, and corrections become instructions.

Where a line is a configurable part, Fluent works the Epicor product configurator: it answers the configurator's questions from the request and reads the configured price back onto the line, so the price comes from Epicor's own rules. Fluent is not a CPQ and does not estimate cost from a 3D model. If your configuration rules are not in Epicor yet, or dealers and customers need a visual configurator, Epicor CPQ adds visual configuration for complex products and Fluent sits alongside it; Tacton CPQ is another option. For costing build-to-print parts from drawings, look at Paperless Parts or your job-shop ERP's estimating module.

When the customer accepts, the quote becomes a sales order in Epicor. Fluent's Order Entry agent reads the customer's purchase order in whatever format it arrives, resolves the customer, ship-to, customer part numbers, units and prices, and flags duplicate POs. The guide on how to automate Epicor sales order entry covers that step.

55 sec
median review time per document
Thousands
of documents reviewed by customers in the 90 days to 1 September 2026

On Epicor Prophet 21, Fluent drafts supplier vouchers and customer orders, and converts the customer's open quote into the order when the purchase order answers one. The same agents are offered for other ERPs, including SAP Business One, Oracle NetSuite, Acumatica and Microsoft Dynamics 365 Business Central. Epicor Kinetic is where Fluent is deepest.

How to start

  • Sort a month of RFQs. Split them into standard and repeat parts, configured products and build-to-print work. The split tells you which kind of automation pays.
  • Take a baseline. Measure turnaround time, touch time and win rate before changing anything.
  • Clean the customer part cross-reference for your largest customers. Every approach depends on it.
  • Check the price lists. Confirm the prices in the ERP match what sales actually quotes.
  • Trial on real RFQs. Include the messy ones, and count corrections per quote.
  • Trial the approvals too. Route a quote to two approvers by a written rule, mark one of them out of office, approve one by replying to the email, and read what the AI flagged for each approver before they opened it.

Customer results

Metalworks, a family-owned manufacturer in Michigan on Epicor since 2010, runs its AP invoices through Fluent. Fluent connected to Epicor in a day, and reviewers rarely change a field it read. Keying an invoice took seven to eight minutes; reviewing the draft now takes under a minute, and an approval that took five minutes now takes seconds, from an email. “It’s like a breath of fresh air,” says Jill Schoedel, IT Manager.

StoneAge, an employee-owned maker of waterblast tools in Durango, Colorado, runs supplier pack slips into Receipt Entry and customer purchase orders into Order Entry through Fluent. Fluent connected to its Epicor in one 40-minute call. A receiver reviews a pack slip in a median of about ten seconds and customer service reviews a sales order in about a minute, where both used to key them by hand. A person approves every document before it posts.

See it on your own RFQs

Send a real request for quote and read the Quote Entry draft Fluent produces, with every unresolved field named. See the Quote Entry agent, all agents and pricing, or book a demo.

Frequently Asked Questions

Automated quotes are quotes drafted in the ERP from a customer's request for quote without anyone retyping it. Software reads the RFQ, matches the customer and parts, enters quantities and units, and prices the lines from price lists or pricing rules. A person then reviews and sends the quote; with Fluent, the draft first goes to the approvers it needs, with a note from an approval agent saying what each one should check.

CPQ software holds the rules for configurable products and works out a buildable configuration and its price. Quote entry automation reads incoming RFQs for parts you already sell and drafts the quote in the ERP. A manufacturer of engineered products needs CPQ; one that quotes many standard and repeat parts gets more from quote entry automation, and the two run side by side.

Route RFQs to a shared address that software watches, have it read each RFQ and draft the quote in the ERP with the customer, parts, quantities, units and prices, and route the draft to the people who approve it before it is sent. Lines the software cannot resolve should come back marked with the reason. In Fluent, conditions written in plain language decide which approvers a quote needs, and approvers can decide by replying to the email. Configured and build-to-print lines still need a configurator or an estimator.

Epicor Kinetic has Quote Entry and its own product configurator, and Epicor CPQ adds visual configuration for complex configurable products. Reading incoming RFQs from email, PDFs and spreadsheets and drafting them into Quote Entry is the job of a document-reading tool such as Fluent's Quote Entry agent, which works through Kinetic's REST API and alongside both. For configurable parts, it answers Epicor's product configurator from the request and reads the configured price back onto the line. Every draft goes through Fluent's approval stages, where an approval agent tells each approver what to check, and nothing is written to Epicor while an approval is pending.

Quote turnaround time (from RFQ received to quote sent), win rate by count and value, and quote accuracy (quotes sent without correction, and orders that differ from their quote). Touch time per quote and the number of open RFQs at the end of each day show where staff time goes. Take a baseline before changing anything.

No. Quote entry automation removes the reading and typing for parts you already sell, so estimators and engineers spend their time on configured, custom and build-to-print work. With Fluent, every quote is a draft that the approvers it needs review before it reaches the ERP, and an approval agent tells each of them what to check.

Read more

Ready to Save Hours Every Week?

Send us a batch of sample documents. Our Epicor specialists will show you what an agent can automate, and what still needs your judgment.