> For the complete documentation index, see [llms.txt](https://orbit-b2b.gitbook.io/orbit-b2b-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orbit-b2b.gitbook.io/orbit-b2b-docs/draft-orders/submit-flow.md).

# How a buyer submits an order

This is what your B2B customer sees on the storefront.

## 1. The button on the cart

For an eligible customer, the app replaces the theme's **Checkout** button on the cart page (and cart drawer) with your **Submit Order for Approval** button. Accelerated buttons (Shop Pay, Google Pay) are hidden so the buyer goes through approval instead of paying immediately.

Customers who aren't eligible (not logged in, or not a B2B customer) still see the normal Checkout button — retail shoppers are unaffected.

## 2. Submitting

When the buyer clicks the button:

1. The whole cart (every line item, quantity, and any product-option properties) is captured.
2. It's sent to your store as a **pending** order request — **no payment is taken**.
3. The cart is emptied and the buyer sees a confirmation:
   * *Manual review:* "Order submitted — we'll review it and email you a payment link shortly."
   * *Auto-create on:* "Order confirmed — we've emailed your payment link" with a **Pay now** button.

## 3. Eligibility recap

Eligibility uses the customer's Shopify tags against your Customer Group tags. Example: with **Approved B2B customers only**, a customer tagged `b2b-gold` (in a B2B group) sees the button; a regular retail shopper sees normal Checkout.

If a group's members should be eligible, make sure the group exists in **Customers → Customer Groups** — the app keeps the storefront eligibility tag list in sync whenever you save a group.

## Next steps

* [How you confirm and send the payment link](/orbit-b2b-docs/draft-orders/confirm-flow.md)
* [Payment terms](/orbit-b2b-docs/draft-orders/payment-terms.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://orbit-b2b.gitbook.io/orbit-b2b-docs/draft-orders/submit-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.