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

# Draft Order emails

Two emails drive the Draft Orders flow. Toggle each under **Orders → Draft Orders → Settings → Notifications**, and edit the wording under **Settings → Email Templates**.

## The two emails

| Template                    | Sent to    | When                                                              |
| --------------------------- | ---------- | ----------------------------------------------------------------- |
| **Order request submitted** | Shop admin | A buyer submits a new order request                               |
| **Order request confirmed** | Customer   | You confirm (or auto-create sends it) — includes the payment link |

## Where they go

* The **admin** email goes to your store's admin email (Shopify → Settings → Store details).
* The **customer** email goes to the address on the order request, with the payment link and terms.

## Editing the wording

Open **Settings → Email Templates**, pick the Draft Orders template, and edit the subject and body. Shortcodes like `{{request_number}}`, `{{customer_name}}`, `{{subtotal}}`, `{{payment_terms}}`, and `{{pay_link}}` are filled in automatically. Defaults ship in English and Vietnamese; other locales fall back to English.

## If emails aren't arriving

* Check the shop's email / SMTP setup (**Settings → Email → SMTP**) and send a test email.
* Check the recipient's **spam** folder — mark the first email "Not spam".
* Confirm the notification toggle is on in Draft Orders → Settings.

See [Emails not sending](/orbit-b2b-docs/faq-and-troubleshooting/emails.md) for the full checklist.

## Next steps

* [Confirm and send the payment link](/orbit-b2b-docs/draft-orders/confirm-flow.md)
* [Troubleshooting](/orbit-b2b-docs/draft-orders/troubleshooting.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/emails.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.