Purchase and vendor management software covers what a factory buys and who it buys from. It holds requisitions and approvals, enquiries and comparisons, purchase orders and amendments, open order follow-up, receipt against order, measured lead times per vendor and item, approved vendor status, rate contracts, and vendor rating on quality and delivery rather than on price alone. Pentoggle is an AI platform that generates production-ready software from a plain English description, which means a factory can build purchasing around its own approval structure and vendor base instead of adapting to a system built for a procurement department.
Most manufacturers in India already run Tally for accounting, some run Busy or Marg, and larger businesses may run SAP Business One. Those systems handle purchase, sales, GST and accounting well. This is not a proposal to replace them. Pentoggle builds the purchasing application around them, covering the workflows they were never designed for.
One boundary is worth setting. This page covers what you buy and who from, up to receipt. What happens after material arrives is covered in the manufacturing inventory and stores guide.
Key takeaways
- Lead times used for planning are almost always assumed rather than measured, which makes every reorder level in the factory an estimate built on an estimate.
- Placing a purchase order is a small part of purchasing, and open order follow-up is where the delivery date is actually won or lost.
- Vendor rating on price alone selects for the vendor who costs the most, once late deliveries and rejections are counted.
- Approved vendor status expires on a calendar, and purchase orders get raised against lapsed approvals unless the status sits where the order is raised.
- The number that runs purchasing is on-time and in-full receipt against the order, by vendor.
Why purchasing in most factories is a follow-up job
The purchase function in a typical Indian factory spends a modest amount of its time placing orders and most of it chasing them. Calls to vendors, promises collected, revised dates noted on a printout, and the same conversation repeated the following week.
This is not inefficiency. It is the actual job, because a purchase order is a request rather than a delivery. What makes it painful is that the chasing runs on memory and a list, so the follow-up that happens is the one somebody remembered, and the item that quietly slipped is discovered when production asks for it.
Accounting systems record the order and the receipt correctly and are silent about everything in between. They will tell you what is pending in total. They will not tell you which pending orders are past their promised date, by how long, and which of those are blocking something.
Packaged ERP does model this, and the larger units use it. Where it tends to fall short is in the approval structure, which in most family-run manufacturing businesses does not resemble the workflow the software assumes, and in vendor rating, which is usually configured optimistically and then ignored.
What purchase and vendor management software holds
Requisitions and approvals
Requests from stores, production or maintenance, with your approval structure as it actually works.
Enquiries and comparison
Quotations received against an enquiry, compared on landed cost rather than quoted rate.
Purchase orders and amendments
Orders with terms, delivery schedule and every amendment retained rather than overwritten.
Open order tracking
What is pending, against what promised date, how overdue, and what it is blocking.
Receipt against order
Quantity received against ordered, short supplies, excess and rejections at incoming inspection.
Measured lead times
Actual days from order to receipt, per vendor and per item, held as history rather than assumed.
Approved vendor status
Which vendors are approved for which materials, with status validity and audit or requalification dates visible where orders are raised.
Rate contracts
Agreed rates with validity periods, so an order raised outside the contract is visible.
Vendor rating
Quality performance from incoming rejections, delivery performance from measured lead times and on-time receipt, alongside price.
Payment status
What is due and when, read from your accounting system rather than duplicated in it.
Nobody measures lead time, and everything depends on it
Ask a factory what the lead time is for a particular item and you will get an answer immediately. Ask where that number came from and the answer is experience, or the vendor's own claim, or a figure entered when the item was created some years ago.
Reorder levels are calculated from that number. Material readiness checks in planning use it. Safety stock is set against it. And it is, in almost every plant, unmeasured.
Measuring it costs nothing extra, because both dates already exist. The order was raised on a date and the material was received on a date. Holding the difference, per vendor and per item, builds a real distribution within a few months: the typical lead time, the spread, and how much worse it gets in particular seasons.
Two things follow. Reorder levels can be set against evidence, which usually means less stock on the reliable items and more on the erratic ones, rather than a uniform assumption applied to both. And vendor conversations change, because a vendor whose quoted lead time is ten days and whose measured average is nineteen is a different proposition from one whose measured average is eleven, and only one of those facts is currently in the room.
The cheapest vendor is often the most expensive
Purchase performance is commonly measured on price, sometimes as savings against a previous rate. It is the easiest thing to measure and the most misleading.
A vendor who is two percent cheaper and delivers a week late imposes costs that never appear against them: a machine idle, a job resequenced, an urgent purchase at a premium elsewhere, a customer delivery missed. A vendor whose material carries a higher rejection rate imposes an inspection load, a shortage discovered mid-production, and material handled twice.
Neither cost lands in the purchase function's numbers, which is why the incentive keeps pointing at price.
Rating vendors on quality and delivery alongside price makes the comparison honest. Incoming rejection rate is already recorded if incoming inspection is captured. On-time performance falls out of measured lead times. Neither requires new data collection, only that the two existing records are attributed to the vendor rather than to the month.
The result is usually uncomfortable and useful in equal measure: the vendor everyone likes because they are cheap turns out to be the one causing most of the disruption, and the evidence for that conversation now exists.
Follow-up is the job, so build for it
Since purchasing is mostly chasing, the software should be built around chasing rather than around order entry.
The view that matters is a list of open orders sorted by how overdue they are, with the promised date, the revised date if one was given, who promised it, and what the material is blocking. That last column is what converts a follow-up list into a priority list, since an item that is holding a customer order deserves the call before an item that is topping up a consumable.
Recording each follow-up and the commitment received also builds something a plant rarely has: a history of whether a particular vendor's promises hold. A vendor who reliably delivers on their revised date is manageable. A vendor who gives a new date every week is a different problem, and it takes several weeks of recorded conversations to see the difference.
Why building this is now practical
Purchase modules in packaged systems assume a procurement process with defined roles and approval levels. In most Indian manufacturing businesses the approval structure is specific, sometimes informal, and frequently involves the owner directly for anything above a threshold. Software that requires the process to change first tends not to get used.
With Pentoggle you describe how buying actually works in your business, including who requests, who approves what, how you compare quotations and how you follow up, and get a working application. When a threshold changes, a new approval step is added, or you want vendor ratings computed differently, you describe the change and the application updates. Most factories start with open order tracking and receipt against order, because those two produce the lead time and rating data everything else needs.
Where purchasing looks different by industry
- Auto Component Manufacturing Software, where your own vendors are rated the way your customers rate you.
- Personal Care and Cosmetics Manufacturing Software, where packaging components decide whether a run can start.
- Electronics Assembly Software, where a single line of a long bill of materials blocks the build.
- Pharmaceutical Manufacturing Software, where approved vendor status carries regulatory weight.
- Food Processing Software, where supplier lots determine yield as much as price.
Why manufacturers choose Pentoggle for purchasing
Your approval structure, not a workflow template
Including the thresholds and the people who actually decide.
Built for follow-up
Open orders by overdue days, with what each is blocking.
Lead times measured, not assumed
From dates you already record.
Vendor rating that includes quality and delivery
Computed from data you already collect.
Changes in days
A new approval level or a new rating basis does not become a three month project.
The one number that runs purchasing
On-time and in-full receipt against order, by vendor.
Price variance measures negotiation. This measures whether the material arrives when it was promised and in the quantity ordered, which is what production and planning actually depend on.
Track it monthly per vendor, and read it alongside incoming rejection. A vendor who scores well on both is worth a longer rate contract and more of your business. A vendor who scores badly on both is costing more than their rate suggests, and this is the number that makes that argument without an argument.
Ready to build purchasing software?
Placing the order is the easy ten percent of purchasing.