Fluent by Technology Coast Partners

Fluent vs Lowki for Epicor Kinetic: Approval Before the Order Is Created

Fluent vs Lowki (Lexi) for Epicor Kinetic sales orders and AP: Lowki creates the order in Kinetic as soon as the email is read and holds it there, while Fluent adds approval workflows before the order reaches Epicor.

Gonzalo Nuñez

Gonzalo Nuñez

Chief Technology Officer


Fluent vs Lowki for Epicor Kinetic Order Entry and AP

For AI order entry on Epicor Kinetic, use Fluent. Lowki fits a narrower case: one person who reviews every order on hold inside Kinetic, typically at a UK manufacturer that wants a UK vendor billed per order line. Both read the purchase orders customers email in and turn them into sales orders in Epicor Kinetic, with a person deciding what goes ahead. Lowki creates the sales order in Kinetic straight away, on hold, and someone reviews and releases it in Order Entry. Fluent runs agents in production for ten Kinetic screens across order to cash and procure to pay, where Lowki's AP invoice automation is in early access, and it puts every draft through an approval workflow before Epicor sees it: an approval agent reviews the draft for each approver before they open it, rules written in plain language decide who signs, approvers who are out of office are routed around, and an approver can decide by replying to the email. Nothing is written to Kinetic until the draft is approved.

How each approaches sales order entry

Lowki

Lowki.ai is a UK company based in Dudley, in the West Midlands. Its product, Lexi, was built inside Thomas Dudley Ltd, a manufacturer that has run it on its own order desk since 2024, and was opened to other Epicor Kinetic manufacturers in 2026. Lowki reports more than 40,000 orders and 171,000 order lines processed there, with 98% customer, 97% ship-to and 95% PO number accuracy.

According to Lowki's website, Lexi watches a Microsoft Exchange Online mailbox, reads the order attachment, and creates the sales order in Kinetic through the REST API, with the order on hold. Unknown part numbers and price differences are flagged rather than guessed, the order links back to the original email, and a person reviews it in Order Entry and takes it off hold. Lexi never releases an order itself. Your team can also drag a document onto an order in Kinetic and mark it for processing, and a deployment can be set to create quotes instead of orders.

Lowki runs Lexi on its own infrastructure. Reporting today is done with BAQs filtered to Lexi's integration user, with dashboards under consideration.

Fluent

Fluent is built by Technology Coast Partners (TCP), an Epicor Platinum Partner with more than 20 years implementing Epicor and more than 600 implementations, all in manufacturing and distribution. It runs agents for ten Epicor Kinetic screens, from Quote Entry and Order Entry through Customer Shipment, AR Invoice Entry and Cash Receipts Entry to PO Entry, Receipt Entry and AP Invoice Entry.

For a sales order, the agent reads what was forwarded or emailed to it (PDF, scan, photo, spreadsheet, email body, XML or EDI) and resolves it against live Epicor data:

  • Customer and ship-to, with the customer's own currency and terms.
  • Parts, including the customer's own part numbers.
  • Prices on the purchase order, compared with the price in Epicor.
  • Units of measure, taken from the purchase order and checked against the part.
  • Duplicates: any existing order already carrying the same customer PO number is flagged.

The result is a draft in Fluent's review queue. Every difference sits on the line it belongs to as a warning: a part that could not be resolved, a price that does not match, a unit that is not valid for the part. The approval workflow then routes the draft through stages, for example the order desk and then a pricing check. 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 a stage is needed at all. When the draft is approved, Fluent creates the order through Kinetic's own business logic, and every field read and every decision, including who signed on whose behalf, is in the audit log.

There are no templates per customer and no model training. Behavior is set with written instructions, and when a reviewer corrects a draft, the correction becomes an instruction.

Where the order waits: in Kinetic or before it

Both products keep a person in charge. What differs is where unreviewed work lives and how much help the reviewer gets.

With Lowki, the order exists in Kinetic from the moment the email is read. It has an order number, it appears in Order Entry and in any BAQ or dashboard that reads sales orders, and review means opening a held order, checking the flagged fields and editing the order itself. When the order should never have existed, such as a resent PO or a quote request read as an order, someone deletes or voids it in Kinetic.

With Fluent, Kinetic only sees approved orders. Before each approver opens the 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 exactly what to look at. The approver can ask the agent about the draft in a private chat, then approve, reject, or return it to the owner with a reason, and approvals reset when the owner resubmits. A rejected draft never reaches Epicor, and blocking issues cannot be dismissed.

Kinetic's hold does its job: the order cannot move on until someone releases it. The difference is Lowki's choice to create the order before anyone has looked at it. For an order desk that wants part, price and unit differences triaged before the order exists, more than one person to sign off, or a record of who approved what on whose behalf, approving first is the stronger model. The guide to held orders and staged review compares the two in depth.

Side-by-side comparison

Built byTechnology Coast Partners, an Epicor Platinum PartnerLowki.ai, founded inside UK manufacturer Thomas Dudley
ERPEpicor KineticEpicor Kinetic
Where the order waits for reviewA draft in Fluent's review queue; nothing in Kinetic until it is approvedA sales order created in Kinetic, on hold
How review worksWarnings on each line for parts, prices, units and duplicates; an approval agent notes what each approver should checkFlagged fields checked in Order Entry; a person takes the order off hold
Approval workflowsStages with parallel approvers, plain-language conditions, routing by name, least busy or the AI's pick, out-of-office delegates, approve by email reply, return to the owner with a reasonNot described beyond a person releasing the hold; confirm with Lowki
How documents arriveForwarded or emailed to the agent from any mailboxA Microsoft Exchange Online mailbox, or dragged onto an order in Kinetic
Formats readPDF, scans, photos, spreadsheets, email bodies, XML, EDIEmail attachments; confirm formats with Lowki
Per-customer setupNo templates or training; written instructionsNo templates or training
What sits in or near EpicorNothing installed; REST API from outside, with an access scope Epicor enforcesREST API, through an integration user
AP invoicesIn production: drafts for AP Invoice Entry, approved in Fluent, with two-way and three-way matchingEarly access: logs invoices in Logged AP Invoice Entry and matches them with Get Receipts
Other Kinetic screensQuote Entry, Customer Shipment, AR Invoice Entry, Cash Receipts Entry, PO Entry, Receipt Entry, Time Entry, Issue MaterialQuotes, set at deployment in place of sales orders
PricingPaid plans from $600/monthPer order line, in pounds: £0.15 pay as you go, or plans from £600/month for 5,000 lines, plus £400 setup
ReportingReview queue, audit log and usage in FluentBAQs filtered to the integration user; dashboards planned

