What happens to a message, in depth.
The homepage shows the morning. This page shows the machinery: the chain an order goes through, the nine labels, the files it has to survive, and - stated plainly - where the edge of the system is.
From PO to tracked invoice, live today.
Five steps run for a real customer now. Three more arrive through the same inbox and are marked exactly as built as they are.
What each one means, and what happens next.
Every message gets exactly one primary label from this list. A message doing two jobs - an order with a question inside it - gets both picked up. For each, Dynaflo suggests the action; your person decides.
A purchase order. Runs the full chain: line items, stock check, pricing, draft invoice.
A chaser asking where an order stands. Matched to the order, not treated as a new one.
A remittance or payment confirmation. Checked against the invoice it is meant to settle.
A counter-offer or rate request. Extracted and flagged — price decisions stay with your person.
A problem with something already delivered. Never turns into an invoice by accident.
A request for a sample or swatch. Kept separate from a firm order.
A request to talk. Queued for a person, not processed as paperwork.
A question that needs an answer before anything else can happen. Queued for a person.
Doesn't fit the other eight. Queued for a person rather than guessed at.
The files this has to survive.
Any vendor can read a clean spreadsheet. Your customers do not send clean spreadsheets. This list is what Dynaflo is actually tested on.
Merged Excel headers
Column headers spread across two merged cells, or missing entirely.
Multi-sheet workbooks
One order across four tabs, only one of which has line items.
Scanned PDFs
A purchase order scanned at an angle, sometimes upside down.
Phone photographs
A photo of a printed PO, taken on a factory floor.
Orders pasted into the email body
No attachment at all — the order is the email.
Handwritten additions
A line item added in pen after the document was printed.
Their words. Your codes. Your shelves.
No customer uses your material codes. They use their own names, their own part numbers, or a description from memory. Matching that to the right code is the job - and the match is checked against your real stock, not a catalogue, so a shortage shows up before you promise a date.
When the match is not certain, it says so and asks. A guessed match on an invoice is exactly the mistake this exists to prevent.
The edges, in writing.
You have been oversold before. The fastest way to be believed about what this does is to be plain about what it does not.
Real screenshots go here.
The screens below will show the live system on real documents. They are held back until the customer whose data appears in them has agreed in writing.
Real screenshots of the running product will appear here once the customer whose data they show has agreed in writing.
See it on your own documents.
Send us one week of your order emails and we will show you what Dynaflo makes of them. Thirty minutes, on a call.