Purchase orders without routine re-keying.
The work behind the workflow.
Staff opened incoming attachments, looked up product codes, converted carton quantities, checked stock and entered each order by hand. Different order formats made that process difficult to standardise.
Human Nexus reports that this work consumed about 4.5 full-time roles before automation. Product mismatches, older spreadsheets and pricing differences all needed to be handled in the workflow.
How the work moves.
- 01
Capture the order
An incoming purchase order is routed from the shared inbox to the appropriate processor.
- 02
Read the attachment
Document extraction reads PDF line items. Spreadsheet scripts parse workbook orders, with conversion for older file formats.
- 03
Match the products
Order lines are matched against the shared product master by code or barcode. Case-pack quantities are converted to units.
- 04
Check stock and stage
Stock is checked and order data is staged as parent and line-item records for the next step and audit trail.
- 05
Create the sales order
A sync flow checks whether the channel is active, then creates the sales order in the ERP without manual entry on the routine path.
- 06
Reconcile or escalate
The workflow compares ERP and source totals. It applies the described adjustment process, while unmatched products, missing fields and out-of-tolerance totals go to staff.
What the case study reports.
These are reported achieved results, not targets. The source provides approximate staffing-capacity figures without a measurement methodology or independently validated financial saving.
- Manual processing capacity reduced from about 4.5 full-time roles to about 0.5, according to the published case study.
- About four full-time roles of capacity returned to the business. This is a capacity measure, not a claim that four people were made redundant.
- Routine orders run without manual handling. The remaining capacity handles exceptions and special requests.
People handle unmatched products, missing information, unusual totals and special requests. Individual order channels can be paused without stopping the others.
Adapted from a published Human Nexus case study. The retailer and its trading partners remain anonymous. Identifying channel details are omitted. This describes an automation engagement, not a separately deployed Counterpart product.