Lowki details come from lowki.ai as of October 2026. Ask Lowki to confirm anything marked "confirm" in writing.

Why Fluent is the default on Epicor Kinetic

  • Nothing should reach Kinetic before it is right. Drafts wait in a queue, so planners, buyers and reports never see an unreviewed order, and nobody cleans up rejected ones.
  • Discrepancies need triage. Part, price and unit differences are listed as warnings on each line, so a reviewer works through the exceptions and leaves the rest of the order alone.
  • More than one person signs off. Approval workflows route a draft through stages with approvers working in parallel, decided by conditions written in plain language, with reassignment, ad-hoc reviewers and out-of-office delegates who sign on behalf of the person away, before Epicor sees it.
  • Approvers should see the problem before they open the order. An approval agent checks each draft against that approver's responsibility and leaves a note on what to look at, writes an approval summary of the document and the decisions on it, and lets the approver decide by replying to the email.
  • AP and the rest of the cycle are next. AP Invoice Entry with two-way and three-way matching is in production today, alongside receipts from packing slips, cash receipts from remittances, quotes, shipments and AR invoices. One vendor, one review queue and one credit balance across order to cash and procure to pay.
  • Orders arrive outside Exchange Online, or as XML, EDI, photos or spreadsheets.
  • You want an Epicor partner behind it. TCP has implemented Epicor for more than 20 years.

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. More Epicor teams are in our customer stories.

55 sec
median review time per document
Thousands
of documents reviewed by customers in the 90 days to 1 September 2026

When to choose Lowki instead

  • One person reviews every order inside Kinetic. If the hold in Order Entry is your whole review step and nobody else signs off, Lowki covers it.
  • You are a UK manufacturer and want a UK vendor, billed in pounds per order line.
  • Your volume is low or uneven. Lowki offers pay-as-you-go pricing per order line.

How to decide

Run both on the same batch of your own orders. Pick purchase orders that are hard for your team today: a customer who uses their own part numbers, one who orders in a different unit than you stock, one whose prices rarely match yours, and one who resends the same PO. Then compare:

  1. How many lines arrive fully resolved against your Epicor data.
  2. How each tool shows what it could not resolve, and where your team sees it.
  3. What happens to an order you reject, and who cleans it up.
  4. How long a person spends reviewing each order.
  5. What your Epicor administrator has to grant or maintain.
  6. Which other documents you want automated over the next year, and whether each one is in production today.
  7. Route one order to two approvers by a written rule, such as "orders from a new customer also go to credit", and see who receives it.
  8. Mark an approver out of office and see whether the order waits for them or reaches their delegate.
  9. Approve an order by replying to the approval email.
  10. Check what each approver is told was flagged 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.

See Fluent on your own orders

The order entry automation page covers sales orders in detail, the AP automation page covers supplier invoices, and the Epicor integration page explains the connection and access scope. To compare Fluent with Lowki on your own purchase orders, book a demo.

Frequently Asked Questions

Yes, and the stronger one wherever review matters. Both read the purchase orders customers email in and turn them into sales orders in Epicor Kinetic. Lowki creates the order in Kinetic on hold; Fluent keeps a draft out of Epicor and runs it through approval workflows, with an approval agent flagging what each approver should check, until it is approved. Fluent also runs agents in production for AP Invoice Entry, Receipt Entry, Cash Receipts Entry and seven other Kinetic screens.

According to Lowki's website, yes. Lexi creates the sales order in Epicor Kinetic through the REST API with the order on hold, and a person reviews it in Order Entry and takes it off hold. From that moment the order has an order number and appears in any BAQ or dashboard that reads sales orders, and an order that should never have existed has to be deleted or voided in Kinetic.

No. Nothing is written to Epicor while an approval is pending. The draft waits in Fluent's review queue with warnings on each line and runs through your approval stages, and blocking issues cannot be dismissed. The order is created in Epicor, through Kinetic's own business logic, only when the draft is approved.

Lowki describes its AP invoice automation as early access as of October 2026: it logs supplier invoices in Logged AP Invoice Entry and matches them against receipts. Fluent's AP agent is in production today, drafting invoices for AP Invoice Entry with two-way and three-way matching against the purchase order and its receipts, then routing them through approval workflows with conditions such as "invoices with no purchase order" and an approver the AI picks, such as the buyer on the PO.

Lowki prices per order line in pounds: £0.15 per line pay as you go, or plans from £600 a month for 5,000 lines, plus a £400 setup fee. Fluent's paid plans start at $600 a month, as shown on the pricing page.

Yes. Both work with on-premise and cloud Epicor Kinetic through the REST API. Fluent installs nothing inside Epicor, works within an access scope Epicor enforces, and restricted networks allowlist Fluent's fixed egress IPs.

Read more

Ready to Save Hours Every Week?

Send us a batch of sample documents. Our Epicor specialists will show you what an agent can automate, and what still needs your judgment.