A purchase request is a list of lines somebody needs. It walks the approval chain your organisation actually has. What is approved becomes a purchase order, and what arrives is received straight into the warehouse at the price it was bought.
Procurement
Configure who approves, in what order. A request in flight carries a snapshot of that chain, taken the moment it was submitted, so adding an approver on Tuesday never pushes Monday's requests back a step and nobody's decision is rewritten under them.
The approval chain is configuration; what a request carries is a snapshot of it. Change the chain and the requests already walking it are untouched, because a request in flight never reads the configuration again.
An approver can pass a request while refusing a single line, with a reason attached to that line. There is no sixth status for a partial approval: which lines survived is a property of the lines.
A line can name a catalogue part. When the delivery arrives, receiving the order posts the stock in the same transaction, at the order's own price, into the location it was delivered to.
You configure who approves and in what order. When a request is submitted it takes a snapshot of that chain and carries it, so adding an approver on Tuesday never pushes Monday's requests back a step, removing one never retroactively approves what nobody approved, and renaming or deactivating a person never rewrites a decision they already took.
Yes, with a reason attached to that line. There is no separate status for a partially approved request: which lines survived is a property of the lines, and the register shows how many were refused so it never overstates what was agreed. An approver can also send a request back for changes instead of rejecting it outright.
No. A purchase order is a commitment of money, and the control every procurement function applies to it is that the person who commits the money is not the person who checks it. Solmex refuses the buyer's own order however many permissions they hold, and refuses to submit an order at all when nobody else could approve it, naming the fix.
You record the delivery against the order, and any line that names a catalogue part posts into the warehouse in the same transaction, at the order's own price, into the location it was delivered to. Receiving more than was ordered is refused, because a tolerance is a policy a site has to state.
Follow a request from the workshop through its approval chain to a purchase order and a goods receipt, in a 30-minute walkthrough.
NO COMMITMENT · YOUR DATA STAYS YOURS