Sales Order Exceptions in Epicor Kinetic: When the Customer PO Does Not Match
Customer part numbers, prices, units, ship-tos, duplicate POs and discontinued parts: what Fluent flags on the draft for each, with worked examples, and who resolves it.
Gonzalo Nuñez
Chief Technology Officer

When a customer purchase order does not match Epicor Kinetic, the order should stop in front of a person with the mismatch named on the line, and nothing should reach Order Entry until that person decides. That is how Fluent handles it: each exception is written onto the draft sales order as a warning or a blocker, an approval workflow sends the draft to whoever owns that kind of decision, and Fluent creates the order in Kinetic only after it is approved.
This guide works through the six exceptions an order desk sees most, with an example of each, what Fluent writes on the draft, and who usually resolves it.
Warnings and blockers
Fluent sorts what it finds into two kinds:
- A warning means the draft is complete, but something deserves a look. Fluent says what it used instead, for example the customer's default ship-to, so the reviewer can accept it or change it.
- A blocker means the draft cannot become an order yet. A part that matched nothing in Epicor is a blocker, and the draft cannot be approved until a person resolves it.
Both sit on the line or header field they belong to, so a reviewer works through the exceptions and leaves the rest of the order alone.
1. A customer part number Epicor does not know
Example. A distributor orders "VLV-2040-SS" on line 3. Your part is 40-2040-316, and the customer has never ordered it under that number before.
What Fluent does. The agent resolves customer part numbers to your parts using your Epicor data, including the customer's own part numbers you already keep. When it finds the match, the line carries your part, with the customer's number kept. When nothing matches, the line carries a blocker, "No Epicor part matched", and the draft waits.
Who resolves it. The order desk picks the right part on the draft. When a reviewer corrects a part, the correction can become a written instruction, so the next order from that customer resolves it.
2. A price that differs from Epicor's
Example. The PO prices a bracket at $4.10. Your price list for that customer says $4.35.
What Fluent does. Epicor's own price lists price the line, the way they would if your team keyed it. Where Epicor's price differs from the document's, the line carries a warning that shows both: the price on the PO and the price in Epicor, and that the order uses Epicor's.
Who resolves it. Whoever owns pricing. An approval stage with a plain-language condition, such as "any line where the customer's price differs from ours", sends only those orders to sales or pricing, and every other order skips the stage.
3. A unit of measure that does not fit the part
Example. The customer orders 12 "CS" of a part you stock and sell in each.
What Fluent does. Units are taken from the PO, never assumed. Where the unit is one the part carries, Fluent converts the quantity to the part's sales unit and notes the conversion on the line. Where the unit is not valid for the part, the line carries a blocker. Where the PO gives no unit at all, the line carries a warning naming the part's sales unit that will be used, so a person confirms it.
Who resolves it. The order desk, usually with one call to the customer the first time. If the customer always means cases of 24, write that down as an instruction.
4. A ship-to that is not on file
Example. The PO ships to a new job site that is not one of the customer's saved ship-to addresses.
What Fluent does. It tries the customer's saved ship-tos first. When none matches, it uses the address on the PO as a one-time ship-to where Epicor allows one, or the customer's default ship-to, and writes a warning saying which it used and why. When there is no address it can use, the draft carries a blocker.
Who resolves it. Customer service, who decide whether the address becomes a saved ship-to in Epicor or stays a one-time address.
5. A duplicate or revised PO
Example. The buyer emails PO 88231 on Monday, then sends it again on Wednesday asking for a ship date.
What Fluent does. Before drafting, it looks for orders already carrying that customer PO number and writes a warning naming them, "Possible duplicate of order 51234". Nothing is written to Epicor, so a resent PO never becomes a second order by accident.
Who resolves it. The order desk rejects the draft, or, for a genuine revision, updates the existing order. A rejected draft never reaches Epicor, so there is nothing to delete.
6. A discontinued part
Example. A long-standing customer reorders a part you made inactive last quarter.
What Fluent does. Fluent does not substitute a replacement part on its own. Epicor itself refuses an inactive part on a sales order line, so an order cannot be created with it, and the reviewer chooses the replacement on the draft.
Who resolves it. Sales or the order desk, who know which part replaced it and whether the customer needs to approve the change.
Exception table
| Exception | What Fluent writes on the draft | Kind | Who usually resolves it |
|---|---|---|---|
| Customer part number not matched | No Epicor part matched, on the line | Blocker | Order desk |
| Price differs from Epicor's | Both prices, and that the order uses Epicor's | Warning | Pricing or sales |
| Unit not valid for the part | The unit, on the line | Blocker | Order desk |
| No unit on the PO | The part's sales unit that will be used | Warning | Order desk |
| Ship-to not on file | One-time or default ship-to used, and why | Warning | Customer service |
| No usable ship-to | No Epicor ship-to matched | Blocker | Customer service |
| Same customer PO number on an existing order | Possible duplicate, with the order number | Warning | Order desk |
| Customer not found | No Epicor customer matched | Blocker | Order desk |
| Inactive part | Epicor refuses it on the order line | Refused by Epicor | Sales or order desk |
Route each exception to its owner
Exceptions differ in who should decide them, so the approval workflow should send each order to the people its exceptions need. A common setup:
- Order desk, every order: parts, units, duplicates and missing values.
- Pricing, only when a line's price differs from Epicor's, by a condition written in plain language.
- Credit or customer service, only for new ship-tos or customers on hold.
Before each approver opens the draft, the AI reviews it against that approver's written responsibility and marks it "nothing flagged" or "needs review", with a note on what to check. Approvers can decide by replying to the email, and an approver who is away is covered by a delegate.
What this looks like at StoneAge
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
Related guides
- How to automate Epicor sales order entry: every route into Order Entry, compared.
- Best AI order entry software for Epicor Kinetic: Fluent against WizCommerce, Ordermatic, Conexiom, Lowki, Esker and ECM.
- How to test AI order entry on your own Kinetic system: a pilot checklist built on these exceptions.
- AI sales orders held in Epicor or staged for review: where an order should wait.
See it on your own exceptions
Send us the purchase orders your desk finds hardest, and we will run them through Fluent with you. The order entry automation page covers sales orders in detail and the Epicor integration page explains the connection. Book a demo.


