Fluent vs Lowki for Epicor Kinetic Order Entry and AP

Fluent and Lowki both read the purchase orders customers email in and turn them into sales orders in Epicor Kinetic, with a person deciding what goes ahead. The biggest difference is where the order waits for that person. Lowki creates the sales order in Kinetic straight away, on hold, and your team reviews and releases it there. Fluent keeps a draft in its own review queue, where parts, prices and units of measure are checked against Epicor and approval workflows run, and writes nothing to Kinetic until the draft is approved. Fluent also runs agents for ten Kinetic screens across order to cash and procure to pay in production, where Lowki's AP invoice automation is in early access.

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. An approval workflow can route the draft through stages, for example the order desk and then a pricing check, before anything is written. When the draft is approved, Fluent creates the order through Kinetic's own business logic, and every field read and decision made is in an 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. The difference is where unreviewed work lives.

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. Review happens on a draft that shows every warning beside its line, so a person approves, corrects or rejects it before an order number is assigned. A rejected draft never reaches Epicor, and approval stages, reassignment and out-of-office coverage run in the queue.

Which suits you depends on your team. If your order desk wants to stay in Order Entry and already treats the hold as the review step, Lowki's approach is direct. If you want part, price and unit differences triaged in one place, more than one person to sign off, or nothing in Kinetic until it is right, a staged queue fits better. The guide to held orders and staged review goes deeper.

Side-by-side comparison

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

Where Lowki may fit better

• Your order desk wants to stay inside Kinetic. If the hold is already how your team reviews orders, Lowki adds no second screen.
• Sales orders are the only document you plan to automate. Lowki is focused on order entry, and its track record comes from a working order desk.
• You are a UK manufacturer and want a UK vendor, billed in pounds per order line.
• Your volume is low or uneven. Pay-as-you-go pricing per order line can suit a desk that enters a few hundred lines a month.

Where Fluent fits better

• 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 reassignment and out-of-office coverage, before Epicor sees it.
• 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.

Luceco posted about its first day on EpiUsers.help. More Epicor teams are in our customer stories.

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.

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.