How to Test AI Order Entry on Your Own Epicor Kinetic System: A Pilot Checklist
Which purchase orders to send, what to compare against your own keying, the pass and fail checks, and who signs off at the end of a 30-day trial.
Gonzalo Nuñez
Chief Technology Officer

Test AI order entry on your own Epicor Kinetic data, with your hardest purchase orders, while your team keeps keying as usual, and judge it on what reaches Order Entry. Fluent's 30-day trial is built for that: one 30-minute call connects it to Kinetic, nothing is installed inside Epicor, and every order stays a draft until a person approves it, so a pilot never touches your live orders until you decide it should.
This checklist covers which orders to send, what to compare, the pass and fail checks, a four-week plan and who signs off.
Before you start
- Name an owner. One person on the order desk runs the pilot day to day, and one manager makes the call at the end.
- Agree what "good" means first. Write down the review time and the error rate you would accept, before anyone sees a result.
- Ask your Epicor administrator to review the access scope. Fluent generates a list of exactly the Epicor services the agent calls. Your administrator imports it, and Epicor enforces it.
- Decide where the drafts go. During a pilot, drafts can be approved into Kinetic or rejected after comparison. Pick one, and write it down.
Which purchase orders to send
Send a batch that looks like your worst week. Include at least one of each:
- The hardest formats: a scanned PO, a photo, a spreadsheet, an order typed into the email body, and a long multi-page PDF.
- Customer part numbers: a customer who never uses your part numbers, and one who uses a number you have not seen before.
- Units: a customer who orders in cases while you sell in each.
- Prices: a customer whose PO prices rarely match your price list.
- Long orders: a multi-line order with 30 or more lines.
- Ship-tos: an order shipping to an address that is not on file.
- Duplicates and revisions: a PO sent twice, and a revised PO for an order you already entered.
- Things that are not orders: a quote request or a status question, to see how the agent treats them.
What to compare
For every order in the batch, compare the draft with what your team keyed:
- Customer and ship-to.
- Each line's part, quantity and unit.
- Each line's price, and whether a difference from Epicor's price was flagged.
- Header values: customer PO number, need-by date, terms and currency.
- What the draft flagged, and whether each flag was right.
- How long the review took, from the time on the in-app analytics.
Pass and fail checks
| Check | Pass | Fail |
|---|---|---|
| Customer part numbers | Resolved to your part, or flagged on the line when unknown | A wrong part entered without a flag |
| Units | Taken from the PO, converted where the part carries the unit, flagged where it does not | A unit assumed or silently changed |
| Prices | Any difference from Epicor's price shown on the line | A price difference that reaches an approver unmarked |
| Duplicate PO | The resent PO named as a possible duplicate of the first order | A second order created |
| New ship-to | The address used is stated, with a warning | An order shipped to the default without anyone told |
| Not an order | The quote request or status email is not drafted as an order | A sales order drafted from it |
| Nothing written early | No order exists in Kinetic until the draft is approved | An order appears before anyone approved it |
| Approvals | The order reaches the right approvers by your written rule | Everyone gets everything, or nobody does |
| Review time | Within the figure you agreed before the pilot | Slower than keying by hand |
A four-week plan
- Week 1: connect and configure. The 30-minute technical setup call connects Kinetic, and a functional session trains the people who will review. Write the instructions your order desk already follows, such as how a customer's cases convert.
- Week 2: run the hard batch. Send the orders above, keep keying them as usual, and compare each draft with what your team entered.
- Week 3: test the approval workflow. Add a pricing stage with a condition written in plain language, mark an approver as away to see the delegate take over, and approve one order by replying to the email.
- Week 4: decide. Read the review time and the corrections from the pilot, set them against what you agreed in advance, and price your volume on the pricing page.
Who signs off
- The order desk lead, on accuracy and on whether reviewing a draft is faster than keying.
- Pricing or sales, on how price differences are surfaced and routed.
- Your Epicor administrator, on the access scope and on what, if anything, they maintain.
- The controller or operations manager, on cost against the labour saved. The cost guide works an example.
Customer results
StoneAge runs supplier pack slips and sales orders through Fluent on Epicor Kinetic. Its team checks each document instead of typing it, and its median review time on Receipt Entry is 9 seconds, measured over 30 days. Read the StoneAge customer story.
We started our implementation call at 4:30 yesterday. First sales orders processing by 4:50. Minimal mistakes out the box.
Richard Gardner · Group IT Director, Luceco
Luceco posted about its first day on EpiUsers.help.
Related guides
- Sales order exceptions in Epicor Kinetic: what each flag in this checklist means, with examples.
- Best AI order entry software for Epicor Kinetic: the shortlist to run this checklist on.
- How to automate Epicor sales order entry: every route into Order Entry, compared.
Start your pilot
The order entry automation page covers how Fluent drafts sales orders, and the Epicor integration page explains the connection and access scope. To start a 30-day trial on your own purchase orders, book a demo.


