PO software exists to stop the same thing happening in every small business that grows past a handful of people: somebody orders something, nobody else knows, and the first anyone hears of it is an invoice for more than expected. The category is crowded and most of what is written about it is aimed at procurement departments. This page is about choosing a PO system when you have between five and fifty people, no procurement function, and no existing process to migrate. The free purchase order generator on this site prices and numbers an order while you decide.
The four things a PO system has to do
Raise a request before the money is committed, so the commitment is visible while it can still be stopped. Route it to somebody who can approve it, against a threshold written down rather than remembered. Turn the approved request into a numbered order a supplier will accept. And keep the order's status as it moves from raised to approved to received to invoiced. Every product in the category claims all four. The differences show up in the second one, because approval thresholds are where each company is different and where a rigid product forces you into a shape you did not choose.
Approval rules are where products actually differ
Ask how the system expresses your rules before you look at anything else. A threshold by amount is table stakes. What separates products is whether the rule can depend on the budget being spent, on the category, on who raised it, and whether it can require two approvers above a number. Write down the three rules you actually run today, including the informal one everybody knows, and make each product show you those three. A system that cannot express them will be worked around within a month, and a worked-around PO system is worse than none because it looks like control.
What a po system for small business does not need
Catalogue management, punchout to supplier websites, sourcing events, spend analytics across business units and ERP integration projects are all real, and none of them is a problem a company of thirty has. Buying them because they came in the same suite means paying for the procurement-function half and administering settings you will never use. The best po system for a small business is usually the one with the fewest screens that still expresses your approval rules and produces an order a supplier accepts.
What comes out matters more than what goes in
Two exports decide whether you can leave: the orders with their line detail and status, and the approval history. Ask about both before buying, and specifically about the approval history, because it is the part products most often keep and do not surrender. It is also the part with the value, since the reason to have run a PO system for two years is being able to say who approved what and when. A record you cannot export is a record you cannot audit and cannot take with you.
Questions people ask about po software
What should PO software do for a small business?
Raise a request before the commitment, route it for approval against a written threshold, produce a numbered order a supplier will accept, and track it from raised to invoiced. Anything beyond those four is usually procurement-function tooling.
How do I compare po systems?
Write down the three approval rules you actually run, including the informal one, and make each product express them. That separates products far better than a feature list, because approval is where every company differs.
Do I need a PO system with ten employees?
You need one when more than one person can commit money and nobody can say what is on order. Headcount matters less than how many people can spend and whether anyone is surprised by invoices.
Can I start without buying anything?
Yes. The free generator and request form on this site produce a numbered order and capture what, why, how much, which budget and who approves. They store nothing between visits, which is the boundary the paid record crosses.