Commerce Purchase Order

Configuration

User field

This payment gateway gives you the option of requiring users to be approved to use purchase orders. When it is installed it adds a field, Purchase Orders Authorized to the User entity. By default, this field is not displayed. To use this field, and require user pre-approval for Purchase Orders, begin by browsing to admin/config/people/accounts/form-display and move this field from Disabled into the form.

Payment Gateways

Payment gateways are added at admin/commerce/config/payment-gateways. Commerce Purchase Order adds the following to the gateway configuration form:

• Limit maximum open purchase orders The number of unpaid purchase orders a customer has can be used to prevent new purchases. See Workflow below.
• Purchase order users require approval in the user account settings When selected, the value of Purchase Orders Authorized is examined when the customer "pays and completes" the order. If the field is not checked (is FALSE) then the payment is denied (not authorized).
• Payment instructions Formatted text instructing the user how to pay their Purchase Order amount. Displayed at checkout and in the confirming email.
• Conditions: Customer - Limit by field: Purchase Orders Authorized This condition is useful when Commerce Purchase Order is one of multiple gateways enabled. When selected the gateway is only offered as an option if the Customer is approved to use it. See the discussion of the field Purchase Orders Authorized above.

Workflow

Commerce Purchase Orders normally progress through the following:

1. New The checkout process has begun and a PO number assigned to a one-time payment method.
2. Authorized The payment is saved and the user has checked out. The Purchase Order has not been paid.
3. Paid A user with permission to administer payments has browsed to the payment tab of the relevant order, selected Receive as the operation, and recorded the payment by saving the Receive Payment form.