AI Sales Order Entry in Epicor Kinetic: Create on Arrival, or Approve First
Two ways an AI order-entry tool keeps a person in charge in Epicor Kinetic: create the order on arrival and use Kinetic's order hold, or keep a draft until approval workflows clear it. Why approving first gives reviewers more.
Gonzalo Nuñez
Chief Technology Officer

An AI order-entry tool can keep a person in charge of Epicor Kinetic sales orders in one of two ways. It can create the order in Kinetic as soon as the email is read and use Kinetic's order hold until a person releases it, or it can keep a draft outside Epicor and create the order only when it is approved. For a tool reading customer purchase orders, approving first is the stronger choice: Kinetic receives only approved orders, discrepancies are triaged on the draft, and Fluent adds approval workflows before the order reaches Epicor, sending each draft to the right approvers by rules written in plain language, with an approval agent telling each one what to check before they open it.
Create on arrival: review on a held order in Kinetic
The tool reads the purchase order, creates the sales order in Kinetic through the REST API and puts it on hold. Fields it is unsure of are flagged, usually in a comment or a user field, and a person opens the order in Order Entry, fixes what is wrong and takes it off hold. Lowki's Lexi works this way.
Where it is enough:
- Early visibility. The order exists as soon as the email is read, so customer service can find it straight away.
- A simple handover. Releasing the hold is the approval, and it is a step every Epicor user already knows.
What creating the order early means:
- Unreviewed orders are real orders. They carry order numbers and appear in Order Entry, trackers, BAQs and dashboards that do not filter on the hold.
- Corrections are edits to a live order. Fixing a part or a unit means changing order lines in Kinetic, after the fact.
- Rejected work has to be cleaned up. A resent purchase order or a quote request read as an order becomes an order to delete or void.
- One handover. The tool's review ends when a person releases the hold. A pricing or credit sign-off is arranged outside the tool.
- Finding what needs attention. Reviewers need a way to list the held orders that came from the tool and see what was flagged on each, usually a BAQ.
Staged review: approve before Epicor
The tool reads the purchase order, resolves it against live Epicor data and keeps the result as a draft in its own review queue. Each difference sits on the line it belongs to as a warning: a part number it could not match, a price that differs from Epicor, a unit that is not valid for the part, a PO number that already exists on another order. A person approves, corrects or rejects the draft, and only then is the order created in Kinetic, through Epicor's own business logic. Fluent works this way.
What it does well:
- Kinetic receives only approved orders. Planners, buyers and reports never see an unreviewed one.
- Discrepancies are triaged in one place. The reviewer works through warnings line by line and leaves the rest of the order alone.
- Approval runs in stages, to the right people. A draft can go to the order desk, then to pricing or credit. Each stage picks its approver by name, by whoever is least busy, or by letting the AI choose the right person from a pool, and a condition written in plain language, such as "orders from a new customer", decides whether the stage is needed. Out-of-office approvers are routed to a delegate, who signs on their behalf.
- Each approver is told what to check. An approval agent reviews the draft against that approver's responsibility before they open it and leaves a note on what to look at, and an approval summary sits with the document.
- Rejected drafts disappear. Nothing is left to delete in Kinetic.
- Epicor still validates. The order is created through Kinetic's business logic, so it meets the same rules as one keyed by hand.
What to watch:
- A second screen. The order desk reviews in the queue, then works the order in Kinetic as usual. Approvers who are away from the queue can decide by replying to the approval email.
- The queue has to move. An order is not in Kinetic until it is approved, so review time matters. On Fluent, the median review across 25,359 documents in the 90 days to 1 September 2026 was 55 seconds.
Comparison
| Staged review before Kinetic | Order created on arrival, held in Kinetic | |
|---|---|---|
| Where unreviewed orders live | In the tool's review queue | In Kinetic, on hold |
| Order number assigned | When the draft is approved | When the email is read |
| How discrepancies are shown | Warnings on each line of the draft | Flags on the order, found by the reviewer |
| What each approver is told to check | On Fluent, an approval agent's note per approver: "nothing flagged" or "needs review", and what to look at | The flags on the order |
| Corrections | Edits to the draft before it is written | Edits to the live order |
| Rejected or duplicate orders | Rejected or returned to the owner in the queue; nothing reaches Kinetic | Deleted or voided in Kinetic |
| Approval workflows | On Fluent: stages, plain-language conditions, approvers picked by name, workload or the AI, out-of-office delegates, approve by replying to the email | The tool's review ends at a person's release of the hold |
| Epicor validation | When the approved order is created | When the order is created |
| Example | Fluent | Lowki (Lexi) |
Questions to ask any vendor
- Where does an order wait before a person approves it?
- How does a reviewer see what the tool was unsure of, line by line?
- What happens to a duplicate PO or a document that was not an order?
- Can more than one person sign off, chosen by a rule written in plain language, and what happens when one of them is out of office?
- Does the order go through Epicor's own business logic when it is created?
- Is every field the tool read, and every decision it made, recorded?
- Can an approver decide by replying to the approval email?
- Does each approver see what the AI flagged for them before they open the order?
Customer results
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.
How Fluent does it
Fluent's agents stage every document. For Order Entry, the draft shows the customer, ship-to, parts, prices and units resolved against live Epicor data, with every difference as a warning on its line and any existing order with the same customer PO number flagged. Approval workflows route drafts through the stages you define. Before each approver opens a draft, an approval agent reviews it through the lens of that approver's written responsibility, using read-only lookups in Epicor, and marks it "nothing flagged" or "needs review" with a note saying what to look at. Approvers can chat with the agent about the draft, approve by replying to the email, or return the draft to its owner with a reason. Nothing is written to Epicor while an approval is pending. When a draft is approved, the order is created in Kinetic, and the audit log records what was read and decided, including who signed on whose behalf.
The same model runs on every screen Fluent covers, so AP invoices, receipts and cash receipts are reviewed in the same queue before they reach Epicor. See order entry automation, compare Fluent and Lowki, or book a demo to see a draft built from your own purchase orders.
Frequently Asked Questions
It can, as long as a person approves each order, and Kinetic's order hold keeps an unreleased order from moving on. For a tool reading customer purchase orders, approving first is the stronger choice: when the tool creates the order on arrival, unreviewed orders exist in Kinetic and rejected ones have to be removed. Staging a draft outside Epicor sends Kinetic approved orders only and lets approval workflows run first: stages, the right approver for each order, and an approval agent's note on what each approver should check.
An order hold flags a sales order so it does not move on to fulfilment until someone releases it. The order still exists, with its number and lines, and appears in Order Entry and in reports that do not filter on the hold.
Staged review keeps each order the AI reads as a draft outside the ERP, with every difference shown as a warning on its line. On Fluent, an approval agent reviews the draft for each approver first and notes what to look at; the approver then approves, corrects, rejects or returns it to its owner. Nothing is written to Epicor while an approval is pending, and the order is created only after approval.
Yes, with a staged tool. Fluent's approval workflows route a draft through the stages you define, for example the order desk and then pricing. Each stage picks its approver by name, by workload or by letting the AI choose, conditions are written in plain language, out-of-office approvers are routed to a delegate, and approvers can decide by replying to the email. The order is created in Kinetic only after the last stage clears.
Only if the queue sits unattended. Because every difference is already listed on its line, review is quick: on Fluent, the median review across 25,359 documents in the 90 days to 1 September 2026 was 55 seconds. Approvers can also decide by replying to the email, and approvers who are out of office are routed to a delegate, so a draft does not wait on someone who is away.
Yes, unless the report or BAQ filters on the hold. A held order is a sales order like any other, so trackers, dashboards and exports include it by default, and a tool that creates orders on arrival puts its unreviewed orders there too. With staged review, only approved orders reach Kinetic, so no filter is needed.


