Purchase-order review
Workflow design — not yet built
Prepare line-by-line order checks before an order clerk decides what enters the ERP.
The workflow
- Buyer problem
- A purchase order can contain unclear customer matches, unknown parts, mismatched units, or disputed pricing.
- Intended users
- Order desks at industrial-parts distributors assessing a review process.
- Inputs
- Fictional post-extraction purchase-order fields and mock customer, product, contract-price, credit, and duplicate facts.
- Intended steps
- Validate the customer and order information.
- Compare quantities, part matches, units, and exact prices with mock source facts.
- Identify duplicates and line-level exceptions.
- Prepare a review packet, including apparently clean orders.
- Intended output
- An intended order-review packet showing the source values and the checks requiring attention.
- Human review
- An order clerk resolves mismatches and decides whether an order may proceed. A clean review does not authorize ERP creation or a customer acknowledgment.
- Limitations
- The design starts after extraction; PDF/OCR behavior is not demonstrated. Live ERP reads, reviewer authorization, reservations, order writes, and acknowledgments remain unimplemented.