Sales & purchasing03
Catch the changed order before buying the wrong thing.
Compare the customer's purchase order with the approved quotation and show the exact lines that changed.
Illustrative workflow · Fictional sample records, not a delivered client project or measured result.
From incoming information
to something usable.
An order looks like the quotation, so someone forwards it to purchasing. A changed quantity, rate or specification then reaches the supplier before anyone notices. The check belongs before that commitment.
Switch between the source and the checked result. The sample shows what the software would organise, calculate or flag.
Same reference. Different commitment.
| Document | Item | Revision |
|---|---|---|
| Approved quote | BR-12 | v3 |
| Customer order | BR-16 | PO-92 |
| Purchasing | Awaiting check | Not released |
Match item identity as well as the document reference.
Three changes. No supplier order yet.
| Field | Approved quote | Customer PO |
|---|---|---|
| Quantity | 120 | 90 |
| Unit price | £12.50 | £11.80 |
| Item code | BR-12 | BR-16 |
Sales confirms the differences before purchasing commits.
Replace a full manual reread with a review of actual differences.
Changed quantities, lower rates, altered products and stale revisions.
What comes in.
- The approved quotation and revision
- The customer's purchase order
- Item identities, units and agreed terms
What comes out.
A difference report linked to the original lines, followed by a confirmed order version that purchasing can use.
What runs, and who checks.
Find the approved baseline
- Software handles
- Retrieve the quotation revision linked to the customer order and retain both originals.
- People check
- Confirm which quotation was actually approved.
Compare lines and terms
- Software handles
- Match by item identity and unit, then highlight quantity, specification, rate and term changes. Leave ambiguous matches open.
- People check
- Review substitutions and explain intentional commercial changes.
Release a confirmed order
- Software handles
- Save the resolved differences and approved version for downstream documents.
- People check
- Obtain customer clarification or internal approval before committing the purchase.
The item code changed, but the description did not.
Two products can share a short description. Treating them as the same item can conceal a different size, rating or finish.
Hold that line for identity confirmation. Keep the rest of the comparison visible without silently substituting a product.
A person makes the call.
Sales resolves differences with the customer. Purchasing proceeds from the confirmed version instead of assuming a similar-looking order is correct.
Measure the actual work.
Count material differences found before supplier commitment and time spent checking each order. Record changes missed by the check.
Bring the work you keep doing twice.
A recent job and its documents are enough to start. We trace the repeated steps, check where mistakes enter and define a useful first build around your existing tools.
Discuss this workflow