Order what is short, and watch it until it arrives
What is short becomes a requisition, the requisition becomes an order, and the order is watched until goods arrive and reconcile. Nothing chased by diary.
Somebody ordered it. Probably.
Every business that moves goods has this conversation weekly.
Procurement in most businesses is a diary, a phone, and one person's memory of what was promised. The gap is not that things go unordered — it is that between asked for and arrived, nothing is written anywhere a second person can read.
What is short is decided by the order, not by whoever remembers to ask.
The shortfall raises its own requisition
Purchases start from recorded need, not from remembering.
A production requisition that cannot be filled from the godown turns its pending lines into a purchase requisition on its own. What you choose to buy for stock joins the same route.
Open until the goods say otherwise
An order on a supplier stays visibly open until material actually arrives — and arrival is not a feeling. The goods come in through the receipt module: counted, photographed, matched against the supplier's invoice, with any gap recorded and settled properly.
A diary and a phoneThe old way- "Was it ordered?" — a question for one man's memory
- Nothing between asked-for and arrived — that a second person can read
- The gap is discovered — when the workshop stops
An order on record- "It was ordered Tuesday" — so the chasing is specific
- Open until the goods say otherwise — counted, photographed, matched to the invoice
- Visibly pending — which is the difference between chasing and archaeology
What stays where it belongs
Your purchase ledger, supplier payments and input credits live in your ERP, exactly as they do today.
What this module holds is the operational half the books never see: who asked for the material, when the supplier was ordered, what actually arrived against the demand, and what is still owed to your godown.
Your ERP keeps
Exactly as it does today.
- The purchase ledger — and every entry your accountant works from
- Supplier payments — and the input credits against them
SaleShade Operations keeps
The operational half the books never see.
- Who asked for the material — and when the supplier was ordered
- What actually arrived — against the demand that raised it
- What is still owed — to your godown, visibly
One purchase, read from both sides
The books hold the money. Operations holds the event. Neither is asked to be the other.
Every purchase step leaves a stamp
Requisitioned, ordered, received, reconciled — each with who and when.
The act itself makes the stamp.
Nobody wrote this. Each line is the act of doing the work.The supplier's Thursday, on record
When the answer is written down, the weekly conversation changes: not "was it ordered?" but "it was ordered Tuesday — ring them about Thursday." Specific questions, specific chasing, no archaeology.
The shortfall and the job stay joined, so nothing is bought twice or forgotten once.
Raise one requisition and follow it to the rack.
Ask for a demo