Every request for quote drafted into Epicor Quote Entry

Fluent records that it could not resolve the value, with the reasoning behind it, and leaves the quote in review. No match beats a speculative match: a quote is never created without a customer, and a line whose part or unit resolves to nothing is held on the draft with the reason written on it rather than sent to Epicor as a guess.

In Quote Entry. The header, the lines and the miscellaneous charges are committed together, so Epicor assigns the quote number and a line it rejects takes the whole quote back rather than leaving a header with no lines. The source files are attached to the quote, and the expiration date is left to Epicor's own quote-date controls.

Nothing posts unattended. Every run ends in a draft carrying whatever the agent could not settle: a customer it could not match, a line without a part, a unit that fell back to the part's sales unit. A person edits the draft and presses Process, and only then does anything reach Epicor. Approvers may approve or reject, never process.

That is the case the part step is built for. Alongside your part master, Fluent reads the Epicor cross-reference for the matched customer, which maps that customer's part number to yours, plus that customer's own past orders and quotes. When none of the three is convincing, the line comes back unmatched with the reasoning attached rather than matched to something that only looks close.

A configuration is only meaningful against a specific part revision, so turning on part configuration turns on revision selection with it. If a part is configurable but has no approved, effective revision, the line is left unconfigured with an explicit error instead of being configured against whatever revision the server would have picked. With price lists in use, prices are not sent at all: Epicor assigns them, and every line where the quoted price differs from the assigned one is flagged on the draft as a price variance.