An order that needs approving goes through four stages: the checkout, the wait, the decision, the payment.
1. The checkout: no way through it ends in a charge
When the cart needs approving, the plugin filters WooCommerce's list of available payment methods (woocommerce_available_payment_gateways) and leaves exactly one: its own Order approval method, shown as "Submit for approval". Every method that takes money — cards, PayPal, bank transfer, cash on delivery — is removed for that checkout.
That one filter is the whole guarantee. The classic checkout, the Checkout block and the Store API all read the same list, so there is no route through any of them that ends in a charge.
The alternative many shops use — let the customer pay, and refund them if the answer is no — costs you a refund fee, gives the customer a card statement to explain, and in some places means taking money for goods you were never going to supply.
The filter also works the other way: when a cart does not need approving (full edition, condition not met), the approval method is removed so the customer pays normally. Otherwise it would be a free way out of paying.
Which carts need approving
- Free edition: every cart, while Hold orders for approval is on.
- Full edition: the cart is checked against Which orders:
- Every order — always.
- Orders over an amount — when the products in the cart, at their current prices times quantities, come to more than the amount.
- Orders from chosen customer roles — when the logged-in customer has any of the chosen roles. Guests are never matched.
- Orders containing chosen products or categories — when any cart product is listed, or is in a listed category or one of its sub-categories.
2. The wait: Awaiting approval
When the customer places the order, the approval method moves it to the Awaiting approval status (wc-gmoa-awaiting) with the note "Waiting for a shop manager to approve it. No payment has been taken." The cart is emptied — the order exists, and a full cart is how somebody waiting for an answer accidentally places the same order twice. The customer sees the order-received page.
The status appears everywhere WooCommerce lists statuses: the orders list and its filter, the status dropdown on an order, and reports.
It is not payable. The plugin removes it from woocommerce_valid_order_statuses_for_payment, so WooCommerce shows no Pay button for it — not in My Account, not on the order page. A customer cannot walk past the approval by paying early.
WooCommerce does not cancel it. WooCommerce's sweep of unpaid orders looks only at Pending payment orders, so an order awaiting approval can wait as long as you need.
It holds its stock. When an order enters Awaiting approval, the plugin reduces its stock with WooCommerce's own wc_maybe_reduce_stock_levels() — as core does for On hold — so the last unit is not sold to somebody else while you read the order. The function records that it acted, so it never reduces the same order twice. Once you approve, the order is Pending payment, where WooCommerce releases the stock until the customer pays.
3. The decision
Approve or decline from either:
- the Awaiting approval box in the side column of the order screen (HPOS and classic), which has Approve, Decline and a Why (sent only if you decline) box; or
- the Approve and Decline bulk actions on the orders list, for many orders at once (a bulk decline sends no reason).
Only users who can edit orders (edit_shop_orders) can decide.
The Approve and Decline buttons submit the order screen's own form. The plugin rewrites the status that form posts to the decided one, because WooCommerce saves the posted status straight afterwards and would otherwise set the order back to Awaiting approval, undoing the decision.
A decision is refused on an order that is not waiting. Clicking Approve twice, or approving an order somebody already declined, does nothing. Without this rule a second click would push a paid order back to Pending payment and ask the customer to pay again.
Approve
- The time and the user who decided are recorded on the order (
_gmoa_decided_at,_gmoa_decided_by). - The order moves to Pending payment with the note "Approved."
- The customer is emailed the approval message with
{pay_link}— WooCommerce's own pay-for-order link, which carries the order key. It is safe to email because only someone with that key can open it.
Decline
- The decision is recorded, and the reason, if you typed one, is saved as
_gmoa_reason. - The order moves to Cancelled with the note "Declined."
- The plugin asks WooCommerce to put back the stock the order holds (
wc_maybe_increase_stock_levels(), which only acts if stock was taken and never twice). - The customer is emailed the decline message. It is sent even without a reason, because silence is worse than a short message.
4. The payment
The approved customer opens the link and lands on WooCommerce's normal Pay for order page. The approval method is not offered there (the order no longer needs approving), so they choose one of your ordinary payment methods. From here it is an ordinary WooCommerce order: payment moves it to Processing, stock is reduced, the usual emails go out.
The payment window. WooCommerce cancels a Pending payment order created at the checkout once it is older than Hold stock (minutes). An approved order is Pending payment, so the plugin filters woocommerce_cancel_unpaid_order to keep any order carrying _gmoa_decided_at open until the customer pays or you cancel it.
Worked example (full edition)
Which orders: Orders over an amount, Over this amount: 500.
- A customer checks out with goods worth 480. The approval method is removed; they pay by card as normal.
- Another checks out with goods worth 1,250. The only method offered is Submit for approval. They place order 1077; nothing is charged.
- Order 1077 shows Awaiting approval. You check the delivery address, then click Approve.
- The customer gets "Your order 1077 is approved — please complete your payment" with the total and the link, opens it and pays by card.
- Order 1078 looks like fraud. You type "We cannot deliver to this address" and click Decline. It is cancelled and the customer receives your reason.
