Helios One · buyer workflow
Supplier reply parser: turn plain email into an exception
A small test for a messy inbox
Supplier replies rarely arrive as a clean table. The working question is narrower than “automate procurement”: can a buyer turn a reply such as “we can ship 20 on Friday, balance next Tuesday” into a visible exception without hiding uncertainty?
Use the preview below with the fictional reply. It shows the fields a buyer would review: quantity, date, partial shipment, and confidence. The sample deliberately leaves “Friday” unresolved because no message date is provided.
What the result means
- Confirmed quantity is the quantity stated in the reply, not the full open quantity.
- Partial is a flag for a split shipment; it does not close the line.
- Human review is required when a date is relative, missing, or conflicts with the PO.
- Undo belongs in the eventual workflow so a buyer can restore the prior promise date.
This is a tool-shaped proof, not an accuracy benchmark. The internal product brief describes the workflow boundary; it does not provide a measured production precision or recall figure. The two public Plex supplier documents show the kind of acknowledgment and delivery details suppliers are asked to provide, but they do not validate this parser.
If you want to test the surrounding workflow, generate the acknowledgment request, score the resulting receipt history, or prepare the minimum export.
Working artifact · fictional sample data
Reply parser preview
- Promised date
- Friday (needs date)
- Confirmed qty
- 20
- Partial
- Yes
- Review
- Human review
Sources and verification
- Internal Helios ERP product brief (reply parsing and undo boundary) (internal; accessed 2026-10-23) — The proposed buyer workflow, reply parsing with undo, and CSV-first boundary.
- NAL Plex Supplier Purchasing Manual (primary; accessed 2026-10-23) — A public supplier purchasing process that illustrates why acknowledgment details matter.
- Plex supplier portal work instructions (Stant) (primary; accessed 2026-10-23) — A public example of supplier acknowledgment steps and portal friction.
Frequently asked questions
Does this parser send or update supplier emails?
No. This staging artifact runs in the browser and shows a review result only. A production workflow would require explicit review, an audit trail, and a tested connector.
What happens to an ambiguous date?
It stays in a human-review state. A phrase such as Friday needs the message date and the buyer's calendar context before it can become a committed date.