Resolved against Epicor
The buyer and every line confirmed against live data, including parts the customer orders under their own numbering.
- Customers, by name and ID
- Parts, including the customer's own numbers
- Units and part revisions
Every request for quote drafted into Epicor Quote Entry
Requests for quote arrive as PDFs, scans, photographs, spreadsheets, Word files or plain email text, from a customer, a rep or your own inbox. Fluent reads them, resolves the customer, the parts, the units and the part revisions against live Epicor data, and drafts the quote in Kinetic for a person to review and process.
How it works
Build the quote from live Epicor data
The customer, the parts, the units and the revisions resolved against Epicor, and configurable parts priced by Epicor itself.
Priced by Epicor, not by us
Where a line carries a configuration, Fluent works the Epicor product configurator and reads the configured price back onto the line.
- Configurations answered from the request
- The configured price comes from Epicor
- Revisions resolved before configuring
Ready to review
A part or a unit that resolves to nothing is held on the draft with the reason, because no match beats a speculative match.
- Unresolved lines named with the reason
- Missing header values listed
- Nothing posts until a person processes it
The difference
No templates, no field mapping, no model training
Legacy document capture is configured per layout: a template for each vendor, a coordinate for each field, a model retrained when the paperwork changes. Fluent is configured in written instructions, and rewriting them changes what it does.
Legacy OCRAgentic automation
Templates
A template for every vendor, layout and document type
Reads each document the way a person does, whatever the layout
Field mapping
Fields found by position, so a moved column breaks extraction
No coordinates. It consults live Epicor data before it writes
Model training
Models retrained on samples whenever a design changes
Corrections become instructions, so it improves without retraining
Exceptions
Exceptions fall out to a queue for manual keying
Reasons through variations and exceptions instead of failing
Changing behavior
Behavior changes through a configuration project
Behavior is set in written instructions you control
Governance
Autonomy you can hand to an auditor
Every agent operates inside boundaries you define. Every action it takes is recorded, explainable, and reversible before it posts.
Approval thresholds
Low-risk orders post automatically; high-value or unusual ones wait for a person.
Audit logs
Every field the agent read, every decision it made, on the record.
Data retention
Your documents and data stay under retention policies you control.
Epicor validation
Transactions are validated by Epicor’s own business logic before they post.
Human review
Exceptions escalate to your team with the agent’s reasoning attached.
Permissions
Agents only touch the business objects and companies you allow.
Customers
What customers are saying
“My dreams have been answered. … Check out Fluent. 10/10 customer service & ease of use!”
Bonnie KlassenPresident, Klassen Custom Metal Fabrication5agents in production
64 secaverage review time
98.6%extraction accuracy
“We started our implementation call at 4:30 yesterday. First sales orders processing by 4:50. Minimal mistakes out the box.”
“The Fluent team got connected very quickly and orders are flowing well. Some mistakes, but easy to resolve with some agent tweaks. Really impressive platform.”
Workflows
Automate other workflows
Erp.UI.SalesOrderEntry
See all agentsOrder Entry
Customer purchase orders posted as sales orders, checked for duplicates before drafting.
Erp.UI.CustShipEntryCustomer Shipment
Shipping instructions become packs, every line resolved to its order release.
Erp.UI.ARInvoiceEntryAR Invoice Entry
Customer invoices and credit memos posted so billing stops waiting on a person.
Erp.UI.CashRecEntryCash Receipts Entry
Payments applied to the open invoices they settle.
Erp.UI.POEntryPO Entry
Vendor quotes and requisitions become purchase orders, priced in the vendor's own currency.
Erp.UI.ReceiptEntryReceipt Entry
Packing slips received against the purchase order line by line, in the unit the supplier shipped.
Erp.UI.APInvoiceEntryAP Invoice Entry
Supplier invoices matched two-way or three-way against the order and the receipt.
Erp.UI.TimeEntryTime Entry
Timesheets and shop paperwork posted against the right job and operation.
Erp.UI.IssueMaterialEntryIssue Material
Material issued to the job without looking up the sequence by hand.
Frequently Asked Questions
See it draft a quote from one of your own RFQs
Send a real request for quote and read the Quote Entry draft it produces, with every unresolved field named.
