Fluent reads the shipping instruction your customer sent and creates the shipment in Epicor Kinetic, with every line matched back to the order release it ships against. Epicor validates the lines before anything is written, and whatever does not pass goes to a person with Epicor's own message on the line.
How it works
Every line resolved to the order release it ships against, and validated by Epicor before anything is written.
A shipping instruction names a delivery order, a carriage number and the customer's part reference, none of which are Epicor keys.
Fluent sends the lines for validation before it writes, and fails closed: a check it cannot confirm blocks the shipment.
A line Epicor cannot confirm is marked failed rather than passed through, and a rolled-back shipment is reported as one.
The difference
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 Epicor 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.
An order 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 Epicor’s own business logic before they post.
Exceptions escalate to your team with the agent’s reasoning attached.
Agents only touch the business objects and companies you allow.
Customers
“People should not feel like it’s too good to be true, because it works.”
“My dreams have been answered. … Check out Fluent. 10/10 customer service & ease of use!”
“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
Requests for quote drafted as Kinetic quotes, with customer part numbers resolved three ways.
Customer purchase orders posted as sales orders, checked for duplicates before drafting.
Customer invoices and credit memos posted so billing stops waiting on a person.
Vendor quotes and requisitions become purchase orders, priced in the vendor's own currency.
Packing slips received against the purchase order line by line, in the unit the supplier shipped.
Supplier invoices matched two-way or three-way against the order and the receipt.
Material issued to the job without looking up the sequence by hand.
Shipping instructions arrive, every line resolves to its order release, and the shipment is created in Epicor Kinetic. Your team reviews the exceptions.
