> 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/enable.md).

# Enable Draft Orders

Draft Orders is off by default. Turn it on, choose who can submit, set the button label and the shop default payment term.

## 1. Open Draft Orders settings

In your Shopify admin go to **Apps → Orbit B2B → Orders → Draft Orders**, then click **Settings** in the top-right.

## 2. Turn it on

Toggle **Enable Submit Order for Approval**. This is the master switch — while off, the storefront shows the normal Checkout button and nothing changes.

> The storefront app embed **Easy B2B Wholesale** must also be enabled in your theme (**Theme editor → App embeds**) for the button to appear.

## 3. Eligibility — who can submit orders

| Mode                                      | Who can submit                                                      | When to choose                                       |
| ----------------------------------------- | ------------------------------------------------------------------- | ---------------------------------------------------- |
| **Approved B2B customers only** (default) | Customers whose Shopify tag matches one of your Customer Group tags | Recommended — keeps retail buyers on normal checkout |
| **Any logged-in customer**                | Any signed-in customer                                              | Looser, if you don't tag B2B customers yet           |
| **Everyone**                              | Anyone, including guests                                            | High-trust or invite-only stores                     |

The check runs on the storefront (to swap the button) and again on the backend at submit, so it can't be bypassed by editing the page.

## 4. Button label

Set the text shown on the storefront button (default **"Submit Order for Approval"**). This is a single value you type in your own language.

## 5. Checkout button selector (advanced)

Leave blank — the app auto-detects your theme's Checkout button (Dawn and most free themes are covered out of the box). Only set a CSS selector here if your theme uses an unusual Checkout button the app can't find.

## 6. Shop default payment term

Choose the term used when a customer isn't in a group — Due on receipt (pay now) or Net 15 / 30 / 45 / 60 / 90. See [Payment terms](/orbit-b2b-docs/draft-orders/payment-terms.md) for the full cascade (group default beats shop default; you can override per order).

## 7. Auto-create (optional)

Turn on **Auto-create draft order & send invoice on submit** to skip manual review — see [Auto-create on submit](/orbit-b2b-docs/draft-orders/auto-confirm.md). Leave off (default) to review and confirm each order yourself.

## 8. Notifications

* **Email admin on new order request** — you're notified when a request is submitted
* **Email customer on confirm** — the customer gets the payment link when you confirm

## Next steps

* [How a buyer submits an order](/orbit-b2b-docs/draft-orders/submit-flow.md)
* [How you confirm and send the payment link](/orbit-b2b-docs/draft-orders/confirm-flow.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/enable.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.