Comparing purchase ordering systems feature by feature produces long evaluations and mediocre fits, because the features are broadly the same. Three facts about how your organisation buys decide which shape of product suits, and once you have them the shortlist is short and the decision is mostly settled.
The three facts
Orders raised per month, how many people raise them, and how often a delivery arrives incomplete. Low on all three and your accounting package's module is probably enough. High on the second and third and line-level receipt tracking becomes essential. High on all three with a dedicated buyer and a procurement suite starts to earn its keep.
Why partial deliveries are the pivot
They are what document-level tracking cannot represent. If deliveries almost always arrive complete on one date, an order is a single event and simple tools cope. If they arrive in pieces over weeks, the order is a running account, and that is exactly where cheaper tools stop being adequate and start generating manual work.
What to insist on at any size
Automatic unique numbering, approval before issue, receipts recorded by whoever takes the delivery, dated revisions, and an export you can read without the vendor. All five are inexpensive in any product and expensive to add later, and the last is the one people wish they had asked about.
Questions people ask about purchase ordering systems
Should we shortlist by industry?
Rarely. Industry-specific products matter where the buying itself is unusual; otherwise sizing matters more.
Can we move up later?
Yes, and it is easier than moving down. Clean data and a readable export make the move cheap.
How do we test partial receipting?
Order ten, receive four, invoice four, and check that six show outstanding on the line.