Approver workflow

Who can approve?

The approver must be an active manager for the same company as the buyer. One approver can manage requests from several buyers in that company. Authorization does not automatically extend to unrelated companies.

Open the pending request

Use the approver experience to open a request and confirm:

• The buyer and company context are correct.
• The requested products and variants match the business need.
• Quantities and subtotal are acceptable.
• The buyer note provides enough context.
• The spend threshold or matching rule is appropriate.

Approve or reject

Approve when the exact request should be allowed to proceed. Reject when the buyer should not continue with that request. Record useful decision context where the interface permits it.

After the decision

An approved buyer can restore the request cart and attempt checkout. A rejected request stays in the history and cannot be reopened, but the buyer may submit a new request for an updated cart.

Approval expiry on Growth

Growth supports a configurable approval validity window. The default is 72 hours when expiry is used. A value of zero means the approval does not automatically expire.

Approver self-management on Growth

If the merchant enables the capability for a company, eligible managers can manage buyer approval settings for that company. Keep an internal owner responsible for reviewing who has manager authority.

Troubleshooting

Problem	Resolution
Request is not visible	Confirm the approver is active and assigned to the request's company.
Request is no longer pending	Refresh the request state; another decision, withdrawal, or expiry may already have occurred.
Buyer cannot check out after approval	Ask whether the cart changed, a discount changed subtotal, the approval expired, or the signed-in buyer differs.