Put your team on one account. Buyers order inside their authority, anything over it routes to an approver, and every order stays in one history that anyone with the right role can reorder from.
Buyer, approver, administrator. Not a permission matrix — a matrix is what turns a purchasing tool into an administration project.
Per person, per period. A blank limit is unlimited; a limit of zero means someone may build a cart but never complete one alone.
Over-limit carts are locked at the total they were submitted at and sent for sign-off. An approver signs off on a figure, not on a cart that can change afterwards.
Nobody decides their own request, administrators included. An approval a requester can grant themselves is not a control.
For runs the published ladder does not cover. Ask the desk to price it, negotiate in a thread, keep the record.
Paste a list of SKUs and quantities, or rebuild a past order exactly — same stock, same finish, same artwork.
A purchasing control that only exists in the browser is a decoration. These are honestly out of scope until the backend supports them.
Net terms
Orders are paid at checkout.
Purchase orders as payment
A PO number can be recorded; it is not a payment method.
Tax exemption
Handled by the tax provider, not by a checkbox.
ERP integration
No punchout, no cXML, no catalogue export.
Creating a company makes you its administrator. Members are invited afterwards and start with no purchasing authority until you set a limit.