Problem/Motivation
I've got a site that needs another step in the purchase order workflow, and it seems like something that might be useful to others, so I made a patch.
The extra step is between "authorized" and "completed." I'm calling it "approved." It means that an administrator has reviewed the PO and deemed it legitimate, so the (digital) product can be delivered and billed later to the buyer.
The site I'm working on uses this for a couple of products.
One is "pay to publish" nodes. In some cases, these will be typical purchase orders. In others, the buyer will be requesting a freebie and will do so by submitting a PO with that request.
Another product that needs admin approval is a postal mailing list of selected users (who of course have given permission). Here, too, an admin will need to approve the purchase before the list can be downloaded.
I know that this module has the ability to restrict the use of purchase orders to approved users. But that requires some advance work. The user has to create an account, then request permission to use a PO, and finally an admin has to grant that permission. Only then can the order be placed.
I need it to work more like Drupal 7, where the user submits a purchase order, and an admin then goes to the "payment" tab to approve ("validate") it. Even anonymous can submit an order, although an account for that buyer is created upon checkout.
Steps to reproduce
Create a purchase order and go to /admin/commerce/purchase-orders, There's no provision for review and approval/rejection after the PO is submitted, just payment/void/refund.
Proposed resolution
Patch coming momentarily.
Remaining tasks
Review, amend, commit, relax.
User interface changes
Admin only: New state and new operations choices on /admin/commerce/purchase-orders.
API changes
None.
Data model changes
None, unless a new value for "state" in the commerce_payment table counts.