We would like to suggest adding a multi-user approval workflow for B2B customer accounts.
This type of approval process is already commonly seen in business systems such as Sage and Interprise, where users can raise or prepare an order request, but a separate authorised user is required to approve it before it becomes a confirmed order.
Bringing a similar workflow into GoB2B would make the platform more suitable for customers with internal purchasing controls.
Suggested User Roles:
Requester / Buyer User
A standard account user who can log in, browse products, build a basket, and submit it for approval.
Approver / Admin User
A senior user or account administrator who can review submitted baskets, approve them, reject them, amend them if required, and then place the final order.
Suggested Workflow:
The requester logs into their account and adds items to their basket as normal.
Instead of placing the order directly, they choose Submit for Approval.
The nominated approver receives an email notification with a link to review the basket.
The approver can approve the basket and place the order, reject the request, edit the basket before submitting, or add comments back to the requester.
The requester can see the status of their request within their account.
Suggested Statuses:
Pending Approval
Approved
Rejected
Ordered
Cancelled
Why This Would Be Useful:
This would make GoB2B more suitable for larger trade customers, schools, venues, councils, installation companies, and businesses with formal purchasing procedures.
At the moment, the closest workaround is placing orders on a proforma basis and allowing the customer to run their own approval process externally. However, this is not as smooth as having the approval workflow built directly into the website account structure.
For customers already used to approval systems in platforms such as Sage or Interprise, a similar feature within GoB2B would feel familiar and would reduce friction when ordering online.
This feature could help increase customer confidence, reduce manual order admin, and make GoB2B stores more attractive to organisations where multiple staff members are involved in purchasing.
Possible Settings:
Enable or disable approval workflow per customer account.
Assign one or more approvers.
Set users as Requester, Approver, or Full Ordering User.
Allow optional order value approval thresholds.
Send email notifications to approvers and requesters.
Show approval status in account history.
Allow comments between requester and approver.
Example Use Case:
An employee at a customer company builds a basket of required products but does not have authority to place the order. They submit the basket for approval. Their manager receives an email, reviews the basket, makes any required changes, and then approves and places the order.
This would create a smoother purchasing process for B2B customers with internal sign-off requirements and would bring GoB2B more in line with the approval workflows already available in wider business systems.
