> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://molsoft.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# What your buyers experience

**Where:** Your online store + the buyer's customer account **Who:** Staff buyers and approvers at your B2B companies **Part of:** [Delegate — B2B self-service](https://molsoft.crisp.help/en/article/delegate-overview-1rfsuep/)

This is what governance looks like from the buyer's side once [spend rules and approval flows](https://molsoft.crisp.help/en/article/spend-rules-approval-flows-8p03l0/) are in place — for the person placing the order and for the person approving it.

## Staff buyer

* When a cart trips a rule, a **banner** explains why, and the native/express checkout buttons are blocked. A **Submit for approval** button creates the request.
* **My requests** in their account tracks each one — pending, approved, rejected — with the line items and progress (e.g. *1/2 approvals*).
* On approval, they get an **email that opens the request** in their account, where a **Resume checkout** action reloads the exact cart to finish paying. They can reach the same request from **My requests**.
* A pending or approved request can be **edited** (which re-checks it) or **cancelled**.


![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/d/3/4dd3899948d8e000/screenshot-2026-08-31-at-83546_1pg1jke.png)

*The approval banner and Submit for approval button in the cart.*


## Approver

* A **queue** shows the requests waiting on them, each with the originator, location, cart, and which rule fired.
* On a request they can **Approve**, **Approve & pay** (complete the checkout on the buyer's behalf — the order still attributes to the buyer's company and location), **Reject** (a reason is required; the cart is preserved for editing), or **Comment**.
* The **company admin** can override and approve a request directly, including one blocked by a *block-checkout* rule — every override is recorded in the audit log.


![](https://storage.crisp.chat/users/helpdesk/website/-/4/d/d/3/4dd3899948d8e000/screenshot-2026-08-31-at-83726_xrelvk.png)

*An approver's request detail with the decision actions.* 


## Emails

Approvers are emailed when a request enters their queue; buyers are emailed on **approval** and on **rejection** (with the reason). Each email opens the relevant request in the buyer's account rather than linking straight to checkout — the buyer resumes from there. Comments are in-account only in this version.