Vendor quotes become purchase orders in Epicor Kinetic PO Entry

No. Every purchase order lands in Fluent as a draft, a reviewer sees the warnings collected at each step, and processing happens when they press process. There is no automatic posting path for purchase orders at all. If a line fails as the order is written, the partial order is removed from Epicor rather than left behind.

In PO Entry, as a normal purchase order: a header, its lines, and any header-level charges, with Epicor creating the release for each line on save. Every source file, including supporting material the agent was told not to extract from, is attached to the finished order.

It still gets created. Parts are searched against your part master and against the vendor part cross-reference in Epicor, scoped to the vendor on the quote, so the vendor's own part number can resolve to yours. When nothing matches, the line is written as a free-text line with the quoted description carried through, and the order still goes in.

A PO line lives in two units at once: the purchase unit the vendor quoted in and the inventory unit the part is stocked in. Fluent puts the quoted quantity on the line in the vendor's purchase unit and lets Epicor derive the stock quantity through its own conversion, and it writes the quoted cost over the vendor price list rather than the other way around. When no Epicor unit matches the document, the line falls back to the part's purchase unit and the draft carries a warning.

Behavior is set in written instructions. There are no templates, no field mapping and no model training, so rewriting the instructions changes what the agent does, and corrections made during review become instructions rather than retraining. Options such as always using the vendor's currency or terms, buying to a job material, or skipping part matching are settings on the agent.