Example workflow
How an emailed order becomes a reviewable draft
This is a public sample with fictitious preloaded data. It shows the review and export steps so you can see the workflow before discussing a pilot.
What the sample demonstrates
Four steps that mirror what a pilot would do on your historical orders — using fictitious data so you can explore without sharing anything.
Review fields
Part numbers, quantities, and units are laid out as editable fields. You can see what was captured and what needs attention.
Select SKUs and units
Where a part number or unit is ambiguous, you pick the right option from a list. Nothing is guessed silently.
Approve or flag
Each line item can be approved or flagged for follow-up. A person makes the final call before anything moves forward.
Export to JSON
Once approved, the draft exports as structured JSON. In a real pilot, this is where your system would receive the data — but the sample does not connect to any ERP.
What this sample is not
It does not read real PDFs. The order data is fictitious and preloaded.
It does not call AI. The draft fields are static for demonstration.
It does not connect to any ERP or ordering system. Export is to a JSON file only.
It is not a case study or a client engagement. No real company or results are represented.
Want to try this on your historical orders?
We scope a pilot on an agreed sample set from your team. Send a few details to get started.