Customer purchase orders arrive as PDFs, spreadsheets and plain email. Fluent reads each one, resolves the ship-to, the contact and every item against your live P21 data, checks for an order already on that PO, and drafts the order your inside sales team would key.
How it works
The ship-to, the items and the units resolved against live P21 data, and the order priced and checked before it is drafted.
The ship-to settles the customer, the way your order takers work, and every item is matched, including the customer's own part numbers.
The order starts from what your team already agreed with the customer, so a price that disagrees with the PO is visible before the order exists.
Whatever could not be settled is named on the draft, so a reviewer sees the open questions and nothing else.
Comparison
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.
A template for every vendor, layout and document type
Reads each document the way a person does, whatever the layout
Fields found by position, so a moved column breaks extraction
No coordinates. It consults live Prophet 21 data before it writes
Models retrained on samples whenever a design changes
Corrections become instructions, so it improves without retraining
Exceptions fall out to a queue for manual keying
Reasons through variations and exceptions instead of failing
Behavior changes through a configuration project
Behavior is set in written instructions you control
Governance
Every agent operates inside boundaries you define. Every action it takes is recorded, explainable, and reversible before it posts.
A document over an amount or outside a price tolerance goes to the approvers who own it.
Every field the agent read, every decision it made, on the record.
Your documents and data stay under retention policies you control.
Transactions are validated by Prophet 21 before they post.
Exceptions escalate to your team with the agent's reasoning attached.
Agents only touch the documents and companies you allow.
Guides
How distributors turn emailed customer purchase orders into Prophet 21 orders: the ship-to, customer part numbers, quotes and contract prices, checked before an order exists.
Which customer orders belong on EDI and which on AI order entry in Prophet 21, how each reaches Order Entry, and how distributors run the two side by side.
OCR reads characters and templates say where to find them. AI reads the document like a person does. Why that changes order entry, why reading is only half the job in Epicor Kinetic, and how Fluent finishes it with approval workflows.
The order to cash process for manufacturers and distributors: each step, the document that arrives, where it lands in Epicor Kinetic, and how Fluent drafts it and routes it for approval.
Prophet 21
Supplier invoices vouched against PO receipts, plus expense invoices and vendor credits, for AP to release.
Send us a batch of customer purchase orders, however they arrive. We will show you what an agent can draft in Prophet 21 Order Entry, and what still needs your judgment.
