One colleague orders materials for next week's client session. Another notices the same need and places a second order. Both checked what was in the cupboard, but neither could see the other's pending commitment.
Preventing duplicate purchases means making the requirement, owner and current ordering state visible before someone acts. An inventory of received items alone cannot show what has already been requested, approved or ordered.
Photo by Kelly Sikkema on Unsplash.
Check the need, not just the product name
Two requests for similar equipment may serve different dates or teams. Conversely, different descriptions may refer to the same requirement. Record the intended use, quantity, needed-by date and receiving location so the comparison has context.
Ask whether an existing resource can meet the need. Do not assume a booked or unsuitable item is available merely because it appears in a stock list.
A pending-purchase record
Requirement and the work it supports.
Quantity or service scope and relevant date.
Requester and coordinating owner.
Existing stock or resource check.
Request, approval and order states.
Authorised purchaser and supplier reference.
Receiving owner and expected arrival.
Cancellation or consolidation decision where duplication is found.
Assign a stable reference before approval so colleagues can identify the same need across messages and systems. The source-of-truth register should explain where that current state is maintained.
An illustrative duplicate-order check
A service team needs presentation equipment for a workshop. One colleague has requested approval for hire, while another is about to buy a replacement. The shared requirement reveals the overlap before either second commitment is made.
The owner checks availability and suitability, then obtains the appropriate decision. One route remains active and the other is explicitly stopped. Nobody simply deletes the second request, leaving its requester free to recreate it later.
Deal carefully with duplicates already placed
Gather order references and current supplier status. The authorised commercial owner decides which action is possible under the actual terms. Do not assume an order can be cancelled, returned or merged without consequence.
Update the receiving team so an unexpected second delivery is not accepted without context. Use your authority boundaries to distinguish spotting a duplicate from approving a commercial response.
Review why visibility failed
Look for requests made outside the agreed route, delayed status updates or approvals that do not name the purchaser. A new form is not enough if people can still create commitments without checking the current record.
If the same need creates parallel purchases across your team, Hili Consulting can help connect requests, approvals and orders around one visible operating record.
